V-Ray Next for Rhino, update 2 is now available!
It can be download here:
download.chaosgroup.com
After installation, you will find more detailed info about the changes in the ‘VRayForRhinoReleaseNotes’ and the ‘changelog’ files:
.\Chaos Group\V-Ray\V-Ray for Rhinoceros\VRayForRhinoReleaseNotes.html
.\Chaos Group\V-Ray\V-Ray for Rhinoceros\changelog.txt
Best regards,
Konstantin
Script Access
- A new Render() method is implemented. It is the better alternative to starting a render using the Rhino command. Set its parameter ‘timeout = -1’ to ensure the call is synchronous
- No extra plugins will be fetched when attempting to retrieve material assets
- A way to start V-Ray rendering in Grasshopper via C# or a Python script is implemented
- A way for saving .vropt files via script or command is implemented
Other Changes & Bug Fixes
- Material using a diffuse texture blended with the diffuse color via the Diffuse Multiplier are now displayed correctly in the Rhino viewport
- Information about the V-Ray version and the render mode is now stored in a new .vrscene ‘plugin’ called ‘InfoRenderEngine’
- Changing an IES Light’s file now correctly triggers an interactive update
- The Rhino ground plane can now use a Wrapper material
- Light Cache map files can now be manually saved
- Light Cache map files are now correctly displayed in the Irradiance Map Viewer tool
- Modifying a custom Sunlight during interactive rendering no longer breaks its connection to the Sky in the environment
- Changing a 3rd party placeholder materials to a V-Ray shader no longer causes a crash
- A number of issues related to asset naming are resolved. Names differing only by special characters no longer cause a conflict when rendered
- Bitmap textures are displayed in the viewport even when wrapped in procedural maps. If for example a Color Correction is used the slotted Bitmap will still be visible on the viewport material. Note that the color corrections will have no effect on the preview
- Proxies, Clipper, Fur or Mesh light created within a block are no longer deleted upon subsequent block editing
- Rendering in the viewport no longer produces black image when the Stereo toggle is enabled
- Opening a Rhino Template containing a V-Ray Dome light no longer causes a crash
- The V-Ray icon in the Rhino properties panel is updated
- Blend material changes now reliably trigger an update during interactive rendering
- Resolved an issue with rendering of Lights, Clipper and Fur in Rhino 5
- The initial path of the default V-Ray studio environment texture is no longer incorrect
- Initializing a batch render job with no V-Ray for Rhino license available no longer leads to a crash
- Render with Chaos Cloud added to the V-Ray / V-Ray Rendering menu
- Importing a Proxy Mesh during Interactive rendering no longer leads to a crash
- The render state in the Asset Editor no longer hangs after a render with VR camera and parallel projection is initiated
- Converting a Directional Light to a Sunlight via command now works as expected
- Alt + drag duplication of a light no longer hides the original until the action is completed
- A number of issues related to RPC objects are resolved. Asset textures gamma is now correct
- Resolved an issue with rendering when the license has been released prior to activating the V-Ray UI
- Starting a production or interactive rendering from the Rhino toolbar no longer prevents both Asset Editor and the render process from launching
- A number of issues related to the batch rendering of vrscene files are resolved