3D Editor
Diagnose Editor performance
Inspect live frame, renderer, loading, memory, and scene-worker diagnostics.
Before you start
Open a workspace scene in the 3D Editor.
Who can do this
Members with Editor access. Editing actions depend on your role and the shared view permissions.
Steps
- Select Diagnostics in the shortcut bar below the viewport, press D, or search for Open diagnostics in the command palette.
- Reproduce the slow interaction while the panel is open so Nimbus captures live samples.
- Review the diagnostic summary, then inspect frame timing, renderer, point-cloud, memory, loading, CPU-task, and scene-worker sections.
- Use Copy diagnostics snapshot to capture the full JSON report, or Reset diagnostics before measuring a separate action.
- Select Assets or press B to replace Diagnostics with the asset browser.
What you should see
The bottom panel shows live diagnostic evidence that can be copied into an issue report.
If something goes wrong
- Profiling is collected only while Diagnostics is open.
- GPU timing can show as unsupported when the browser or graphics driver does not expose timer queries.