https://dev-docs.bevyengine.org/bevy_render/diagnostic/struct.RenderDiagnosticsPlugin.html
Ideally we nest the diagnostics so that each view has it's own diagnostic subpath, although we'll have to figure out how shadow passes fit into that, as well as non-view-specific nodes like MeshPreprocessing.
Also would be nice to further group by category, e.g. prepass/gbuffer, mainpass, post processing, etc.
Total path would look like /render/view_<NameOrEntityId>/main3d/opaque/gpu_time, using the Name component of the view if it's available, else the entity ID.
https://dev-docs.bevyengine.org/bevy_render/diagnostic/struct.RenderDiagnosticsPlugin.html
Ideally we nest the diagnostics so that each view has it's own diagnostic subpath, although we'll have to figure out how shadow passes fit into that, as well as non-view-specific nodes like MeshPreprocessing.
Also would be nice to further group by category, e.g. prepass/gbuffer, mainpass, post processing, etc.
Total path would look like
/render/view_<NameOrEntityId>/main3d/opaque/gpu_time, using the Name component of the view if it's available, else the entity ID.