Search Issue Tracker
Fixed in 7.3.0
Votes
0
Found in [Package]
4.3.0
Issue ID
1118665
Regression
No
[VFX] Uninformative errors are thrown when Quad Output's Speed Range is set to zero
How to reproduce:
1. Open the attached project ("case_1118665-DaEffects.zip")
2. Open the repro scene ("repro")
3. In the Hierarchy, select the "VFX three" object and open its Visual Effect component
4. Inspect that Quad Output's Speed Range is set to zero
5. Close the VFX tab
5. Inspect the Console
Expected results: errors can be seen in the console stating that the Speed range cannot be zero
Actual results: uninformative shader errors are thrown, which doesn't link to the actual issue
Reproducible with: 2018.3.9f1, 2019.1.0b7
Reproducible Package version: 4.3.0, 5.7.2
Notes:
1. Changing the Quad Output's "Speed Range" property's range to be bigger than 0 fixes the issue
2. Couldn't test with 2017.4 because HDRP and VFX package are not supported in this branch
3. Couldn't test with 2019.2 because of package errors
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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Resolution Note (fix version 7.3.0):
Package available in 2019.3.0f6 and above