I recently had a crash after saving a VRIMG to disk via the VFB (saving in history, not exporting as file). After a hard reset I started max again, then opened the VFB and max+VFB froze. Did it two more times, then manualle deleted the VRIMG file in the file explorer prior to opening the VFB and the issue was gone.
Sadly I don’t have the VRIMG anymore, also not in the trash :-(. Anyways I thought it was strange that even when crashing AFTER saving (right after) the VRIMG somehow got currupted. Maybe you want to take a look at how the VFB behaves when there’s a corrupted image in the history. Maybe there can be done some optimizations so it doesn’t freeze the host app and the VFB.
3ds max 2016 latest SP, VRay latest stable release.
Could you give us more details regarding the crash.
Does the crash occur on a specific scene or you have noticed that it happens on other ones also?
What was the size of the image you were saving?
Did you have any specifiy render elements switched on?
Can you confirm that the crash occured just after the vrimg file was saved and are you sure there was vrimg file after the crash in your the history folder?
The crash occured only on one specific scene (don’t know which one though - sorry) and didn’t re-occur as of yet. This may hint at some external influences though I couldn’t pinpoint anything that could have triggered it.
The size of the image was quite big, I don’t remember the exact dimensions but it was at least 8k and with several render elements. I know this is all vague and I regret not saving more information on this and it’s some time ago now…
I can confirm the crash occured after saving the VRIMG since an “emtpy” image showed up for a brief moment in the history.
Thanks for the feedback. We will take a note but there isn’t much we could do without reproducing the issue. If you notice any unexpected behaviour, please write us back with more details.