Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.2.14f1
6000.5.0a4
Issue ID
UUM-129555
Regression
No
[FrameDebugger] Resizing FrameDebugger while it’s enabled, randomly jumps through the passes
Steps to reproduce:
- Download attached project and open in Unity.
- Open SampleScene.
- Open FrameDebugger >> Window >> Analysis >> FrameDebugger.
- Dock it next to the Game View.
- Enable FrameDebugger.
- Select (RP 4:0) CopyColor pass.
- Select the window edge between the Game View and Frame Debugger.
- Resize the window horizontally.
- Observe: Frame Debugger will jump through the passes.
Actual results: Frame Debugger jumps through the passes when resizing the window.
Expected results: Frame Debugger should stay on the pass that was selected while resizing the window.
Reproducible with versions:
6000.2.14f1, 6000.5.0a4
Tested on (OS):
MacBook Pro (16-inch, 2021), CPU: Apple M1 Max, Memory: 64 GB, macOS Tahoe: 26.1
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.