V-Ray Next App SDK 4.30.01 Released

[kalina.maneva]

V-Ray Next App SDK 4.30.01 is now available for download.
(if you don’t have access, request it here: https://www.chaosgroup.com/vray/application-sdk#contact)

This release includes an upgrade to the latest version of V-Ray Next, plus many improvements and fixes (full Release Notes are below).
Please, update and let us know what you think!

Regards,
V-Ray App SDK Team

RELEASE NOTES - V-Ray Next App SDK 4.30.01


Highlights

• VRayRenderer is now thread-safe
• Added plugin categories and a new plugin categorization API
• Added new Optix (RTX) render modes (interactive and production)
• Added support for Node.js v.12
• Added support for Electron v.5 and v.6

New features

• Added new functions to manage the Optix devices: VRayRenderer.getComputeDevicesOptix() and VRayRenderer.setComputeDevicesOptix()
• Added bucketReadyHasBuffer and progressiveImageUpdateHasBuffer properties to VRayRenderer to control if VRayImage instances are to be received in OnProgressiveImageUpdated and OnBucketReady event handlers
• Added VRayRenderer.setBitmapCache(bool) to control if bitmap textures are to bе stored in memory and not unloaded and reloaded again on the next render
• Added Plugin.getIntegerID() to allow easier caching of plugin instances in maps, etc.
• Added examples for creating triangle meshes (trimesh); made numerous example updates
• Updated ScannedMaterialParams struct with new members and features

Bug fixes

• Fixed low CPU utilization during light cache calculation
• RenderView.use_scene_offset is no longer forced to 0 if the user has explicitly set it
• Fixed a bug where a change in the name of a plugin instance read from a .vrscene file removes all references to it from plugins in the .vrscene file
• Fixed a bug where geometry preview of vrproxy (in the ScenePreview API) was wrong with more than one object in the file
• Fixed a bug which caused auto exposure and auto white balance to return 0 in productionCuda and productionOptix render modes
• Mouse+keyboard camera movement inside the VFB window in interactive mode now works correctly with different current frames / at different times
• [.Net] The binding is now compatible with strongly named assemblies
• [Python] Added the missing pickPlugins() method
• [Python/macOS] Fixed module loading issues on macOS