109.0.2#

Improved#

  • Added support for importing large .e57 point cloud files with vertex buffers exceeding 4GB for native RTX rendering [OMPE-71386]

Known Issues#

  • When rendering multimatte AOVs, the attributes omni:rtx:pt:multimatte:channel<N> and omni:rtx:pt:multimatte:channelCount must be set on each RenderProduct that is being rendered. This could be confusing as in the default case of a Kit-managed RenderProduct for the viewport, the Kit settings panel manages these attributes automatically for the viewport RenderProduct. This workflow will be simplified in a future release.

Fixed#

  • Object ID values in GenericModelOutput buffer were filled with constant bytes instead of valid 128-bit stable IDs [OMPE-73575]

  • Matte objects appeared blurrier when using RTX Real-Time 2.0 compared to RTX Interactive mode [OMPE-73495]

  • Scenes appeared significantly darker when using RTX Real-Time 2.0 compared to RTX Interactive mode [OMPE-73360]

  • Application crashed when switching from RTX Interactive to RTX Real-Time 2.0 rendering mode [OMPE-72934]

  • CUDA coredump generation failed to activate automatically on Linux systems with NVIDIA driver 580+, preventing crash debugging [OMPE-72891]

  • Ray guide performance regression caused decreased camera movement frame rates [OMPE-70571]

  • Multimatte render output produced inconsistent results across renders [OMPE-69657]

  • Application crashed on multi-GPU systems when switching from RTX Interactive to RTX Real-Time 2.0 renderer mode [OMPE-68620]

  • Mesh lights intermittently failed to illuminate geometry correctly due to non-deterministic light linking when geometry instances were created with streaming [OMPE-67366]

  • Matte Object Fade Out feature stopped working in RTX renderers, causing edge artifacts when compositing matte objects [OMPE-66916]

  • Visual artifacts appeared on Linux with Vulkan when using Clash Detection extension [OMPE-52613]