Search Issue Tracker
Fixed
Fixed in 2023.2.X, 2023.2.0a18
Votes
0
Found in
2022.2.6f1
2023.1.0b3
2023.2.0a16
Issue ID
UUM-27261
Regression
No
[UI Toolkit] Match Game View doesn’t reflect how UI appears in Game View with some Panel Settings
Repro:
- Open the project from the attached .zip.
- Open Assets -> Scenes -> 01_MainMenu and view the Game Scene.
- Set Game Scene resolution to Free Aspect.
- Open MainMenu.uxml (Assets -> UI Toolkit -> UI Assets -> UXML) in the UI builder.
- Ensure ‘Match Game View’ is selected on the Canvas.
- Adjust the Game view size to see how it affects the canvas in the UI Builder viewport.
Expected Outcome: The Viewport in the UI Builder matches what you see in the Game View
Actual Outcome: The UI in the viewport looks very different from the Game View. See attached image.
Reproducible in 2023.1.0b3, 2021.3.18f1 - marking as not a regression.
Have not extensively regression tested the issue - please contact the assigned ticket reporter if you need further testing or information.
Note:
- Have only seen this happen when Panel Settings has Scale Mode set to ‘Scale with Screen Size’ and the Reference Resolution is set.
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 (fix version 2023.2):
Verified in PR