Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0a1
2019.1.0a1
2019.1.7f1
2019.2.0a1
2019.3.0a1
Issue ID
1164170
Regression
Yes
Parameter for frac() in surface shaders ignores increments inside nested loops
How to reproduce:
1. Open the attached "NestedLoopShader.zip"
2. Reimport the SurfTest and SurfTest2 shaders and materials
3. Inspect the materials
Expected results: Both of the materials are identical
Actual results: The SurfTest material is all black, while the SurfTest2 material is rendered correctly
Reproducible with: 2018.4.3f1, 2019.1.8f1, 2019.2.0b8, 2019.3.0a8
Not reproducible with: 2017.4.29f1
Notes:
1. The issue is only reproducible if the parameter is initialized at 0 (SurfTest3 demonstrates this)
2. The issue does not reproduce in vertex fragment shaders
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
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
Resolution Note (2019.3.X):
Microsoft FXC compiler bug