Search Issue Tracker
By Design
Votes
0
Found in [Package]
5.13.0
Issue ID
1151623
Regression
No
[LWRP] The Shader becomes distorted in the build
How to reproduce:
1. Open the attached 'Test cube shader.zip' project
2. Play the 'SampleScene' scene and observe the Game Object
3. Build the project
4. Observe the Game Object
Expected result: Game Object looks the same as in Editor
Actual result: Game Object is rendered differently
Reproducible: 2019.1.3f1
Can't reproduce:
- 2018.4.1f1, because the Game Object is rendered in magenta
- 2019.2.0b2 (LWRP 6.5.3), 2019.3.0a1, 2019.3.0a3, because the Game Object immediately disappears in the build
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 due to the UV on the custom mesh loses precision after Vertex Compression. User can solve this by doing this: PlayerSettings > Vertex Compression > exclude "Tex Coord 0" for first UV channel.