Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
1
Found in
2019.4.16f1
2020.2.0b14
2021.1.0a7
2021.2
Issue ID
1311717
Regression
Yes
"In order to call GetTransformInfoExpectUpToDate, RendererUpdateManager.UpdateAll must be called first" when entering Play Mode
How to reproduce:
1. Open user-submitted project
2. Open the ReproScene
3. Enter Play Mode
Expected result: no errors are thrown
Actual result: one error is thrown
Reproducible with: 2019.4.16f1, 2019.4.19f1, 2020.2.0b14, 2020.2.3f1, 2021.1.0a7, 2021.1.0b5, 2021.2.0a2
Not reproducible with: 2018.4.31f1, 2019.4.15f1, 2020.1.0a1, 2020.2.0b13, 2021.1.0a1, 2021.1.0a6
Notes:
Warnings about missing scripts are caused by project size reduction. Only the error appears in the actual full project
-
VolodyaSaiyajin
Feb 19, 2023 17:15
Same for me on 2021.3.11f1
-
indie6
May 09, 2021 06:37
Still appearing in 2020.3.5f1
-
smokyedawg
Apr 02, 2021 23:51
Same on 2019.4.20f
-
Snigros
Mar 25, 2021 00:10
Still appearing in 2020.3.1f1 - annoying!
-
matt-FLG
Mar 08, 2021 12:57
Will this fix come to 2020.2?
It's an annoying error still appearing while playing on the editor -
luigiboccardo3
Feb 12, 2021 07:43
Same for me on 2019.4.19f1
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
- EditorUtility.DisplayDialog is not shown when Input.GetMouseButtonDown is called a second time
- Animator Enum Properties get set to 0 instead of the value specified in the Scene when the Property is animated by a State that is not playing
- [iOS] Background thread runs a few times slower when “application.targetFrameRate“ is set to 30 compared to 29 on some iOS devices
- Multiple Enum Flags not rendering correctly in the Editor when custom PropertyDrawer values are changed
- Harsh edges appear when raising the Terrain with a low opacity value brush
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a8
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0b12
Resolution Note (fix version 2020.3):
Fixed in 2020.3.3f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.23f1