Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.0.0b3
Issue ID
632350
Regression
No
Audio Profiler: Window displays a lot of information, which can be a bit confusing at a glance
Audio Profiler : Window displays a lot of information, which can be a bit confusing at a glance. Please see attached screen shot for details.
Not sure if this would make sense for a developer, but would it make sense to divide all the Stats information into subgroups? Like for instance:
Sources
- xxx
- xxx
Voices
- xxx
- xxx
CPU
- xxx
- xxx
Memory
- xxx
- xxx
To reproduce:
- Open attached project and launch "test" scene
- Open Profiler
- Hit Play
- Select a certain point that you want to profile
- Select "Channels And Groups"
- Observe all the information on the right-hand side of the Audio Profiler
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
Add comment