V-Ray Next is now available for download! An overview video of the new features is available here:
Similar to V-Ray 3.x, many of the features will continue to be improved and refined throughout the V-Ray Next release cycle.
It’s been a while since we last had a paid upgrade and we now have more purchasing options that might deserve your attention - our sales team will be able to assist you if you email them at sales.software@chaosgroup.com; if you purchased V-Ray 3.x recently you might be eligible for a free upgrade.
Important note: V-Ray Next requires a processor supporting SSE4.2. If your CPU is close to 10 year old or older, please check if it supports SSE4.2
V-Ray Next (official)
=====================
New features:
(*) V-Ray: Require CPU with SSE 4.2 to support SIMD optimizations;
(*) V-Ray: Update the SDK to make greater use of SSE instructions for 3D vector, color and matrix operations;
(*) V-Ray: Update Embree to version 2.13;
(*) V-Ray: Add options for auto-exposure and auto white balance in the Camera section of the render settings;
(*) V-Ray: Add tooltip translation support for various languages;
(*) V-Ray: Add scripts for the 3ds Max Scene Converter (2017 and newer) for various scene elements to V-Ray ones;
(*) V-Ray: Add drag-n-drop support for V-Ray asset files onto the 3ds Max window (.vrmesh, .abc, .vrscene, .ies, .aur, .f3d, .vdb, .vrlmap, .vrmap);
(*) V-Ray: Show render progress on the Windows taskbar buttons;
(*) V-Ray: Support for the mesh vertex velocity internal interface in 3ds Max 2019;
(*) V-Ray: Add dialog to confirm file overwriting with Separate Render Channels;
(*) V-Ray: Cryptomatte support for DWA compressed OpenEXR files;
(*) V-Ray GPU: Implemented new rendering architecture resulting in better performance;
(*) V-Ray GPU: Add support for adaptive dome light;
(*) V-Ray GPU: Add support for volumetric rendering;
(*) V-Ray GPU: Support for BRDF mode of VRayGLSL’s PTX backend;
(*) V-Ray GPU: Re-organized the UI options;
(*) V-Ray GPU: Add support for glossy Fresnel;
(*) V-Ray GPU: Improved GPU 3D displacement;
(*) V-Ray GPU: Initial version of GPU dedicated UI (to be further simplified in next versions);
(*) V-Ray GPU: Initial support for VRayEnvironmentFog (without textures);
(*) V-Ray GPU: Initial support of VRayVolumeGrid (brute force probabilistic volume sampling only);
(*) V-Ray GPU: Initial support for VRscans (VRayScannedMtl);
(*) V-Ray GPU: Support for Bercon Noise texture;
(*) V-Ray GPU: Support for DoF with pinhole camera;
(*) VRayLight: New adaptive dome light option to help speed up rendering of interior scenes and IBL in general;
(*) VRayMtl: Add “Metalness” parameter for easy support of PBR workflows;
(*) VRayMtl: Add a texmap slot for the GGX GTR tail falloff;
(*) VRayDenoiser: Integrated the NVIDIA AI denoiser as an alternative denoising engine;
(*) VRaySwitchMtl: Add switch material for selecting sub-materials based on a texmap value;
(*) VRayHairNextMtl: Implement a new hair shader with melanin color control;
(*) VRayLightingAnalysis: Implement VRayLightingAnalysis render element;
(*) VRayLightSelect: Add “indirect”, “indirect diffuse” and “indirect specular” modes;
(*) VRayProxy: Add support for Alembic 1.7 layers;
(*) VRayProxy: Modifiers applied to VRayProxy objects are rendered correctly (the proxy is converted to a regular mesh);
(*) .vrscene exporter: Initial support for the native OSLMap in 3ds Max 2019;
(*) VFB: Add option to disable VFB resizing on image load;
(*) V-Ray Light Lister: Add control for VRayLights type;
(*) VRayMDL: Ability to manage include paths through MAXScript;
(*) VRayMDL: Support for UTF-8 resource file paths;
(*) VRayOSL: Support for OSL scene attributes;
(*) VRayOSL: Ability to attach textures to arbitrary OSL parameters;
(*) VRayOSL/VRayMDL: Allow adding shader include paths from UI;
(*) VRayPluginNode: Initial implementation of VRayPluginNode material and texture;
(*) VRayRenderTime: Per-pixel render time information render element (bucket sampler only);
(*) VRayScannedMtl: Add triplanar mapping option;
(*) VRayVolumeGrid: Direct loading of sparse VDB caches without resampling;
(*) VRayVolumeGrid: Support for relative cache paths in .vrscene files and the -remapPath option in V-Ray Standalone;
(*) VRayVolumeGrid: Integrate new velocity-based grid interpolation method;
(*) VRayVolumeGrid: Support XForm modifiers in Volumetric render mode;
(*) vdenoise.exe: Implement GUI for use without command-line parameters;
(*) VRayDenoiser: Ability to denoise multiple render elements in a single pass (also added denoising on/off in various other REs);
(*) vrstconvert.exe: Add the deep reader and converter for .vrst files to V-Ray for 3ds max and Nuke installations;
Is there support for fog in IPR CPU?
Is there a way how to use cryptomatte element in Photoshop? Not sure if there is some plugin or something, but this element would be handy even for rendering pictures, not only animation.
It’s an official holiday in Bulgaria today, sorry for the late reply.
Fog support is still not in CPU IPR for the official builds; I know I did say that I will do it, and most of the code is done but it didn’t make it into the official release. I can get you a build to test if you like, though.
About Cryptomatte in PhotoShop, I believe there was some work done on one of the OpenEXR plugins for PhotoShop, but I have to dig out which one specifically.
thank you for reply. If you can send me some build for testing, it will be great. I have to done some work for a couple of weeks and then will buy Vray Next, cant change it now.
I will look at Open EXR if they say something about cryptomatte support, thank you.
And one little question about this forum: I notice for some reason dont get any notifications about someone replied to my threads. Didnt change any settings so dont know what is going on.
I am planing to buy vray next and have get some quotation from my local supplier, and also planning to buy a pc too, but i wonder if vray next stable, should i buy it?
Well I am planning on buying it asap. Was hoping to get my hands on it end of last month, but a bit of a delay in getting paid, but hopefully not long to wait now. As for it being stable. Hey every piece of software out there, is stable, unless you try doing something crazy or something that wasn’t discovered in the extensive beta testing phase, from what I can tell, it’s definitely stable enough for what I intend to be doing.
If you are planning to buy it and are also planing to buy a PC too, might I suggest you get the PC first and make sure it’s specification is compatible with V-Ray Next
Finally completed the purchase of V-Ray Next upgrade from V-Ray 3, sadly as usual, Chaos Group being 2 hours ahead of us here in the UK, means they are closed for the day.. Same as last year when I purchased V_Ray 3. No idea if it will be sorted on Saturday, do Chaos Group open at weekends. If not it will mean having to wait until Monday, to get it downloaded, installed and running.. but hey, the fact that I have finally upgraded, is what matters.. Lucky too, because the promotional price, ends tomorrow (30th June).. Itching to get playing with it now
Since the official release we’ve uploaded a few hotfixes, you can find the changelog for these below:
4.02.04.00005
=============
Bug fixes:
*) VRay2SidedMtl: Invalid colors with V-Ray Standalone when rendering scenes with two VRay2SidedMtl materials nested in each other;
*) VRayVolumeGrid: Fixed message boxes not showing;
*) VRayVolumeGrid: Caches containing digits after the # format can not be loaded;
*) VRayPluginNodeTex: IPR crashes when VRayPluginNodeTex using TexNoise as a displacement map is being modified;
*) VRayEnvironmentFog: Crash with VRayEnvironmentFog in specific scene;
*) VRayOSLTex: Crash when selecting specific VRayOSLTex in the Material Editor on scene open;
*) VRayDirt: Crash when undoing deletions of geometries with Dirt texture;
*) V-Ray: Exception when cancelling a batch render in 3ds Max;
*) V-Ray: Crash when region rendering with render elements and Previous render set to Darken;
*) VFB: Closing the V-Ray VFB while 3ds Max is saving a VFB image causes 3ds Max to crash;
*) V-Ray scene converter: Improve CoronaTriplanar texture conversion;
*) V-Ray scene converter: Improve CoronaSkin materal conversion;
*) V-Ray GPU: Crash with Ornatrix in V-Ray GPU;
*) VRayScene: Support for rendering lights from .vrscene files;
*) V-Ray GPU: Noisy alpha channel with shadow catcher objects;
*) V-Ray: Different brightness in high-res renderings with Auto Exposure;
*) V-Ray GPU: Crash when deleting heavy geometry in specific scene during IPR;
4.02.04.00004
=============
Bug fixes:
*) DR: Fixed crashes with DR on render end;
*) V-Ray IPR: Crash on the second frame in scenes with lots of animated plugins;
*) V-Ray GPU: Crash with Displacement and Environment Fog in V-Ray GPU IPR;
*) V-Ray GPU: Crash with BerconNoise and VRayDisplacementMod;
*) V-Ray GPU: CUDA error 700 when turning off Lights while rendering in IPR;
*) V-Ray GPU: Crash when deleting VRayLights during IPR in specific scene;
*) VRayOSLMtl: OSL issues errors when output closures are not explicitly specified;
4.02.04.00003
=============
New features:
*) V-Ray: Add a parameter for additional control of the auto-exposure in f-stops (renderers.current.camera_autoExposure_compensatio n);
*) V-Ray: Initial support for direct rendering of CoronaMtl and most materials from the Corona material library;
Bug fixes:
*) VRayScene: Camera settings saved in .vrscene affect the camera in 3ds max;
*) VRayScene: When a VRScene is moved, a texture projection inside the .vrscene file is not moving with it as expected;
*) V-Ray GPU: GLSL materials cause GPU to recompile kernels on each start;
*) V-Ray GPU: TexFalloff slotted within TexBlend produces CUDA error 700;
*) V-Ray GPU: Random crash when changing VRayLight options during IPR;
*) V-Ray GPU: Fix render elements for double-sided materials;
*) Lens analyzer: Crashes when analyzing a photo manually;
*) V-Ray GPU: When there is just one light in the scene, adaptive lights v2 unnecessarily resets the progressive buffer;
*) VRayMDLMtl: Add support for Ward BRDF in MDL plugin;
*) Installer: Improve the Instruction set check message;
*) V-Ray GPU: Multiple overlapping volumes do not blend correctly with V-Ray GPU;
*) V-Ray GPU: Crash when rendering VRayVolumeGrid with GPU as production after rendering with IPR;
*) V-Ray GPU: Fixed a crash during Phoenix FD simulation when using V-Ray GPU;
*) V-Ray GPU: VRayHDRI with RGB multiplier in the Output rollout renders differently with V-Ray GPU;
*) V-Ray: Standard material diffuse texture and opacity map do not work with V-Ray Next;
*) V-Ray: Crash when starting IPR after resetting a scene with a DR render;
*) VRayHDRI: Better performance with tiled .tx and OpenEXR textures;
*) VFB: VFB Image Info has to be cleared when loading a new image in VFB;
*) V-Ray GPU: Refresh interactive button doesn’t work correctly in V-Ray GPU IPR;
*) VRay2SidedMtl: Crashes on second frame with animated sub-material;
*) V-Ray GPU: Saves blank images when used as texture baking renderer;
*) VRayLight: Improve sampling with adaptive dome light on directly visible surfaces;
*) V-Ray: Stuck at “Building embree moving trees” with multisegmented motion blur;
*) VRayGLSL: QuickShader improvements - shortcuts for compilation (Ctrl+S) and reset (Ctrl+R) as well as respective right-click menu commands;
*) VRayOSL: Crashes with OSL in specific situations;
*) V-Ray GPU: When using displacement, textures are affected by the texture format settings;
*) V-Ray GPU: Unexpected render result with non-spherical Dome VRayLight and matte shadows;
*) V-Ray GPU: TexOCIO does not work with bitmaps;
*) V-Ray GPU: CUDA error 719 with specific scene;
*) V-Ray IPR: Crashes with Alembic hair in specific scene after stop;
*) VRayScene: Support for Cryptomatte render element;
*) VRayDenoiser: Switch to OptiX 5.1;
*) VRayOSLTex: Renders black in IPR if attached to VRayExtraTex;
*) DR: Crash when rendering with DR;
*) V-Ray GPU: Crash with specific VRayProxy and displacement;
4.02.04.00002
=============
New features:
*) V-Ray Cloud: V-Ray Cloud submit scene analysis - UI implementation;
Bug fixes:
*) V-Ray IPR: Crash when modifying VRayInstancer material in IPR and switching to another frame;
*) VRayOSLTex: VRayOSLTex crashes in IPR;
*) VRayOSLTex: Flipped textures with exported OSL maps to .vrscene files;
*) VRayOSLTex: Assertion failure when exporting OSL maps;
*) V-Ray GPU: V-Ray GPU crashes with top-bottom stereo mode in IPR;
*) VRayInstancer: Crash with VRayInstancer fed by Thinking Particles;
*) V-Ray: Separate render channels output files are not named properly when saving to separate folders (regression);
*) V-Ray IPR: Aspect ratio is changing when resizing VFB during IPR;
*) VRayInstancer: Particle extraction limited to single-theaded (otherwise particles may be lost);
Vlado, anybody?