Annoying Difference Between V-Ray 2 and V-Ray 3

[thomasala]

We recently upgraded from V-Ray 2 to V-Ray 3.

In V-Ray 2 it was possible to have more asset editors open than there were licenses available and it would only alert if all the licenses were in use for rendering. This was good because not everyone at our company was rendering at the same time but it might have been necessary to check or work on settings simultaneously.

Now in V-Ray 3 it is only possible to open the same number of asset editors as there are licenses. This is a major impediment for our workflow. It's like requiring two DJs playing back-to-back to have two licenses for one mixer.

Please update V-Ray 3 to have this feature as in V-Ray 2, thanks!

[mihail_kuzev]

Hello,

Currently the Asset editor is available for V-Ray 3.0 for Rhino and SketchUp which use similar type of licensing.

For example the V-Ray 3.0 for SketchUp Workstation license includes:
V-Ray 3.0 for SketchUp interface (GUI) license.
V-Ray 3.0 AppSDK license.
V-Ray 3.0 Render node license.

And the V-Ray 3.0 for Rhino Workstation licenses includes:
V-Ray 3.0 for Rhino interface (GUI) license.
V-Ray 3.0 AppSDK license.
V-Ray 3.0 Render node license.

The V-Ray 3.0 for Rhino GUI and the V-Ray 3.0 AppSDK licenses are engaged when creating/editing scenes with V-Ray in Rhino and when working with the Asset editor.
The V-Ray 3.0 Render node license is engaged when rendering and when updating the material preview in the Asset editor.

The V-Ray 3.0 licenses are floating and are engaged per machine. This means that you can open multiple instances of Rhino with V-Ray and the Asset editor on a single computer and they will only take 1x V-Ray 3.0 for Rhino Workstation license.
However running Rhino with V-Ray on another computer at the same time will require an additional V-Ray 3.0 for Rhino Workstation license.

If the V-Ray 3.0 for Rhino workstation license needs to be used on another computer it will be possible to release it without closing Rhino - simply use V-Ray > Help > License > Release V-Ray License. The licenses can be reengaged simply by opening the V-Ray Asset Editor.

[thomasala]

Hi Mihail,

You are stating obvious facts and not addressing the real issue which is that floating licenses should be engaged only while rendering and not while the asset editor is open. The way it was with V-Ray 2 was good and the way it is now with V-Ray 3 is not.

[adesignaddict]

I gotta second that.

Our workflow relies heavily on our team being able to use the GUI/Asset Editor to prepare scenes on their workstation while others are rendering their own scenes simultaneously. In our opinion the GUI should be decoupled from the licenses and just have the rendering option disabled if there are more GUIs being used than available licenses. It's absolutely not viable for us to buy a huge amount of licenses just to use the GUI, even though only 2 or 3 machines are actually rendering.

[mihail_kuzev]

Hello,

Currently the Assets editor in V-Ray 3.0 for Rhino, SketchUp and Revit engages a V-Ray 3.0 Render node license when previewing the materials as they are being rendered with V-Ray on the go. This method provides a realistic preview of the materials and allows you to edit them at the same time.
The Workstation license that includes the GUI, the AppSDK and the Render node licenses allows working with the Asset Editor while simultaneously rendering (in production or interactive mode) on a single workstation.

In case you want to use a workstation only for rendering it is not necessary to open the 3d Application and engage the workstation license. It will be possible to export the scene to .vrscene format and render it with V-Ray Standalone using the command line:
https://docs.chaosgroup.com/display/...d+Line+Options

This way only a V-Ray 3.0 Render node license will be engaged. Also it will be possible to perform a distributed rendering with the V-Ray 3.0 Swarm render nodes using V-Ray Standalone however you will need to specify the IP addresses/Hostnames in the command line as Swarm tags are not supported in command line mode.

Please note that this setup might require extra V-Ray 3.0 Render node licenses because if you engage all the render node licenses that are included in the Workstation license it will not be possible to preview the materials in the Asset editor or perform a local rendering on the workstations that have the 3d applications running.

If you need more information on how to work with V-Ray Standalone or require assistance with the setup please write us to support@chaosgroup.com