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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment