Search Issue Tracker
By Design
Votes
1
Found in [Package]
12.0.0
Issue ID
1349065
Regression
No
[Shader Graph] Position Node uses World Space instead of Object Space when there is more than 1 instance in the scene
How to reproduce:
1. Open the attached project's Scene labeled "Test"
2. In the Scene View, inspect the square sprites
3. Note how they look
4. Disable/delete one of the sprites
5. Note that the appearance changed
Expected result: Position Node uses Object Space no matter how many instances of the Material there are in the Scene
Actual result: Position Node uses World Space when there's more than one instance of the Material in the Scene
Reproducible with: 7.7.1 (2019.4.29f1), 10.5.1 (2020.3.15f1), 11.0.0 (2021.1.16f1), 12.0.0 (2021.2.0b6, 2022.1.0a4)
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
This issue is a byproduct of batching sprites into one mesh - we lose the object coordinates. Dynamic batching is done automatically and can't be disabled.
A workaround is to make a unique material for every sprite, but this isn't scalable and may led to a performance impact.