Hi guys,
There is a new Stable nightly build of V-Ray Next for Rhino available.
The nightlies download page can now be accessed by anyone with chaosgroup.com account.
Here’s a link to the latest build:
V-Ray Next for Rhino, stable 20200226
Note that it’s not recommended to use the nightly builds in production.
They are for test purposes only.
Scenes setup with the nightly build might not behave the same way when loaded in the final official build.
Regards,
Konstantin
Grasshopper
- The UV channels of Rhino objects referenced in the Grasshopper definition are now preserved
- V-Ray Bitmap component implemented. It allows material texturing to be done directly in V-Ray for Grasshopper. The component also enables UV channel selection and texture placement modifications
- Vertex Color mode added for the Bitmap component. Use it to colorize materials with the vertex colors of a mesh
- The V-Ray Timeline component can now be resized
- Grasshopper animations exported to Rhino no longer override the existing Rhino animation (recording). Use the Animation Source switch in the V-Ray Animation settings to select the one to be rendered
- Grasshopper camera animations sent to Rhino can now have animated focus distance
- Color or texture variations can now be introduced among V-Ray Instancer items. Use a Multi-Sub texture in ‘Random by render ID’ mode connected to the material to achieve it
- The Render in Project component now correctly sends the Infinite Plane to Rhino
- The animation preview of the V-Ray Timeline component can now be interrupted with the Esc key
- ‘Look Through Camera’ context menu function added to the V-Ray Camera component
- The V-Ray Light Rig Dome no longer loses its texture when disabled and then re-enabled
- Connecting a V-Ray Geometry component to the Infinite Plane geometry input no longer causes issues
- Disabling the Camera no longer interrupts the interactive rendering process
- The V-Ray Material Simple component now exports vrmat files correctly
- A number of issues with the V-Ray Instancer component are resolved
- Proxy Meshes loaded in Grasshopper now display a bounding box preview in the Rhino viewport
- Embree is now used for Fur rendering in Grasshopper. Proxy Scenes with Fur will render faster
- A number of issues related to interactive rendering scene updates are resolved
- The ‘Manage Collection’ option can now be used for the Material from File component
- The Material from File component no longer allows file path changes while this data is derived from an input
- Displacement can now be applied to Grasshopper objects. Use a Material from Project component referencing a project material with displacement enabled
- A number of issues related to loading Library materials in Grasshopper are resolved
Script Access
- Allow retrieval of top-level only plugins
- 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
- 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