Tilemap Renderer with Mode=chunck and detect chunck culling bounds=manual, give me the error.

If you are using TileMaps, this exception maybe caused by calling the tilemap.SetTile() or tilemap.SetTiles() right after instantiating the TileMap. This exception disappears, at least in my case, when I call .SetTile() on next frame or update after the Tilemap was created.

I've got this error as well. Should I just ignore it?

P.S. The issue also persisted through restarts, so something in the data was setting it off.

Encountered this issue when attempting to use tiles with bottom centre pivots. It doesn't show up immediately but at some point calls to tilemap.SetTilesBlock were starting to set it off (I'm dynamically streaming tile data to and from a tilemap in the editor). The only thing that solved it was to re-pivot the tiles to the centre. Everything else failed - re-creating the tilemap, re-creating the pivot, creating a brand new scene - any time I used those bottom pivot tiles this error starts recurring whenever I used SetTilesBlock.

This suggests to me that the tilemap features aren't very compatible with non-default pivots at the moment.

Not resolved. Seeing it in 2019.4.32f1 URP.

Updated various assets to current. Tried various fixes below in thread. Nothing worked. Soon as my camera renders the scene I get this error.

Still an issue

Not resolved in 2019.4.22

Not resolved yet. Using 2019.4.16f1 URP

It had happened to me when the directional light was inside an animated game object that was being initiated in Awake(); before pressing the "Play" button.