Vray won't render a scene saved in 901 and opened in 10.1

[vandigital]

So any scene I saved with the old version of vray and 901 SP2 will not render in 10.1 MODO all you get is a black frame.

If I open the scene in 901 SP2 it renders fine.

Also if I created a scene in 901 SP2 and open in 10.1, save in 10.1 then reopen in 901 SP2 it also renders black. Also happens in 10.0.

[vladimir.nedev]

Can you send me the scenes in question. The one saved in 901 that doesn't render in 10.0 and the one saved in 10.0 that doesn't render in 901.
I've tried here on a simple scene and all seems to work fine. I also have a lot of unit tests (around 700 ) that are all saved in MODO 9 and I've test rendered them in MODO 10.

Note that MODO 902 SP3 fixes an issue where scenes saved in 10.0 (probably 10.1 as well) are recognized by 902 SP2 (and earlier) as being saved in earlier versions of MODO (before 901).
This means versions of MODO 9 before 902 SP3 will load a 10.0 scene incorrectly, assigning the incorrect values to some material channels that haven't been edited by the user.
For example, "match specular" will be set to OFF when the 10.0 scene is opened in 902 SP2, although it is ON when the scene is opened in 10.0.

I did change some V-Ray default values for the 3.01.02 version, which will affect old scenes, but I don't think they can have such a significant impact as you describe.

Greetings,
Vladimir Nedev

[vandigital]

I sent you an example

It wont render in either actually.

And the fur in that also gives crash error.

[vladimir.nedev]

I sent you an example

It wont render in either actually.

The scene is missing a camera and V-Ray for MODO will refuse to render without one.
Just add a camera and the render will start. V-Ray will pop-up an error dialog in this case, but you might have disabled it. The tricky part is that V-Ray uses one error dialog for ALL errors, so if you disable one dialog message, it will disable all of them.
I guess you know, but you can reset the automatic dialog behavior from "Preferences -> Application -> Reset "In the future..." messages".
Also the Event Log contains the error as well, so looking at it is helpful if rendering refuses to start.

The environment in the scene is set as invisible to all rays (gi, camera, reflection, refraction), so there is no light in the scene.

Not sure if the camera/environment were corrupted when the scene was saved.

In your e-mail you mentioned that " It doesn’t even load vray."
Do you mean the VFB ?
The 3.01.03 nightly version has a pretty significant rewrite of the VFB to support high DPI displays. There might be a bug in the code that loads the VFB settings from the .lxo file.
For me, the color corrections are placed in a strange place inside the VFB, resizing the MODO viewports will fix this, as a workaround. Or you can go back to the 3.01.02 version where these problems aren't present.

And the fur in that also gives crash error.

I will see what crashes exactly, but I suspect it is the MODO Render Cache API.
So most likely I won't be able to fix it and will have to report it to The Foundry.

Greetings,
Vladimir Nedev

[vandigital]

I will try again in that case however I didn't change anything in the version I sent you it was straight from 902 which rendered fine until I saved in 10.

Though this may be an issue with Version 10 as ive noticed other things going wrong as well...

Also the fur on that strap used to render fine in earlier versions of vray and modo. It was only your more recent betas that it gave the render cache crash error. So either luxology changed something or you did.

[vladimir.nedev]

Also the fur on that strap used to render fine in earlier versions of vray and modo. It was only your more recent betas that it gave the render cache crash error. So either luxology changed something or you did.

I haven't changed anything in my code related to MODO's Fur.
There is some instability in the MODO Render Cache API. Sometimes it works, sometimes it crashes on the same scene.
The crashes seem to be fixed in 10.1 but the returned data is not enough to reconstruct the hair. I've reported this on The Foundry's forum.

If you happen upon such crashes in the future, you can run the sdk.rcache.print command, if it causes MODO to crash, this means that the crash is in the Render Cache API, so it's better to report the problem directly to The Foundry, as I can't do anything to fix it.

Greetings,
Vladimir Nedev