vrscene export

[timuckl]

Hi!

Is there a way to just export the vrscene file without directly rendering on the local machine. I want to create a script that exports the vrscene file and submits this to our renderfarm.

Best
Timo

[vladimir.nedev]

You can use the Export As... command.
I think it is scene.saveAs "D:\Untitled.vrscene" VRay true.
It won't allow you to choose the type of renderer (CPU or RT GPU), so that might be a problem, as the .vrscene is different when RT GPU is used.

I will add a dedicated Export .vrscene command with this and some other options. Not sure when this will happen. I will write back here.

Greetings,
Vladimir Nedev

[MildMustard]

Rebus has an option to render through Standalone. I have submitted a test scene from exported vrscene but somehow it doesn't pick up any textures and seems to use a default render setting. If I import the same vrscene into Modo, it also doesn't pick up the textures for some reason.

[vladimir.nedev]

Rebus has an option to render through Standalone. I have submitted a test scene from exported vrscene but somehow it doesn't pick up any textures and seems to use a default render setting.

Does Rebus indicate somewhere what version of V-Ray Standalone they are using ?
At the moment, the standalone that comes with V-Ray for 3ds Max/Maya doesn't include the material/texture plug-ins written specifically for V-Ray for MODO.
These plug-ins are still in active development, and since we release V-Ray for 3dsMax/Maya/MODO at different times, even if we did include them, it is very
possible that an older version would be used, resulting in renders that do not match what you see in V-Ray for MODO.
Ideally, Rebus should have an option to use the Standalone that comes with the V-Ray for MODO installation.

If I import the same vrscene into Modo, it also doesn't pick up the textures for some reason.

This is noted in the docs. The .vrscene import is implemented and will work (reasonably) correctly only for .vrscene files exported from V-Ray for 3ds Max.
The .vrscene file can include many different material, texture, BRDF and UVW plug-ins.
Some of these need to be translated to native MODO constructs, which takes time to code, so I've done it only for the most common case - .vrscene created from V-Ray for 3ds Max.

Also, note that a lot of the information about how things are arranged in the Shader Tree is lost when you export a .vrscene.
So, even if I do add support for importing .vrscene files created in V-Ray for MODO, not everything can be re-constructed to its original MODO scene form.

Greetings,
Vladimir Nedev

[MildMustard]

Ok thanks Vladimir, I guess I will need to wait for Rebus to load Vray for Modo rather. They cannot give me any info on it unfortunately...

[simonbjork]

Does Rebus indicate somewhere what version of V-Ray Standalone they are using ?
At the moment, the standalone that comes with V-Ray for 3ds Max/Maya doesn't include the material/texture plug-ins written specifically for V-Ray for MODO.
These plug-ins are still in active development, and since we release V-Ray for 3dsMax/Maya/MODO at different times, even if we did include them, it is very
possible that an older version would be used, resulting in renders that do not match what you see in V-Ray for MODO.
Ideally, Rebus should have an option to use the Standalone that comes with the V-Ray for MODO installation.

I'll contact them to see if they can add a dropdown were a user can select the standalone version. But how does that work in terms of licensing? If they already have standalone liceneses can they pick up the standalone that works with Modo or do they have to buy new licenses? This is a pretty huge deal for us that use online render farms if none of the render services that support .vrscenes could be used.

Also, I've asked them for Modo for VRay support recently but it didn't seem like it would happen anytime soon.

[vladimir.nedev]

I'll contact them to see if they can add a dropdown were a user can select the standalone version. But how does that work in terms of licensing? If they already have standalone liceneses can they pick up the standalone that works with Modo or do they have to buy new licenses? This is a pretty huge deal for us that use online render farms if none of the render services that support .vrscenes could be used.

Also, I've asked them for Modo for VRay support recently but it didn't seem like it would happen anytime soon.

V-Ray standalone requires only a Universal Render Node license, so the needed licenses will be the same, no matter where the standalone came from.

Greetings,
Vladimir Nedev

[simonbjork]

Great! Which version of standalone works with modo?

[vladimir.nedev]

Great! Which version of standalone works with modo?

The one that comes packaged with V-Ray for MODO will work best. Not sure how hard it would be for render farms to add support for it.

Greetings,
Vladimir Nedev

[simonbjork]

Ah, I see. Is it possible to get that version without purchasing the modo plugin?

Is the plan to add the modo specific plugins to the main version of standalone in the future?

[vladimir.nedev]

Ah, I see. Is it possible to get that version without purchasing the modo plugin?

You need to purchase it in order to be given download access to it.
Not sure what the EULA says about giving the installer to somebody who doesn't have a V-Ray for MODO UI license.
The V-Ray Standalone that comes with it doesn't need the UI license.

Is the plan to add the modo specific plugins to the main version of standalone in the future?

They should be in the vc101 builds of V-Ray Standalone, but due to a bug I think, are not in the other "vraystd_adv_" builds.
But the code for the MODO specific stuff might be old, it is very possible that it doesn't match the code that comes with V-Ray for MODO.

Greetings,
Vladimir Nedev

[simonbjork]

Hm, not sure I quite get how all of this works. I guess it's best if I ask Rebus to contact you (Chaos Group) directly and see if they can work something out.

I had hoped it would just magically work with a .vrscene. If they have to do a lot of Modo specific customization chances are that they might not do it as they didn't seem all that intrested (but I could be wrong).

I'll reach out to some other companys as well and ask if they have any plans for the modo specific implementation.

[Robert]

I noticed a problem with vrScene export and texture path. For example I used a windows machine to export and it set all path to desktop like C:/... However when opening the scene on OS X, I got the message that the texture was not found under the path, without any option to redirect it. Its frustrating. Both that there is no option and path are not relative to file.. they should !!!

[vladimir.nedev]

I noticed a problem with vrScene export and texture path. For example I used a windows machine to export and it set all path to desktop like C:/... However when opening the scene on OS X, I got the message that the texture was not found under the path, without any option to redirect it. Its frustrating. Both that there is no option and path are not relative to file.. they should !!!

Yes, the problem is with the importer actually, it must give you a dialog to browse for the file which cannot be located.
It is logged as an issue.

Greetings,
Vladimir Nedev