You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our production has reported a performance degrade when switching from default 'object sorting' to 'depth peeling'.
This happens for PointInstancer but seems better for non-instanced prims.
Example - non-instanced prims: all the tiny cubes in the viewport are just regular prims:
🆗Navigate the viewport on 'object sorting' in smooth shaded mode: performs reasonable;
🆗Navigate the viewport on 'object sorting' in wireframe mode: performs reasonable;
🆗Switch to 'depth peeling', without changing display mode: performs reasonable;
🆗Then switch to either smooth shaded or wireframe mode: becomes unresponsive at first and then becomes reasonable later, Maya might be doing something at the beginning but as long as the viewport responses normally, I think it's acceptable.
Example - PointInstancer prims: all the tiny cubes positions & numbers match exactly the non-instanced example:
🆗Navigate the viewport on 'object sorting' in smooth shaded mode: performs reasonable;
🆗Navigate the viewport on 'object sorting' in wireframe mode: performs reasonable;
🆗Switch to 'depth peeling', without changing display mode: performs reasonable;
🚫Then switch to either smooth shaded or wireframe mode: becomes unresponsive, needs to wait for much longer than non-instanced example until Maya UI responses, but then keep navigating the viewport, it's still unresponsive for a long time before coming back to user.
Example - Navite Maya geometries: imported (converted) from non-instanced example into Maya as native geometries, just for reference:
No matter which transparency mode and/or shading mode combination, viewport runs quite good actually.
Steps to reproduce
Steps to reproduce the behavior:
Launch Maya and load either the example USD file example_non_instanced_prims.usda or example_point_instancer.usda
Change the transparency mode from default 'object sorting' to 'depth peeling'
Switch viewport shading mode to either smooth shaded or wireframe mode
Navigate in the viewport and observe the responsive time
Expected behavior
Improve the viewport performance for PointInstancer when using depth peeling mode.
Describe the bug
Hi,
Our production has reported a performance degrade when switching from default 'object sorting' to 'depth peeling'.
This happens for PointInstancer but seems better for non-instanced prims.
Example - non-instanced prims: all the tiny cubes in the viewport are just regular prims:
Example - PointInstancer prims: all the tiny cubes positions & numbers match exactly the non-instanced example:
Example - Navite Maya geometries: imported (converted) from non-instanced example into Maya as native geometries, just for reference:
Steps to reproduce
Steps to reproduce the behavior:
Expected behavior
Improve the viewport performance for PointInstancer when using depth peeling mode.
Attachments
Example USD files:
performance_degrade_example_USD_files.zip
Specs (if applicable):
The text was updated successfully, but these errors were encountered: