Search Issue Tracker
By Design
By Design in 2023.2.X
Votes
1
Found in
2021.3.28f1
2022.3.5f1
2023.2.0a23
Issue ID
UUM-42791
Regression
Yes
Rendering and vertex position mismatches when using the Offset property
Reproduction steps:
1. Open the attached project “OffsetBug“
2. Open the Scene “Assets/Scenes/SampleScene”
3. In the Hierarchy window select the GameObject “Square”
4. Observe the Scene View
Expected result: Vertex and rendering positions are the same
Actual result: Positions do not match
Reproducible with: 2021.3.28f1, 2022.3.5f1, 2023.1.0a10, 2023.2.0a16, 2023.2.0a23
Not reproducible with: 2023.1.4f1, 2023.2.0a15
Fixed in: 2023.1.0a11
Reproducible on: Windows 11
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 a known issue when Dynamic-Batching is enabled as vertices are pre-transformed to batch multiple different sprites using the same texture/material. Hence any object space change to vertices won't really work.
To workaround such use-cases, please either use SRP-Batcher or enable Instancing.
Resolution Note (2023.2.X):
This is a known issue when Dynamic-Batching is enabled as vertices are pre-transformed to batch multiple different sprites using the same texture/material. Hence any object space change to vertices won't really work.
To workaround such use-cases, please either use SRP-Batcher or enable Instancing.