To ensure Autodesk VRED products runs to their potential, please ensure your hardware meets the minimum recommended system requirements.

• Requirement for VRED 2023

• New Features and Enhancements

• Fixed Issues

• Known Issues and Workarounds

These are the requirements, new features, improvements, and known issues found in VRED 2023.2 products:

Requirement for VRED 2023.2

The following is required for VRED 2023.2

• For Windows users, 2023.2 requires an NVIDIA RTX driver v.511.65 or above.
• For Linux users, 2023.2 requires an NVIDIA driver v.510.47.03 or above.
• Linux dependency for Render Node - If working on a Linux machine, set your local directory to /var/opt/Autodesk with write access on the Linux machine that is running the VRED 2020 Render Node.

New Features and Enhancements

For the new features and enhancements in Autodesk VRED 2023.2 products, see the What's New.

Fixed Issues

These are the issues we fixed in VRED 2023.2 products:

Animation

• Camera Position Changes - Output animation for constrained cameras no longer jumps to different camera positions when Antialiasing is enabled.
• Clearing Undo History - Fixed a crash when modifying orphaned curves in the Curve Editor after clearing the undo history containing these objects.
• Export to FBX - An unused group object is no longer created in the FBX file when exporting to FBX.

Asset Manager

• Apply To Scene by Name imports sub-materials from a material switch into the Material Editor.

Camera

• Camera Error Message - Creating a new scene (File > New Scene) after using Cut to remove a camera aim camera no longer generates a camera error message in the Console.
• Aim and Up Camera - Creating, then undoing an Aim and Up Camera no longer leaves a ghost camera.
  • Interactive Depth of Field quality settings are greyed out when Off or Stillframe is selected.
  • The Visualization options, Display Camera, Display Aims, and Scale, are no longer saved to the viewpoint.
• VRED no longer crashes when copying and pasting Tonemapping in the Camera Editor.
  • The Contrast value is now included when pasting Tonemapping attributes in the Camera Editor.

Environments

• Transparency and Environments - When Is Visible is disabled for an environment, the environment is no longer visible when looking through transparent materials.

  Issue	Fix

General

• Objects are selectable and transformation handles are visible when the near clipping plane is too close.

• After using Isolate View, geometry that should be selectable can now be selected.

• The system default Microsoft Windows' ICC profile, sRGB Color Space Profile.icm, can now be embedded into a rendered PNG image file. VRED uses this color profile, if Edit > Preferences > Color Management > Use System Monitor Profile is enabled and Device Profile in Windows' Color Management is set to sRGB IEC61966-2.1 (sRGB Color Space Profile.icm).

  

• In OpenGL, the local lighting is displayed correctly for geometry using more than six clipping planes.
• Fixed the execution of scripts for VREDServerNode.exe.

GPU Raytracing

• Visible in Alpha now provides the same results for auxiliary passes on GPU raytracing mode as on CPU.
• Material Ball Updates - After the material ball is updated the material ball model no longer randomly appears in the viewport.
• GPU cluster doesn't crash when rendering a combination of variants using the Render Settings > Variant Set Render with GPU raytracing.

Lights

• Black Shadow - A black vertex shadow no longer appears when vertex baking with a textured disk light.
• Texture on lights update during a display cluster session in OpenGL and CPU/GPU raytracing render modes.

Materials and Material Editor

• Infinite Tiling - Infinite tiling works as expected on triplanar displacement maps in OpenGL mode.

• Triplanar material interpretation in VRED 2023.2 matches that of 2023.

• Color Control: Spectrum can be set although it's not needed/supported

• Incandescence Color - When photometric parameters are active, the correct incandescence color is set and displayed in OpenGL and raytracing modes.

• Changing Anisotropy works as expected for Incandescence textures.

• Material previews appear as expected when switching from GPU to CPU raytracing, while previews are being rendered.

• White Balance settings are changed when pasting Color Correction attributes onto another viewpoint.

  • Subsurface Scattering color works in OpenGL mode for Triplanar projections.

• On systems without OpenGL support, when trying to modify a Substance material, Substance tries to use the GL library and crashes.

  • In OpenGL, the Woven Cloth material no longer turns black when Subsurface Scattering is set to Volume Scattering mode.

Raytracing

• The reflections on brushed metal are now correct. This fixes the issue when the reflections are converted to vectors for BRDF layers of a material.
• The surface structure bump is correctly evaluated for photons.
• Toggling Photometric Parameters correctly updates incandescence.
• The geometry clipping state is now updated when adding or removing geometry from the local clipping plane node.
• The consistency of rendering glass materials between CPU and GPU raytracing has been improved.

References

• Loading a newly created file containing Smart References causes no problems.
• Unshared geometry references for FBX files from PIXYZ.
• References in FBX files converted from CAD using PIXYZ appear when imported into VRED.

Rendering

• Fixed switching from Surface Analysis Rendering to Analytic Rendering mode.
• There are no longer inconsistencies between live and offline rendering of the background color and backplate pass.
• After Analytic Rendering is set and a new scene is created, analytic rendering is still active.
• SSAO computations account for the change in viewport size when using stereo rendering.

Scenegraph

• Isolate View - After using Isolate View Selected and changing geometries, pick-selection in the viewport works as expected.
  • Only the visible children of an isolated node are shown, and not the hidden.
  • When Isolate View is used on a hidden group node, visible child geometries are displayed, while hidden children are not.
  • With multiple render windows, objects hidden by Isolate View reappear immediately in the viewport when Isolate View is switched off.

Scripting

• The Camera Editor Python methods, vrdCameraBaseNode.setToCurrentView(), vrdCameraBaseNode.resetView(), and vrdCameraNode.setInitialCamera(), are now undoable.
• Loading cameras no longer freezes VRED.

VR and XR

• Pressing the Place or other buttons in the VR Menu when in Desktop mode no longer crashes VRED.

Web Interface

• The Cluster Manager web interface works with Python web APIs.

Known Issues and Workarounds

• Windows Users in VR with 6+ GPUs - Due to limitations of the virtual address space in Microsoft Windows, using more than 6 GPUs in a NVLink configuration requires setting VRED_DISABLE_CUDA_MEMORY_POOL_SUPPORT as an environment variable. Disabling the usage of the memory pool will reduce scene initialization and update performance.

  Here is the error message you would encounter:

   Failed to create Cuda stream: CUDA_ERROR_ILLEGAL_ADDRESS: an illegal memory access was encountered
  
   Failed to synchronize stream: CUDA_ERROR_INVALID_HANDLE: invalid resource handle
  
   Failed to allocate memory: CUDA_ERROR_LAUNCH_FAILED: unspecified launch failure

  For instruction on entering environment variables, see Where To Enter Environment Variables.

• Cluster Manager - When saving renders from the Cluster Manager job queue to a network folder, VRED fails to create an output file or trigger a warning.

  A workaround for this is to change the file name, the path in Render Settings, and then check to see if the image already exists in that location.

• Cluster Failure - A cluster will fail to start, if the last node is localhost in the cluster list.

  Explanation: A pipeline and PCs at the beginning of the list need to reach PCs later in the list by the given Name or IP Address. If localhost is used, VRED tries to use the hostname of the master PC; however, PC 10.148.241.230 doesn't know GRED-P710 by name.

• Internet Explorer dependency - If installing VRED 2020 on a machine running Internet Explorer, Internet Explorer 10 is needed to display the Let's get started screen.

  A workaround for this is to create a deployment installer. When creating deployment installer images, VRED starts up fine for all license types. In the VRED user control popup menu,

  • Sign In works
  • Sign Out And Quit (user license) won't work
  • Manage License won't work
  • Explore Purchase Options sort of works, but the web page looks strange due to the older version of Internet Explorer