It can easily be replicated, at least here it can:
1 . Open a scene which contains VRay elements in Max on a computer that does NOT have VRay installed, ignoring all the warnings about missing dlls etc.
2. Save the scene from the non VRay computer.
3. Now try opening the scene on a computer that does have Vray installed.
At this point Max fatal errors and closes. Is this a known problem? You could argue of course that my non VRay colleagues shouldn’t be opening my VRayed scenes on their nasty little single proc, scanline rendering boxes anyway… But they have.
I’m using Max 8 SP1, XP Pro SP2 and VRay 1.47.18.
Thought I’d better mention this is case no-one else had come across it.
I haven’t heard of this specific problem, but a possible workaround is to merge the contents into a new scene instead of trying to open the file directly.
Yeah, I tried that and it crashes if any of the VRay objects are included in the merge. The only solution I’ve found is to open the file again on the non VRay machine, apply standard materials to everything, delete VRay lights, modifiers etc. and assign scanline as the renderer then resave. It can then be opened in Max+VRay again but obviously I’m back to square one as far as lighting and materials are concerned.
Try installing VRay free on those other machines. It might be just enough to prevent the scenes from getting messed up. I’ve had no file-level problems when bringing files originally done with VRay Free into VRay Advanced (although rendering results usually differ).
Thats sounds like a good idea, better still if I install the current VRay advanced. It won’t work for rendering etc. because there aren’t any licences left on the server but at least it won’t corrupt my files. I’ll try it now.
Thanks Dynedain.