Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.24f1
2022.2.17f1
2023.1.0b14
2023.2.0a15
Issue ID
UUM-35050
Regression
No
[VFX Graph] Floating point division by zero at kernel warning is thrown upon node connection
How to reproduce:
1. Import the attached 'Warning' VFX
2. Connect float to Speed Range port of Scale over Speed block in Update Context
Actual result: Shader warning in '[Warning] [System] Update Particle': floating point division by zero at kernel CSMain at Warning.vfx(191) (on metal) is thrown to the console
Note: Resproduced on macOS, Windows
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Although we can potentially detect static divide by zero errors and display a warning in the graph (or an error and make compilation fail). Dividing by zero in graph means it's ill formed so we don't want to fix it, it's on the user's to fix their graph
Resolution Note (2023.2.X):
Although we can potentially detect static divide by zero errors and display a warning in the graph (or an error and make compilation fail). Dividing by zero in graph means it's ill formed so we don't want to fix it, it's on the user's to fix their graph