Search Issue Tracker
Won't Fix
Won't Fix in 1.0.X
Votes
0
Found in [Package]
1.0.0
Issue ID
SPLB-6
Regression
No
UV coordinates are incorrectly generated when width is uneven and low segmentation is used
Reproduction steps:
1. Open the user's attached project "Splines.zip"
2. Observe the yellow line in the middle of the road where it widens and narrows
Expected result: The zigzag of the line is not very visible and the line appears parallel to the edges of the road
Actual result: The zigzag is large and obvious
Reproducible with: 1.0.0-pre.8 (2021.2.17f1), 1.0.0-pre.9 (2022.2.0a9), 1.0.0 (2022.1.0b14, 2022.2.0a9)
Could not test with: 1.0.0-pre.8 (2019.4.37f1, 2020.3.32f1) (Script compilation errors)
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:
The problem is coming from the fact that using Width SplineData is deforming the road mesh. The default Unity shader is then using a affine projection of the UVs which result in this visual artifact.
As this is only a sample, and not meant to be a generic reusable code, we won't fix this as it seems to be out of scope for the package.
The user can still looks on the internet for some shaders solution using perspective mapping for the UVs that would fix this problem.
Resolution Note (1.0.X):
The problem is coming from the fact that using Width SplineData is deforming the road mesh. The default Unity shader is then using a affine projection of the UVs which result in this visual artifact.
As this is only a sample, and not meant to be a generic reusable code, we won't fix this as it seems to be out of scope for the package.
The user can still looks on the internet for some shaders solution using perspective mapping for the UVs that would fix this problem.