V-Ray 3.60.05 is available for download

[alexander.kazandzhiev]

Hello,

An updated build V-Ray 3.60.05 is now available with a number of fixes that have accumulated over the past few months. The changelog follows.

Build 3.60.05 (official) (15 November 2018 )
==============

New features:
(*) V-Ray: Cryptomatte support for DWA compressed OpenEXR files;
(*) VRayVolumeGrid: Add a getFrameInfo() MAXScript function that retrieves the currently loaded frame info string;
(*) VRayVolumeGrid: Support XForm modifiers in Volumetric render mode;

Modified features:
(*) VRayHDRI: Improved performance for tiled .tx and .exr textures;
(*) V-Ray: Support for the <frameNum> tag in VRayHDRI;
(*) V-Ray: When rendering spherical cameras, the z-depth channel for deep OpenEXR images should be the distance from the camera;
(*) VRayMDL: Improve anisotropy precision in MDL;
(*) VRayScene: Implement support for VRayCryptomatteElement;
(*) VRayVolumeGrid: Allow grid Channel Smoothing to be applied over channels with any value range;
(*) VRayVolumeGrid: Apply the Smoothing Random Variation over all voxels regardless of the Smooth Threshold;
(*) VRayVolumeGrid: *.aur cache latest format support and multi-threaded import;
(*) VRayVolumeGrid: MaxScript interface for getting grid data and loading render presets directly from the volume grid nodes;
(*) VRayVolumeGrid: Support for the new transformation model of OpenVDB caches from FumeFX 5;
(*) VRayVolumeGrid: Particle Shader rendering of PFlow particles in VRScenes;

Bug fixes:
(*) V-Ray: Artifacts with adaptive lights in a certain interior scenes;
(*) V-Ray: Less than normal samples are calculated with Use camera path with Irradiance map GI engine;
(*) V-Ray: MAXScript auto-load script error with 3dsMax2018.4;
(*) V-Ray: Noisy glossy refraction with BF\LC and Retrace turned on in a specific scene;
(*) V-Ray: Improve selection of VRayPhysicalCamera and VRayLight in the viewport;
(*) V-Ray: V-Ray Standalone crashes with specific scene with MDL materials and Scanned materials;
(*) V-Ray: Unhandled exception error with particles and camera motion blur enabled;
(*) V-Ray: Unhandled exception when rendering matte reflections;
(*) V-Ray RT: Changing the "enabled" parameter of a light is not updated properly;
(*) V-Ray RT: Difference in render result with V-Ray Cloud when using MultiTexture;
(*) V-Ray RT: Flickering in animation with 3ds Max animated Noise modifier;
(*) V-Ray RT: V-Ray exposure control is not working with Physical Camera;
(*) V-Ray RT: Sequence render output is saved twice;
(*) VRayFastSSS2: Material in Raytraced (refractive) mode is lit by excluded V-Ray light with Cast Shadow disabled;
(*) VRayGLSL: Error when merging scenes with GLSL shaders;
(*) VRayGLSL: LLVM produces code for Skylake processors that causes crashes;
(*) VRayGLSL: Shaders use too much memory per thread;
(*) VRayGLSL: Wrong shadow calculation when used as opacity map;
(*) VRayScene: Crash with .vrscene sequence and missing first file;
(*) VRayToon: Toon line disappears with big FOV camera values;
(*) VRayVolumeGrid: Caches containing digits after the # format can not be loaded;
(*) VRayVolumeGrid: Caches containing a minus/dash sign before the # format can not be loaded;
(*) VRayVolumeGrid: Caches with particle groups render the mesh for each group;
(*) VRayVolumeGrid: Can't load OpenVDB files whose "file_voxel_count" metadata is 0, though they contain active voxels;
(*) VRayVolumeGrid: Cannot render a simulator with modifiers;
(*) VRayVolumeGrid: Particle shader particles exported to vrscene are not rendered;
(*) VRayVolumeGrid: The VRayVelocity render element is not rendered in Volumetric Geometry mode if Motion Blur is off;
(*) VRayVolumeGrid: When exporting to a .vrscene the 'etmult', 'brdfscatter', 'bounces', 'difmul', 'fadebylevel', 'displvelfade', 'usecolormap' and 'colormap' parameters are missing;
(*) VRayVolumeGrid: Wrong velocity direction and motion blur with OpenVDB files from FumeFX;
(*) VFB: 3ds Max crashes when copying an image from VFB to the clipboard and then copying text from Layer/Scene explorer;
(*) VFB: Freezes randomly if playing with it while rendering;
(*) V-Ray Standalone: Lens effects from vrscene are not applied with -display=0 option;

Best regards,
Alexander

[joconnell]

This'll make a lot of people happy

(*) V-Ray: Artifacts with adaptive lights in a certain interior scenes;

I take it with the volume grid the memory instancing of vdb's didn't make it in this time?

[kostadin.petkov]

Hello,
"I take it with the volume grid the memory instancing of vdb's didn't make it in this time?"
This has always been like that with instancing and copies, cache files are always loaded once no matter how many volumes use them.
You may be talking about our native support for VDB, where we did not convert it our own internal format(which results in less memory consumption). Unfortunately this is now available in VRayVolumeGird in V-Ray 3, however it is available Phoenix FD for V-Ray 3.

Hope that helps

[Svetlin.Nikolov]

Just to clarify (there also seems to be a typo: "now" vs."not"):
- Loaded caches were shared in RAM in both Phoenix and VVG
- I implemented sparse VDB grid loading in the beginning of 2018, but V-Ray 3 code is long long behind, so it's practically incompatible - so this is only in Phoenix and V-Ray Next, but in V-Ray 3 sparse VDBs will take so much RAM as if they were dense.

Cheers!

[joconnell]

Yep, just confirming, thanks guys!

[spyzor]

Yes !!!!

I can render my particles .
Didn't see the update when it came out.

Thanks !

[anthonyh]

Always appreciate the updates. Keeps us ticking until the higher ups let us upgrade.