New file export options now let you exclude physics and constraint attachments when exporting VPB/OSB files. Additional enhancements include a search bar in the Terminal, a Log Files option in the Help menu, interface improvements to Camera Editor Blending Frames, as well as various scripting enhancements and updates to the Material SDK.
You can now enable the Lightweight importer for 3DXML/CATIA V6 in the Import window and VRED Preferences to improve import performance on representative files.
You can now copy materials from the Material Editor of one VRED instance to another.
After selecting the materials in the first VRED instance, hold Alt + LMB until the export label appears next to the cursor. Then drag the materials into the Material Editor of the second VRED instance and release them to import the materials.
VRED supports extensive drag-and-drop workflows between editors. A common issue occurs when the target editor is docked in a tab group and not visible. We've improved this workflow: hover a dragged scene object over a tab to bring the corresponding editor to the front, similar to Windows File Explorer.
VRED now supports Shader Execution Reordering (SER), which dynamically regroups divergent ray workloads at runtime. This improves GPU coherence and utilization in complex ray-traced scenes, speeds up progressive rendering convergence, and boosts performance in material-heavy scenes.
We've added new functions and classes for Variant Sets and Thin Film. MDL and MaterialX compilation types now support cutout transparency. Additionally, new Faceter options are available in vrdAtfSettings and vrdTessellationSettings.
For a complete list of what has been added or changed in the VRED Python API, see What's New in Python API V1 and V2.
When using multiple GPUs for ray tracing, ensure that the Windows page file is configured with sufficient virtual memory. According to NVIDIA guidance, the page file must be large enough to accommodate the system's total memory capacity, including both system RAM and the combined memory of all installed GPUs.
For example, a workstation with:
has a total memory capacity of 512 GB (128 GB + 4 x 96 GB). In this configuration, the Windows page file should be set to at least 512 GB.
If the page file is too small, the system may experience out-of-memory crashes, even when sufficient physical RAM and GPU memory are available.
We've updated Getting Started tutorial videos for the following topics in the VRED help:
You can access the legacy tutorial videos from the VRED 2026 help.