OTOY Forums

bug spotted on 4.9 with max2016

An object is having turbosmooth modifier.
And the turbosmooth modifier is set to iterations on render (Render Iters) checked.

Then the octane viewport is reseting itself. Samples go 0-1-0-1-0-1..................n!

Can't reproduce, all works OK for me... Are you able to share the scene?..

JimStar wrote:Can't reproduce, all works OK for me... Are you able to share the scene?..

Sadly I think I've written over the problematic scene. It was errored.
It was reproducible after restart.

And now I tried on a fresh scene to reproduce but alas...

But I can confirm that I had those issue yesterday, even after reboot and restarting max.
turning off the "render iters" checkbox did the trick.

I'll share the scene when it's reproducible on my end, again

Same here

rv3d wrote:Same here

Hi,

Do you have a scene that can be used to reproduce the issue?

Cheers,
Azen

azen wrote:

rv3d wrote:Same here

Hi,
Do you have a scene that can be used to reproduce the issue?
Cheers,
Azen

Azen I suspect the problem might occur whilst using turbosmoothing at render time. Also spotted the bug way back in time while using hair (ornatrix)
And sometimes in animated scenes.
I know you cannot make the move on suspicions. But please do keep that in mind.
I'll try to keep an eye on it if I see and keep that scene whenever it's reproducible.

Dear Azen & Jimstar.

I'm happy to announce that I've managed to reproduce the problem once more.
As I suspected the problem lies between the moveable proxy setting and related modifiers in max.

So it's not only turbosmooth also optimize modifier is affected from this.
And any other modifiers that enables to use separate values for viewport and render.. Whist setting the objects as Moveable Proxy..
Like Ornatrix hair primitives (I couldn't reproduce that but I rarely see this problem with hair as well.)

I've just sent you a simplified scene (attached below)
The scene is a 3Dsmax 2016 file on 3.03.2 - 4.9 plugin. Nvidia driver 368.39.

If you happen to open up the scene and open octane viewport right away without touching anything. The problem should be seen instantly.
The render resets itself on octane viewport. This is not an issue with production render as far as I can see.

If you do see the problem. Lets move on.

Select an object in the scene.
There is an optimize modifier on each object provided.
it's setup in a way that optimizes the object in viewport but applies no optimize at render..

if you turn off the optimize modifier in all objects. The problem still exist. That is simply because of the object are in Moveable Proxy mode, along with Use obj render settings. And there is a problem with that connection. Either you turn off optimize or not...

To prove my point select all the objects and remove the instanced Optimize modifiers.
if you try to open up the octane viewport. The problem should have gone away.

Now Lets test this bug with turbosmooth.
Please select all the objects and assign a Turbosmooth modifier to all.
Iterations 1 ----- & ----- Render Iters uncheck
Test octane viewport. No problems so far.
Now check the Render Iters checkbox and set the value to 0.
Open up octane viewport
Boom you'll see the problem there.
if you happen to change the Render Iters to 1 - 2 or 3. Open up viewport.
It will take hell a lot of time to open up the viewport. And the problem will exist.

Now,
Open up render settings window. Under Render Settings.
Uncheck the Use obj render settings
Test the Oct. Viewport again. The problem is no more there.



So there you are.