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
- Crash on GfxDeviceD3D12::AllocBottomLevelAccelerationStructure when using Raytracing
- The search icon in the "Searches" sections is blurry and inconsistent
- "RenderingCommandBuffer" error is thrown when switching to the tvOS platform
- Left side cog menu button is obstructed by the maximum Y value of the graph when editing a curve in the Particle System Curves
- "Property exceeds previous array size (64 vs 32)." warnings are thrown when switching from tvOS platform to a Standalone platform after restarting the Editor
Resolution Note (2019.3.X):
Microsoft FXC compiler bug