Tweet
Max 2017 crash on render completion
Well, not really 
I used a title I saw in the Problems subforum and since I can't post there, I figured I'd comment here in case the info helps somebody.
It's always possible that I'm off the wall of course.
1. I never had a crash with the demo VRay, so try that too in case you have a borderline dongle.
2. If you still crash, you probably use some VRay module I haven't tried (that maybe falls in the category I describe below?), or you have some other plugin that misbehaves.
The only unexplained crash I had up to now with Max 2017, was caused by a demo of Krakatoa. I tend to trust their software and since the same version demo worked great in Max 2016. it got me curious.
I don't remember the details now but looking at Max's dump file, the crash was always in some basic Microsoft string routine.
Looking at the 2016 vs the 2017 plugin, the 2017 one was using the api-ms-win-core libraries implemented with the latest Windows kernel architecture changes.
Somebody, somewhere, did something wrong. I think (but am not sure) 3ds Max 2017 uses these libraries too and if so, it must be something off on the plugin's side.
I don't know if it helps pinpointing some problem but keep it in mind.
A useful reference to it I came across is here: http://www.nirsoft.net/articles/wind...e_changes.html
Regards.
I used a title I saw in the Problems subforum and since I can't post there, I figured I'd comment here in case the info helps somebody.
It's always possible that I'm off the wall of course.
1. I never had a crash with the demo VRay, so try that too in case you have a borderline dongle.
2. If you still crash, you probably use some VRay module I haven't tried (that maybe falls in the category I describe below?), or you have some other plugin that misbehaves.
The only unexplained crash I had up to now with Max 2017, was caused by a demo of Krakatoa. I tend to trust their software and since the same version demo worked great in Max 2016. it got me curious.
I don't remember the details now but looking at Max's dump file, the crash was always in some basic Microsoft string routine.
Looking at the 2016 vs the 2017 plugin, the 2017 one was using the api-ms-win-core libraries implemented with the latest Windows kernel architecture changes.
Somebody, somewhere, did something wrong. I think (but am not sure) 3ds Max 2017 uses these libraries too and if so, it must be something off on the plugin's side.
I don't know if it helps pinpointing some problem but keep it in mind.
A useful reference to it I came across is here: http://www.nirsoft.net/articles/wind...e_changes.html
Regards.
