Bug with standard max camera

Sub forum for bug reports
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.


All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Post Reply
mark0spasic
Licensed Customer
Posts: 146
Joined: Thu Mar 08, 2012 4:46 pm

I found bug when using standard 3dsmax free camera. When I render image using octane render viewport and try to save image 3dsmax won`t open max framebuffer. This only happens with standard camera not with octane camera or when in perspective view. OctaneRender® for 3ds max® v2.25 - 2.17 3dsmax 2014.
This happens in any scene even in empty scene.
AMD FX 6300, 24 GB RAM, Gigabyte ga-990fxa-ud5, 2x MSI GTX 780 3GB
azen
OctaneRender Team
Posts: 790
Joined: Mon Jun 01, 2015 11:06 pm

Hi,

Just to clarify - have you ever encountered this issue in previous versions of the plugin? If this has not been an issue in in 2.16 or before, this will make the issue far easier to isolate and resolve.

Cheers!
mark0spasic
Licensed Customer
Posts: 146
Joined: Thu Mar 08, 2012 4:46 pm

Previously I had installed OctaneRender® for 3ds max® v2.25 - 2.15 and didn`t have any problems, this only occurs in v2.25 - 2.17.
AMD FX 6300, 24 GB RAM, Gigabyte ga-990fxa-ud5, 2x MSI GTX 780 3GB
azen
OctaneRender Team
Posts: 790
Joined: Mon Jun 01, 2015 11:06 pm

Hi,

Thank you for the clarification. Version 2.18 has just been released, so I would recommend upgrading to that and seeing if that fixes your issue. I will confirm on my end if the bug can be duplicated in the new release - if the problem is still there, I will raise the issue.

Cheers,
Azen
mark0spasic
Licensed Customer
Posts: 146
Joined: Thu Mar 08, 2012 4:46 pm

Hi, with new version everything works as is should v2.25 - 2.19. :)
AMD FX 6300, 24 GB RAM, Gigabyte ga-990fxa-ud5, 2x MSI GTX 780 3GB
azen
OctaneRender Team
Posts: 790
Joined: Mon Jun 01, 2015 11:06 pm

Excellent! Good to see that your issue was among those fixed in the recent releases.

Cheers,
Azen
Post Reply

Return to “Bug Reports”