Announcement

Collapse
No announcement yet.

V-Ray Next Update 3 hotfix 2 available for download (Next 3.2)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • V-Ray Next Update 3 hotfix 2 available for download (Next 3.2)

    V-Ray Next Update 3.2 is now available for download from our website.

    We've officially added support for 3ds Max 2021 as well as a lot of fixes and some improvements.

    Change log in the docs.

    Full change log:

    Build 4.30.02 (V-Ray Next, update 3.2) (07 April 2020)
    ==============

    New features:
    (*) V-Ray: Support for 3ds Max 2021;
    (*) V-Ray: Support for "Bake to Texture" in 3ds Max 2021;

    Modified features:
    (*) V-Ray: Improve performance scaling with 2nd gen Epyc dual 64-core setups 128 and more threads;
    (*) V-Ray: Look for the XML file with the view graph for viewport IPR relative to the vrenderNNNN.dlr file location;
    (*) VRayOSL: Add the ability to connect an OSL triple float output to a OSL single float input;
    (*) VRayScene: Matte and Visibility control;
    (*) VFB: Add MaxScript control for Test resolution through vfbcontrol;
    (*) .vrscene exporter: Update SettingsPresenZ export;

    Bug fixes:
    (*) V-Ray: 3ds Max frame buffer has the same resolution as VFB regardless of the "Get resolution from Max option";
    (*) V-Ray: Any click on the Light Cache preset dropdown changes the mode;
    (*) V-Ray: Crash after baking to texture in 3ds Max 2021;
    (*) V-Ray: EXR metadata in the VRayOptionRE is not saved with deep images;
    (*) V-Ray: Fume FX render elements are missing in V-Ray renders;
    (*) V-Ray: Random crash when rendering scene with VRayFur;
    (*) V-Ray: Tiled EXR textures cause specific scene to render considerably slower compared to 4.1;
    (*) V-Ray, V-Ray GPU: Incorrect internal reflection in glass when glossy Fresnel is enabled;
    (*) V-Ray: VRayRenderID by node handle is not saved correctly in deep EXR output;
    (*) V-Ray: Wrong 3ds Max Render output JPEG image with Test resolution;
    (*) V-Ray IPR: Deleting/updating VRayInstancer or assigned materials won't cleanup material-clones-bindings and would lead to crash;
    (*) V-Ray GPU/V-Ray Cloud: Anima AXYZ no animation when exported to vrscene;
    (*) V-Ray GPU/V-Ray Cloud: BerconMapping doesn't render properly when exported to Standalone;
    (*) V-Ray GPU: Bucket rendering produces black output when AA Filter size drops below 1.41;
    (*) V-Ray GPU: Crash when rendering VRMesh files with more than 16 mapping channels;
    (*) V-Ray GPU: Crash with VRayLightMtl with Direct illumination enabled, applied to tySpline;
    (*) V-Ray GPU: Crash with VRayEnvironmentFog when switching from bucket to IPR between consecutive renderings;
    (*) V-Ray GPU/V-Ray Cloud: Different result for BerconNoise in Standalone with some combinations of Noise Function and Fractal;
    (*) V-Ray GPU: Rendering on GPU with NVLink spanning more than 2 cards results in a crash;
    (*) V-Ray GPU/V-Ray Cloud: Tile UV mapping of the Bercon tile is not rendered properly;
    (*) V-Ray GPU: VRayMtl is missing glossy reflections on the back side if "Reflect on back side" is enabled ;
    (*) V-Ray GPU/V-Ray Cloud: VRayMtlID render element renders black;
    (*) V-Ray Standalone: -skipExistingFrames breaks file output to current directory;
    (*) V-Ray Standalone: -skipExistingFrames creates extra files in animation;
    (*) VRayEnvironmentFog: Artifacts with custom geometry fog gizmo in a specific scene;
    (*) VRayEnvironmentFog: Can not render with VRayNoiseTex used as density map;
    (*) VRayEnvironmentFog: Renders significantly slower with Scatter GI in V-Ray Next;
    (*) VRayFastSSS2: Material does not compose back to beauty properly;
    (*) VRayFastSSS2: VRayLightSelect in full mode does not match beauty pass when diffuse amount is above 0;
    (*) VRayGLSL: Float to int vector casts in shaders lead to crashes;
    (*) VRayGLSL: Incorrect matrix multiplication results;
    (*) VRayGLSL: Missing return statements in non-void GLSL functions lead to crashes;
    (*) VRayMtl: 100% white Opacity Map affects material Reflections;
    (*) VRayOSL: Crash in material editor preview rendering after editing OSL texture from MaxScript;
    (*) VRayOSL: Crash with Bitmap texture vrayattached to VRayOSLTex while exporting for V-Ray GPU;
    (*) VRayScene: Compiling geometry time is increasing with each frame in animation rendering with V-Ray Standalone;
    (*) VRayVolumeGrid: Volumetric rendering slow-down with Volume Light Cache enabled with V-Ray memtracker;
    If it was that easy, it would have already been done

    Peter Matanov
    Chaos
Working...
X