Hello everyone,
As you probably noticed from the title, we’ve added initial support for importing the contents from a V-Ray Scene (.vrscene) file as native objects in Cinema 4D with V-Ray 6 Update 2. This means that you should be able to export a .vrscene file from any DCC application with V-Ray installed as well as any CAD application with Enscape installed and import it in Cinema 4D in an editable state as long as the object is implemented in some compatible form in V-Ray for Cinema 4D.
As you can imagine, this could be a really powerful tool, giving you a lot of flexibility, especially in cross-collaborative environments where your work is not tied only to Cinema 4D as your main software and easily transfer materials, lights, cameras etc.
With that being said there are some important notes I’d like to share with you for better understanding what to expect from the V-Ray Scene import tool.
In general, everything that could be imported but doesn’t exist as a native object in V-Ray for Cinema will be imported as a blackbox object. Those objects are renderablebut not editable since they’re not imported as native objects and will have no parameters.
It’s important to note that importing V-Ray Scenes exported from other and especially older V-Ray integrations would probably never be perfect, but we will do our best to make it as good as possible. Since this is aninitial support, please keep in mind that the V-Ray scene you’re importing might not have the exact same resultbut should be close enough for achieving the same result with some additional tweaking inside Cinema 4D.
Unsupported data import and known limitations
Let us know about your experience here on the forums or report your findings to our support teams.
Looking forward to your feedback,
Thank you!
As you probably noticed from the title, we’ve added initial support for importing the contents from a V-Ray Scene (.vrscene) file as native objects in Cinema 4D with V-Ray 6 Update 2. This means that you should be able to export a .vrscene file from any DCC application with V-Ray installed as well as any CAD application with Enscape installed and import it in Cinema 4D in an editable state as long as the object is implemented in some compatible form in V-Ray for Cinema 4D.
As you can imagine, this could be a really powerful tool, giving you a lot of flexibility, especially in cross-collaborative environments where your work is not tied only to Cinema 4D as your main software and easily transfer materials, lights, cameras etc.
With that being said there are some important notes I’d like to share with you for better understanding what to expect from the V-Ray Scene import tool.
In general, everything that could be imported but doesn’t exist as a native object in V-Ray for Cinema will be imported as a blackbox object. Those objects are renderablebut not editable since they’re not imported as native objects and will have no parameters.
It’s important to note that importing V-Ray Scenes exported from other and especially older V-Ray integrations would probably never be perfect, but we will do our best to make it as good as possible. Since this is aninitial support, please keep in mind that the V-Ray scene you’re importing might not have the exact same resultbut should be close enough for achieving the same result with some additional tweaking inside Cinema 4D.
Unsupported data import and known limitations
- Animations and animated geometry
- Render Settings (including ACEScg, OCIO, and Color Mapping) - not importable
- Chaos Scatter - not importable
- Render Elements - not importable
- V-Ray Environment fog - not importable
- V-Ray Clipper - imports as blackbox, renderable
- V-Ray MeshLight - imports as blackbox, renderable
- V-Ray Renderable Spline and hairs - imports as blackbox, renderable
- V-Ray Enmesh - imports as blackbox, renderable
- V-Ray Volume Grid - not importable
- V-Ray Particles - imports as blackbox, renderable
- Instanced objects (instancer) - partial import, no animations, blackbox
- Light and Shadow linking - not importable
- Custom User Data (UserAttributes) - not importable
Let us know about your experience here on the forums or report your findings to our support teams.
Looking forward to your feedback,
Thank you!
Comment