We just switch to Vray 2.30 with 3dsMax 2013
On some scenes, we had problems saving our files as 16 bits or 32 bits exr, which is our usual workflow.
We nailed it down to the use of a refraction pass that was done in a previous version of Vray.
So a new scene would not give us any problems, but an old scene, or a new scene in which we would load presets, that in our case include different passes, would make a network rendering job save 8 bits only. The 16/32 bits save works fine on the local machine. Using the presets, and deleting the refraction pass, and replacing it with a new one works just fine..
That’s odd as nothing has changed in this regard in the 2.3 build. Can you get me a scene that has the problem along with the steps necessary to reproduce them to vlado@chaosgroup.com ?
We are having a similar issue but it looks like it is an issue with backburner 2013 and not vray.
I have submitted a bug report to Autodesk but they don’t seem to like touching backburner
Thablanch- Do you get the same error when you render the file in 2012 Vray2.3 and an older version of backburner?
We do not have 2012 installed, we switched from 2011 to 2013. We did not have any problems with 2011 refraction passes. As when deleting the Vray pass and replacing it, the problem goes away, I taught it was Vray related.. But Backburner could be the problem, but it is weird that it is on a specific pass… whatever.. got a workaround solution…
Found the problem on a scene that has no refraction pass. looks like the solution was only partial. have to investigate more. But, if anyone has a clue, feel free to share …
