Tweet
The nightly builds folder from today (2015.09.12) has a new build (26244) with a new command called "vray.vrscene.import" (you can find it in the V-Ray menu and tool-box, right below the create proxy command),
which is able to import a .vrscene file into MODO items.
This is an initial version so it has a lot of limitations, but hopefully it can still be useful.
I've tested mainly with .vrscene files exported from 3ds Max. .vrscene files exported from Maya won't work most likely.
Here are some notes:
- Geometry import
- Light import
- Material/texture import
- Render settings import
- Camera import
The import command will write various warnings in the Event Log, so you can take a look at it for more information.
I am on vacation next week, and will be back on 2015.09.23. I hope you can still find the import command useful until then.
Greetings,
Vladimir Nedev
which is able to import a .vrscene file into MODO items.
This is an initial version so it has a lot of limitations, but hopefully it can still be useful.
I've tested mainly with .vrscene files exported from 3ds Max. .vrscene files exported from Maya won't work most likely.
Here are some notes:
- Geometry import
- Only triangular meshes are imported (no V-Ray proxy, meshes with sub-division or displacement);
- If the mesh has a shear transformation it will be ignored ( I don't know how to set this type of transformation in the MODO locator;
- The UV channel with index 1 from 3ds Max is named "Texture". All the rest are called vrscene_map_X, where X is the channel index.
UV channels from Maya should have the same names as in Maya.
- Meshes are imported as "Static Mesh", so they are made of only triangles. It seems some parts of the MODO code don't work correctly with static meshes, for example :
- the scene scale is wrong, the .vrscene file DOES contain information about the real-world scale of objects, but if I fix geometry scale, I also need to fix all parameters that are in world units
(like ambient occlusion/dirt texture distance, reflection dim distance, etc...) so it is not trivial;
- If the mesh has a shear transformation it will be ignored ( I don't know how to set this type of transformation in the MODO locator;
- The UV channel with index 1 from 3ds Max is named "Texture". All the rest are called vrscene_map_X, where X is the channel index.
UV channels from Maya should have the same names as in Maya.
- Meshes are imported as "Static Mesh", so they are made of only triangles. It seems some parts of the MODO code don't work correctly with static meshes, for example :
- right clicking a mask in the shader tree and selecting "Select polygons" won't work;
- when a new texture is created, its texture locator is set to "Cubic" as if the geometry in the scene has no UV maps;
Both of these problems can be fixed by selecting all imported geometry, right clicking on it and selecting Convert -> Mesh. This will also allow you to assign new materials to them;- when a new texture is created, its texture locator is set to "Cubic" as if the geometry in the scene has no UV maps;
- the scene scale is wrong, the .vrscene file DOES contain information about the real-world scale of objects, but if I fix geometry scale, I also need to fix all parameters that are in world units
(like ambient occlusion/dirt texture distance, reflection dim distance, etc...) so it is not trivial;
- Light import
Didn't have time for this, so only Rectangular Portal lights are imported, nothing else.
- Material/texture import
Standard materials from 3ds Max are NOT imported, as well as the V-Ray material when exported from V-Ray for Maya (as the export code there creates a more complex representation of the material).
I've tested importing the following materials, exported from V-Ray for 3ds Max:
- V-Ray Material
- V-Ray Blend Material
- V-Ray Light Material
- V-Ray Override
- V-Ray Skin
Bump mapping is imported but only from a bump map (not normal map) and the bump amount is probably wrong.
I've also added UI for a few more textures from the V-Ray SDK that get exported from V-Ray for 3ds Max.
Object properties (visibility to reflection/refraction/etc.) and V-Ray Object Propeties (GI mult., matte surface, alpha contribution, etc.) are not imported, but it shouldn't be hard to do add them later on.
UV mapping import is very basic. Only 3ds Max's "Explicit Map Channel" mode is supported, and only some of its parameters. UV mapping from Maya won't be imported at all.
I've tested importing the following materials, exported from V-Ray for 3ds Max:
- V-Ray Material
- fog color is not imported correctly because it depends on scene scale;
- use environment override is imported as unchecked, as V-Ray for 3dsMax/Maya don't export it;
- V-Ray 2-Sided Material- use environment override is imported as unchecked, as V-Ray for 3dsMax/Maya don't export it;
- V-Ray Blend Material
- the sub-materials and their textures get added in the Shader Tree, but the actual connections are made in the Schematic, as the exporter doesn't allow this type of setup yet.
I did it like this, so the base material's diffuse texture can be seen in MODO's OpenGL view-port;
- V-Ray FastSSS2I did it like this, so the base material's diffuse texture can be seen in MODO's OpenGL view-port;
- V-Ray Light Material
- V-Ray Override
- V-Ray Skin
Bump mapping is imported but only from a bump map (not normal map) and the bump amount is probably wrong.
I've also added UI for a few more textures from the V-Ray SDK that get exported from V-Ray for 3ds Max.
Object properties (visibility to reflection/refraction/etc.) and V-Ray Object Propeties (GI mult., matte surface, alpha contribution, etc.) are not imported, but it shouldn't be hard to do add them later on.
UV mapping import is very basic. Only 3ds Max's "Explicit Map Channel" mode is supported, and only some of its parameters. UV mapping from Maya won't be imported at all.
- Render settings import
Most render settings are imported EXCEPT:
- environment
- render elements
Note that V-Ray for 3ds Max doesn't export the AA filter, and probabilistic lights, so these can't be imported from a .vrscene file created in V-Ray for 3ds Max yet.
- environment
- render elements
Note that V-Ray for 3ds Max doesn't export the AA filter, and probabilistic lights, so these can't be imported from a .vrscene file created in V-Ray for 3ds Max yet.
- Camera import
- The camera position and FOV, as well as physical camera settings are imported;
- Standard DOF (without physical camera), film fit, physical camera focus distance are not imported, so if you have DOF on a physical camera you will need to fix the focus distance;
- Standard DOF (without physical camera), film fit, physical camera focus distance are not imported, so if you have DOF on a physical camera you will need to fix the focus distance;
The import command will write various warnings in the Event Log, so you can take a look at it for more information.
I am on vacation next week, and will be back on 2015.09.23. I hope you can still find the import command useful until then.
Greetings,
Vladimir Nedev
Comment