Search Issue Tracker
By Design
Votes
0
Found in
2020.3.40f1
2021.3.10f1
2022.1.16f1
2022.2.0b8
2023.1.0a10
Issue ID
UUM-15015
Regression
No
[URP] Object world position to object position transformations in the ShaderGraph shaders effected by the camera position an orientation
How to reproduce:
- Open the attached project (IN-9402.zip)
- Make sure the “Main” scene is open
- Move the Scene View camera so only one of the two sprites is visible
- Observe the sprite’s texture
Expected result: the texture remains the same as when both sprites are visible
Actual result: the texture changes to yellow with a slight orange gradient at the bottom
Reproducible with: URP 10.10.0 (2020.3.40f1), 12.1.7 (2021.3.10f1), 13.1.8 (2022.1.16f1), 14.0.3 (2022.2.0b8), 15.0.1 (2023.1.0a10)
Reproducible on: Windows 10, Ubuntu 20.04
Note: The issue is also reproducible on project builds
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
This is by design and working as intended. Sprite renderers use dynamic batching by default, which is why you are seeing different world matrices depending if the sprites are batched. See https://docs.unity3d.com/2021.3/Documentation/Manual/dynamic-batching.html for batching limitations.
If you require to use world position in your shaders, consider using SRP Batcher instead where per object data is preserved. See https://docs.unity3d.com/Manual/SRPBatcher.html for more information.