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
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
- Visual Studio Code does not integrate with the project when the .slnx project is opened
Add comment