Search Issue Tracker
Fixed
Votes
63
Found in
2021.3.28f1
2022.3.4f1
Issue ID
UUM-41387
Regression
Yes
RectTransform "Pos Y" is not loaded when opening the project/Player
Reproduction steps:
1. Open the “RectTransformPosY“ project
2. If the “BugScene” scene is not open, open it and reopen the project
3. Select the “Image“ GameObject
4. Observe the “Pos Y” value in Inspector
Expected result: “Pos Y” is 150
Actual result: “Pos Y” is 0
Reproduced in: 2021.3.28f1 (“Pos Y” is 128), 2022.3.3f1 (only in Player), 2022.3.4f1
Not reproduced in: 2021.3.27f1, 2022.3.2f1, 2023.1.3f1, 2023.2.0a22
Reproduced using: Windows 11
Not reproduced using: macOS 13.4.1 (Intel)
Notes:
1. Also reproduced in Play Mode and Player
2. Not reproduced with “Pos X”
3. Can be temporarily solved in Editor by reopening the scene
-
PassionProjectStudio
Jul 21, 2023 17:30
As a new game game dev attempting their first larger game project and using Unity,
I just love wasting full days trying to track down what I'm doing wrong only to finally conclude that the software I'm using is the cause and not me.I don't even understand how a software made for producing other software can have these kind of glaring bugs in released builds. This isn't a small issue, and I had to waste a significant time trying to solve it.
Shit that is right where I put it when I'm working and going back and forth between editor and play mode is literally moving around every time I restart Unity, it's ridiculous.
-
ainisciurlys
Jul 12, 2023 18:27
The internal ticket was resolved as fixed in 2021.3.29f1 and 2022.3.5f1
-
wonilmax
Jul 10, 2023 16:41
I have the same problem. Pos Y set to 0 when Unity reopen. So, I create an empty scene that is not the scene I am working on and exit unity from that scene. Then, when I turn on Unity again, PosY is all set to 0 only for the visible scene, so when I enter the scene I am working on, PosY does not change. I'm doing this temporarily, but this bug is definitely bothering me. hope it gets resolved soon
-
pixelsplit
Jul 04, 2023 08:55
Same problem here. Breaks the complete UI. With 2022.3.3 it happened less then with 2022.3.4. Showstopper right now, because Scene Changes etc. break the UI. We revert to 2022.3.2 and wait for a fix.
-
JolanHuyvaertDieKeure
Jul 03, 2023 11:50
This breaks our game's UI prefabs and causes the scene to be marked as dirty when opened in editor. We had to do a rollback to 2022.3.0 for our project, but of course that version has other issues. I really hope this is fixed in 2022.3.5.
-
Good_Punk
Jul 02, 2023 12:10
The UI scaling is broken in builds, moving UI elements outside of the screen.
This bug makes Unity 2022 unusable for me. Please fix. -
BobberooniTooni
Jul 01, 2023 01:22
I am in 2022.3.4 and my canvases are working perfectly except in game builds, where several canvases have their x values reset to 0 every time.
-
ted_paradox
Jun 30, 2023 23:54
Since this causes the UI vertical offset on UI GameObjects to be zero for standalone player builds consistently (no matter how many times the standalone player is run), these versions of Unity are unusable for any game using UGUI. I did notice that 2022.3.3 sometime builds standalone correctly and sometimes builds it where the UI gets set to zero, while 2022.3.4 does it every time.
-
drnagol369
Jun 30, 2023 16:16
It's strange how it only affects when the scene loads as part of project open, but doesn't affect opening the file post-project load...
Would be interesting to know what exactly causes it
-
c0nd3v
Jun 30, 2023 15:32
I have the same problem
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Fixed by another internal issue: UUM-41127: Button fails to be created in the scene view