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
- The Property's reference does not default to "_MainTex" when creating a new Texture2D Property in a ShaderGraph
- The "--additional-libraries" argument is ignored when building projects with the IL2CPP scripting backend
- Matching Selectors list not updating correctly with element's pseudo-state updates
- [Android] Crash on vendor/lib64/egl/libGLES_mali.so when Graphics Jobs(Experimental) is disabled and the Player is running on the Google Pixel 6 with the March security patch installed
- Profiler does not profile after building the Project with Autoconnect Profiler Option enabled
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.