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

URP Features

-

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

  1. Resolution Note (fix version 2021.2):

    Fixed in 2021.2.0a8

  2. Resolution Note (fix version 2021.1):

    Fixed in 2021.1.0b12

  3. Resolution Note (fix version 2020.3):

    Fixed in 2020.3.3f1

  4. Resolution Note (fix version 2019.4):

    Fixed in 2019.4.23f1

Comments (8)

  1. Fernando-Ferreira

    Dec 27, 2023 05:16

    Found this same error on 2023.2.2f1 when setting multiple tiles at once in a tilemap

  2. HuldaGnodima

    Dec 14, 2023 15:59

    If anyone gets this in 2023 and beyond:

    Just got this error too a few days ago and made a bug report that is now in the bug-fixing pipeline it seems!

    https://issuetracker.unity3d.com/issues/rendererupdatemanager-dot-updateall-must-be-called-first-error-is-thrown-when-entering-the-play-mode

    Hopefully it will be patched and in the near future and no one else will encounter it :) Just sharing in case it's helpful to anyone

  3. VolodyaSaiyajin

    Feb 19, 2023 17:15

    Same for me on 2021.3.11f1

  4. indie6

    May 09, 2021 06:37

    Still appearing in 2020.3.5f1

  5. smokyedawg

    Apr 02, 2021 23:51

    Same on 2019.4.20f

  6. Snigros

    Mar 25, 2021 00:10

    Still appearing in 2020.3.1f1 - annoying!

  7. 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

  8. luigiboccardo3

    Feb 12, 2021 07:43

    Same for me on 2019.4.19f1

Add comment

Log in to post comment