Page 1 of 1

Why so janky?

Posted: Mon Feb 03, 2020 4:49 pm
by Antoncromas
Why is Octane implementation for Max is so bad?

Coming from C4D I straight up don't want to use it all.

Change light settings dont update the VFB out of the box. Octane material library button located inside the render settings for some reason. HUGE block of text when opening the render settings, I font even want to go over how terrible the default settings are that for some reason differ from other app for octane. Framebuffer is also absolutely terrible, not sure if the dev saw how the competing products look but this is really unacceptable. If I had to compare the Max implementation and look of Octane it would be Craigslist.

Re: Why so janky?

Posted: Tue Feb 04, 2020 10:52 am
by paride4331
Hi Antoncromas,
Change light settings dont update the VFB out of the box.
You would set "movable proxy": select the object > click right mouse > Octane properties > movable proxy.
You can also set it in Kernel panel > Autoupdate movable proxy
Octane material library button located inside the render settings for some reason
Octane LiveDB/LocalDB button is in Tools panel, it opens the Octane LiveDB/LocalDB windows like in SA.
Octane materials are available in the 3dsMax material editor as well.
Framebuffer is also absolutely terrible, not sure if the dev saw how the competing products look but this is really unacceptable.
Octane for 3dsMax Viewport info is availabel here: https://docs.otoy.com/3DSMaxH/3DSMaxPlu ... ewport.htm.
Regards
Paride