Search Issue Tracker
Fixed in 7.1.1
Votes
0
Found in [Package]
4.1.0
Issue ID
1154051
Regression
No
ShaderGraph AlphaClipThreshold does not accept input values unless Vector 1 node is attached
Reproduction steps:
1. Open the attached project named "Case_1154051"
2. Open the CutoutWithoutSlider shader with shader graph
3. Observe the preview window, notice that the sphere has cutouts
4. Delete the Vector 1 node attached to AlphaClipTreshold
Expected result: Shader does not change as the AlphaClipTreshold value remains the same (0.5) after the node is deleted
Actual result: The cutouts disappear even though the value is the same as before (0.5)
Reproducible with:2018.4.1f1, 2019.1.3f1, 2019.2.0b3, 2019.3.0a3
Could not test with: 2017.4 ( Lack of a Package manager )
Tested package versions: 4.1.0, 4.10.0, 5.1.0, 5.13.0, 6.5.3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Add comment