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
- Rigidbody prefab in scene is losing overrides on Linear/Angular Damping
- "ObjectDisposedException: SerializedProperty injectionPoint has disappeared!" errors are thrown in the Console and the Renderer Feature addition cannot be undone after performing Undo on a Full Screen Pass Renderer Feature
- Rendering corruption on ARM Mali GPU when using shader with FrameBuffer and DepthTexture with Vulkan API
- TextMeshPro text fails to render on macOS Standalone builds when Canvas Plane Distance is close to the Camera's Near Clip Plane
- info-log.json logs the wrong OS version when using a macOS device
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.