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
- Imported FBX is rendered differently in Game view when comparing to Scene view
- "GetAllOverlapping failed" Error displayed in console or endless loading process on Application.Message.LeftButtonUp when cycle-selecting GameObjects with GPU Resident Drawer enabled
- Scene View has an inverted Game View window when changing from Game View to Scene View on a specific project
- An error is thrown when one TreeView root element is dragged and held over a parent element but is dropped between the elements
- Text Object position shifts when selecting multiple Text Objects and expanding the Extra Settings in the Inspector
Resolution Note (fix version 7.3.0):
Package available in 2019.3.0f6 and above