Search Issue Tracker
Feature Request
Feature Request in 2020.2.X
Votes
0
Found in
2020.2.6f1
Issue ID
UUM-7387
Regression
No
Scripting Code not Auto-Instrumented when run in a custom PlayerLoop delegate and using Deep Profiling
No description entered in Cloud incident.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
Resolution Note:
We've considered the issue and concluded that this is behaving as it should at this moment, but we have filed it as a feature request to insert instrumentation for custom PlayerLoop delegates.
The current workaround is to manually place ProfilerMarkers in custom PlayerLoop delegates to get them to show up in the profiler, or to turn on Deep Profiling.
Resolution Note (2020.2.X):
We've considered the issue and concluded that this is behaving as it should at this moment, but we have filed it as a feature request to insert instrumentation for custom PlayerLoop delegates.
The current workaround is to manually place ProfilerMarkers in custom PlayerLoop delegates to get them to show up in the profiler, or to turn on Deep Profiling.