Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2019.3.0a1
2020.2
Issue ID
1376843
Regression
No
Unity.Profiling.LowLevel.MarkerFlags is inconsistent with profiler plugin API declarations in IUnityProfiler.h
User pointed out that there is no way to find out whether or not ProfilerCounter is supported in release Players - https://forum.unity.com/threads/allow-filtering-release-build-working-profilerrecorderdescriptions.1189633/#post-7613026
However upon further inspection I've discovered that we do have such a flag and there is an inconsistency between C++ and C# API surface.
Actual result: Unity.Profiling.LowLevel.MarkerFlags is inconsistent with UnityProfilerMarkerFlags definitions.
Expected result: All UnityProfilerMarkerFlags are reflected in Unity.Profiling.LowLevel.MarkerFlags enum and are documented.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
Add comment