OTOY Forums

mbetke wrote:Can't render with this release. Using 431.86 Studio Drivers. As soon as the Octane Viewport opens, 3ds max nearly freezes and I have to click the red x several times until I get the whole program closed.
I didn't set a GPU to low priority because it was never necessary and I always had a smooth interaction.

EDIT: Updated to the latest Studio Driver. Problem persists. All displays nice until I click something in the viewport. Then endless lag and no interaction.

javierluisbravo wrote:

paride4331 wrote:

javierluisbravo wrote:I still don't understand why "OctaneRender_VR_for_3ds_Max_2018.1.2_-_7.06" works perfect regarding movable proxy objects.
and all the other versions i tested later... objects that has "movable proxy ON" don't update correctly (i think instanced geo or lights)

is something that i am missing?

my simple workflow is in octane properties... i turn on movable proxy to objects that needs to be updated because they rotate, change or something... to be safe.
and that worked perfectly in 2018.1.2 and earlier versions i used

... but after plugin 2018.1.2.. the new ones i tested.. that couldn't work anymore so clean and nicely.

why is that? it happened to like 3 or 4 versions i tested (2018 and 2019 both) and it forces me to go back to 2018.1.2
Thanks in advanced

Hi javierluisbravo,
could you share a movable proxy scene issued please?
this issue coming from OctaneRender for 3ds max v2018.1.2 - 7.06, Is it correct?
Regards
Paride

The problem is the scatter of some geo instances and LIGHTS and the refresh of their position based on the real scene (even they are set as movable proxy!)
I notice this as i have ALL linked to a dummy that rotates and move . The problem is that some instanced elements don't update correctly unless i force in that frame a REBUILD scene.

Octane for 3dsmax 2018.1.2 7.06 => WORKS PERFECT with "use same scatter node for comp instances: CHECKED"
Octane for 3dsmax 2018.1.3 7.16 => NOT WORKING PROPERLY with "use same scatter node for comp instances: CHECKED"

Octane for 3dsmax 2019.1.5 8.14 => NOT WORKING PROPERLY with "use same scatter node for comp instances: CHECKED"
Octane for 3dsmax 2019.1.5 8.15 => NOT WORKING PROPERLY with "use same scatter node for comp instances: CHECKED"

Having "Use same scatter node for compatible instances: unchecked" FIXES the problem... But what's the point having that off? as in version 2018.1.2 7.06 works great with that ON/CHECKED. Why it STOPPED working after that version? All the versions i tried after that on didn't work properly.

Here the scene. Max 2018: https://we.tl/t-ZmlLIAJUCS (check the last shot where it's more visible the problem)

(this is related with this post: viewtopic.php?f=81&t=72705)

mbetke wrote:Can't render with this release. Using 431.86 Studio Drivers. As soon as the Octane Viewport opens, 3ds max nearly freezes and I have to click the red x several times until I get the whole program closed.
I didn't set a GPU to low priority because it was never necessary and I always had a smooth interaction.

EDIT: Updated to the latest Studio Driver. Problem persists. All displays nice until I click something in the viewport. Then endless lag and no interaction.

coilbook wrote:Hi Paride,
can you please report bugs with new volume behavior so they 'll finally fix it. It's much darker, light doesnt travel through it well and it leaves dark grid artifacts on the mesh, Scene is attached thanks

I attached the scene please go to frame 620 and open cotane viewport

javierluisbravo wrote:Hi paride,

Could you see the bug about instancing not refreshing properly for certain times of objects?
Could you open the file i sent to you?

kind regards,
Javier