Crash when creating shademap for stereoscopic

[landrvr1]

Hello again, one problem solved last week with stereoscopic, but now a new one! I can create the stereoscopic image no problem at 9216x1536, but when I try and create a shademap file (Render shade map) I get a crash. I'm including the crash popup.
Tnx

[tashko.zashev]

Is it possible that the machine runs out of memory ? Please check that out.
If this is not the case then please send us your file to support@chaosgroup.com for a further troubleshooting.

[RobH22]

I'm having a similar problem. My specs are below for my system. If I drop the stereoscopic helper into the file and render I'm ok and can render successfully, but, as soon as I tick 'adjust resolution' any attempt to render crashes Max. I've tried it with a new blank file to eliminate any chance of mesh errors. I've also tried it with a few teapots in case an empty scene creates issues.

Finally, I'm working with a fresh install of Max and V-Ray from yesterday. So I have a very clean installation.

[matanov]

I'm having a similar problem. My specs are below for my system. If I drop the stereoscopic helper into the file and render I'm ok and can render successfully, but, as soon as I tick 'adjust resolution' any attempt to render crashes Max. I've tried it with a new blank file to eliminate any chance of mesh errors. I've also tried it with a few teapots in case an empty scene creates issues.

Finally, I'm working with a fresh install of Max and V-Ray from yesterday. So I have a very clean installation.

Can you share a simple scene reproducing the crash ?

[tashko.zashev]

I also did a few tests using the same software configuration to see if the crash will occur but without success. There isn't any useful information in the log or dump file, so there could be some relation between the other issue you have with the RT engine. We can check this issue as well during the remote session.
Details are sent through our ticket system.

[RobH22]

Yes, here is a very simple scene set up just to try to diagnose and reproduce the crash. I have a much more complex one that began to crash in which I began to delete things, element by element until it would render. When I deleted the stereoscopic helper, it would render. That told me it was the issue and I built the simple scene. And, sure enough, I can't get the simple scene to render with 'adjust resolution' ticked.

I think it might have to do with Max SP3 as I don't recall having issues with rendering it on SP2.

This simple scene will render for me if I "don't" tick 'adjust resolution'. But, as soon as I do, crash, every time.

[tashko.zashev]

Thanks for the scene file. We managed to replicate the crash here and it has something to do with the autosave option in high resolution renders in the VFB. When we have more information we will post here.

[RobH22]

Ok, good to hear you reproduced it. Makes me feel better that it's not just a broken install on my machine.

[vasil.minkov]

The problem occurs when the image is saved in the VFB history. As a workaround you could disable the "auto save" option in history settings.
The crash occurs with certain image aspects. If you increase the image width then it will crash even without stereoscopic helper.

[RobH22]

Great, that's not a painful workaround. I like VFB History but I can live without it for now. I'll try it and report back.

Thanks.

[RobH22]

Seems to be working. I disabled 'Autosave' in History. I then 'ticked' 'adjust resolution' in the stereoscopic helper. First render attempt crashed Max. I reloaded Max and now I've rendered 3 frames successfully. So I think I'm OK for now. Not sure why it crashed the the first time but maybe that purged something. Looks good for now and working.

[vasil.minkov]

The crash may also occur when the VFB tries to load particular image preview from history. If the crash is persistent you may change the VFB history location.

[tashko.zashev]

Hi Rob,

I would like to inform you that we managed to fix this issue for the next V-Ray update.

[RobH22]

Good to hear. Thanks for the update.

Now if I can just get the CUDA issues in iRay and V-Ray 'In process' resolved. Autodesk is looking at it with me. The same issue is in Max 2017 so it's not a Max 2016 issue only.