Unity Issue Tracker - ShaderGraph's Object node's WorldBound property produces a wrong value when a Tilemap Renderer Component is active
Closed
UUM-65353
ShaderGraph's Object node's WorldBound property produces a wrong value when a Tilemap Renderer Component is active
Unity: 2D
Won't Fix
6.2.X
6.1.X
2023.3.X
2023.2.X
2022.3.X
Cancelling this 2023.2 tech release issue since the support for this release has come to end of life. Cancelling this 2023.2 port case does not affect any LTS or Unity 6 Beta/Preview that remain open.
Steps to reproduce:
1. Open the attached "Hopeful Dumpster Fire" project
2. Open the "Assets/Scenes/SampleScene" scene
3. Duplicate the "Square" GameObject
4. Move around one of the "Square" GameObjects and observe it’s color change
5. In the Hierarchy window, expand the "Grid" GameObject and enable the "Renderer" GameObject
6. Move around the "Renderer" GameObject
7. Observe the results
Expected results: The "Square" GameObject's color changes only when it is moved around
Actual results: One of the "Square" GameObjects' colors change when the "Renderer" GameObject is moved around
Reproducible with: 2022.3.20f1, 2023.2.13f1, 2023.3.0b10
Could not test with: 2021.3.35f1 (Object node does not have the World Bounds Min property as it was added in the 2022.3 stream)
Reproducible on: Windows 11 Pro
Not reproducible on: No other environments tested
Notes:
Reproducible in Editor and Standalone Player
This only affects one “Square” GameObject at a time and when the affected GameObject is disabled, the issue starts affecting the next “Square” GameObject
Prioritise and Follow this issue
Have a workaround or additional info about this issue?