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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment