Search Issue Tracker
By Design
Votes
0
Found in
6000.0.15f1
Issue ID
UUM-78321
Regression
No
Frame Debugger UI glitches on MacOS
Reproduction steps:
1. Open the attached “Repro“ project
2. Open the “Assets/Darfall-Game/Scenes/Scene_05_Game.unity“
3. Enter the Play Mode
4. Open the Frame Debugger (Window > Analysis > Frame Debugger)
5. Enable it and observe
Expected result: Everything behaves as normal
Actual result: Can’t scroll in the Frame Debuggers Hierarchy, Selections flicker
Reproducible with: 6000.0.15f1
Couldn’t test with: 2021.3.42f1, 2022.3.42f1 (Unable to downgrade the project)
Reproducible on: M1 Max MacOS 14.5
Not reproducible on: No other environment tested
Comments (1)
-
Wrymnn
Aug 28, 2024 12:20
Issue persists even when using suggested code by Unity, or when completely disabling the VolumetricFog...
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
The FrameDebugger inspects in realtime what is being submitted to render.
They have a custom VolumetricFog class with a method called UpdateNoise.
There, the user is not always performing the same Graphics API calls, this is good as an optimization, but they need to check if the FrameDebugger is enabled:
if (activeProfile.noiseFinalMultiplier != 0 && !activeProfile.constantDensity
#if UNITY_EDITOR || DEVELOPMENT_BUILD
|| FrameDebugger.enabled
#endif
)
This will always perform the Graphics.Blit that was making the FrameDebugger flicker, if the FrameDebugger is enabled.
The FrameDebugger stops the game logic, but the rendering logic can be different on everyframe, this is a limitation of the tool. To get an snapshot you can use other tools such a RenderDoc.