So just upgraded from 2016 to 2018.4 on the ws and rendernodes and am running into a hopefully small issue;
Max2018 has a "save file" button under the main render button in the render dialog. I never use the 3ds max save dialog so ignored it and saved the file in the vray tab and sent it to backburner to do some testrenders on the rendernodes.
This gave a backburner error that the rendernode "couldn't read/write file type: c:\users\....."
- When saving only a jpg the file would be saved to the network location but backburner still gave the error and restarted.
- When saving a vimg it would give the error at the beginning and try and restart.
The "fix" which I have found is to also use the "save file" button and just save a jpg in the corresponding network folder additional to what I save from the vray framebuffer dialog in the vray tab.
Surely this isn't the new correct workflow?! Needing to save every render from two menu's to stop a backburner error?
Had a search but couldn't find this anywhere
Max2018 has a "save file" button under the main render button in the render dialog. I never use the 3ds max save dialog so ignored it and saved the file in the vray tab and sent it to backburner to do some testrenders on the rendernodes.
This gave a backburner error that the rendernode "couldn't read/write file type: c:\users\....."
- When saving only a jpg the file would be saved to the network location but backburner still gave the error and restarted.
- When saving a vimg it would give the error at the beginning and try and restart.
The "fix" which I have found is to also use the "save file" button and just save a jpg in the corresponding network folder additional to what I save from the vray framebuffer dialog in the vray tab.
Surely this isn't the new correct workflow?! Needing to save every render from two menu's to stop a backburner error?
Had a search but couldn't find this anywhere
Comment