Stability of ipr in maxtoA

[Anonymous]

Hi

I appreciate this is probably going to be an impossible question to answer. I cant share anything to do with the scene as it is client work.

I have huge problems with the stability of the ipr in the Arnold render window.

It is almost guaranteed to crash every time I use it, at some point, could be seconds, could be minutes.

I am not sure if it is to do with the size of the scene, number of objects, shaders etc. Im not sure if the scene I am working on is heavy by todays standards. approx 800 objects, 30 million polys.

It crashes doing different things whilst using ipr.

As a short list it has crashed: isolating an object, changing decay of a light, trying to move a light, trying to move objects, moving the perspective view (not render view) changing values of lights etc.

these are all things that I would expect to be able to achieve using ipr. The ipr sometimes can run for a while, in minutes, or crash quickly.

I have a threadripper 32c/64t and have threads set to -20

128gb ram

So is this a kind of known problem or is there anything I can try to help stability?

Thanks

[lee_griggs]

What does the log file say when it crashes?

[Anonymous]

Here is the log file for the last crash, the log is set to debug

thanks

MaxACrash.zip

[thiago.ize]

Are you overclocking your CPU or using some tool to "optimize" CPU/motherboard/memory settings? See https://answers.arnoldrenderer.com/answers/23528/view.html for an example.

[thiago.ize]

Another thing to try is to set your options.enable_fast_ipr setting to false since there's a bug in 6.1.0.0 where that can cause crashes. See https://answers.arnoldrenderer.com/answers/29232/view.html for details.

[Anonymous]

Hi and thanks for the suggestions.

As far as I know I have just have default settings and no overclocking etc.

I tried your other suggestion but no luck unfortunately. Will keep trying to work it out tomorrow.

It seems to crash when not using ipr as well now, when attempting a higher resolution render. This is with subdivision and displacement turned off in the diagnostics panel.

[madsd]

Brute force is to delete half the scene, see if it improves, then keep dividing till you find the assets that cause the instability.
It could be legacy things, or modifiers, or something else.