Hi,
Not an urgent issue but rather a usability thing:
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.
cheers
Not an urgent issue but rather a usability thing:
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

3ds max 2016 latest SP, VRay latest stable release.
cheers
Comment