3.5 beta 2 unhandled exception preparing objects

[Kim Laughton]

Had this come up last night through backburner - but seemed to be intermittent and some nodes perhaps not affected at all. The scene rendered fine on 3.4.

[Kim Laughton]

This actually seems to be ongoing with all the nodes - usually there are no problems, but then at random this error will occur and that node will stop rendering and only start again when I remove and reassign the job to it. It there any kind of log file I can send in?

[yavor.rubenov]

Hello,

Could you share the crashing scene or a part of it that still crashes?

Best regards,
Yavor

[Kim Laughton]

The problem with sending part of it is that given the nature of the crash it might be tricky to know which part of the scene is causing it. There'd be no way to test given that it can render a few frames fine before it shows up.

I tried zipping up the scene to send and max gives me this great error:



I could send the scene without maps and proxies - but maybe the error occurs when it tries to load a proxy or something like that?

[yavor.rubenov]

You could send the scene without the maps to our support - we'll try to reproduce it here if possible.

Apart from that - googling about the maxzip error message - maybe there is some problem with the destination of the archive? Are you trying to save on a network drive?

[Kim Laughton]

You could send the scene without the maps to our support - we'll try to reproduce it here if possible.

Apart from that - googling about the maxzip error message - maybe there is some problem with the destination of the archive? Are you trying to save on a network drive?

Tried the zipping again to a local drive - but no luck there either -_-

Here's the scene without any extras: www.kimlaughton.com/misc/main48.zip

This is from the log:



(I can send the full thing if needed?)

[Zdravko.Keremidchiev]

The crash seems to occurs locally as well. We'll investigate further and let you know as soon as we get any update.

[Kim Laughton]

The crash seems to occurs locally as well. We'll investigate further and let you know as soon as we get any update.

Ah - great, thanks!

[Kim Laughton]

Wondering if there is any way to force max to restart after a crash when rendering through backburner? I'm 20% into the animation now so don't want to go back to the previous version of Vray, but often wasting whole nights of rendering because the scene crashes early on and I'm not there to restart that node.

[vlado]

Actually we have a fix for this already; if you want to get it, please email me to vlado@chaosgroup.com

Best regards,
Vlado

[Kim Laughton]

Actually we have a fix for this already; if you want to get it, please email me to vlado@chaosgroup.com

Best regards,
Vlado

Oh that's super amazing, thanks!! Mailing!

[chris-x//]

I tried to install beta 3.50.02 and that's an instant max crash for me. Not matter the scene, reboot, reinstall... Going back to 3.50.01 is okay.
Online licensing is active, I can access the UI, but when I launch a render, whatever the scene, even empty, max crashes.


Max 2016 SP4 - Win 8.1 64bits

Having some bump issues in RT, just needed to change beta after some rt forum reading.

Seems the closest thread to my problem, too many threads.

Thanks

[Svetlozar Draganov]

Please contact us at support@chaosgroup.com and include a link for reference to this page.
We may need to connect remotely to see what's going on.

[vlado]

Same reply to you - please email me to vlado@chaosgroup.com with your 3ds Max version and hopefully we have a fix for it.

Best regards,
Vlado