Reaction Manager Crash

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
Rico_uk
Licensed Customer
Posts: 118
Joined: Mon Oct 24, 2011 6:42 pm

Any object with an Octane material on it will crash Max instantly if you try to select that object as either the master or a slave in the Reaction Manager.
azen
OctaneRender Team
Posts: 790
Joined: Mon Jun 01, 2015 11:06 pm

Hi,

Thank you for raising this issue, so that we may look into resolving it for future releases if possible. The Reaction Manager certainly does not react well to objects with Octane Materials in it. You can still use the Reaction Manager with meshes containing Octane materials, though this will require you to assign the Octane material after completing your setup with the Reaction Manager.

In the cases of meshes that already have Octane Materials assigned, a simple workaround is to assign a default (non-Octane) material to target meshes, use the Reaction Manager, and then re-assign the Octane materials where needed. In the meantime, I will keep this forum updated as to what measures have been determined to resolve this issue.
User avatar
pixonoid
Licensed Customer
Posts: 26
Joined: Wed Sep 23, 2015 10:29 am

i wanted to point out that this issues is still present,
lost almost a day times work, reimporting checking etc etc, until i came to the almost stupid assumption (well it wasnt that stupid afterall) that octane might play a role in my problem with the reaction manager



this is actually unaccetable.

when are you guys going to fix this ?
GPU - 2x Gigabyte GTX1080 8GB + 1x EVGA GTX980 TI sc | CPU - Intel i7-4790K@ 4.0GHz | OS - Windows 10 Pro 64-bit - 32 GB RAM | 3Dsmax - many
azen
OctaneRender Team
Posts: 790
Joined: Mon Jun 01, 2015 11:06 pm

pixonoid wrote:i wanted to point out that this issues is still present,
lost almost a day times work, reimporting checking etc etc, until i came to the almost stupid assumption (well it wasnt that stupid afterall) that octane might play a role in my problem with the reaction manager



this is actually unaccetable.

when are you guys going to fix this ?
It was my understanding that the problem was fixed. It could be possible that the issue snuck back into the build at some point - I'm not 100% certain without investigating further.

Either way, the issue has been resolved, and the fix will be available in the next update.
User avatar
pixonoid
Licensed Customer
Posts: 26
Joined: Wed Sep 23, 2015 10:29 am

Thank you so much azen, this makes my project alot easier from now :)
GPU - 2x Gigabyte GTX1080 8GB + 1x EVGA GTX980 TI sc | CPU - Intel i7-4790K@ 4.0GHz | OS - Windows 10 Pro 64-bit - 32 GB RAM | 3Dsmax - many
Post Reply

Return to “Bug Reports”