Dealing with NaN
-
I think that there should be an option to do a "NaN Scan" somewhere. What the NaN Scan does is that it checks through all the important variables in the game; when it finds NaN in a variable, it automatically sets the variable back to 0, then continues the scan until it is finished.
Quite annoying when there's NaN pressure destroying everything in your save.
(Note: NaN pressure is possible; create a tight box of ACEL (life 65535, use in console !set life acel 65535) and put one pixel of something like BGLA inside it. Doesn't work for all elements, but it happens)
-
I don't think an "NaN Scan" would do anything, if there is a bug causing all the variables to be corrupted you need to restart the game. Also the only thing i've ever seen this happen with is pressure, and the next version fixes that by adding a cap on velocity (to some extreme number that won't affect anything).
-
What about the pixel velocities themselves? Sometimes, ACEL can also NaN the velocities of the pixels. I know that because I have a debug script I got from someone...
-
@PTuniverse (View Post)
The pressure and velocity grids are calculated from each other and are basically the same thing, if one has NaN the other does too. But that bug is fixed, it's caused when a particle velocity goes up to insane numbers that they should never be at, which causes that effect in the pressure / velocity grids. -
@tmo97 (View Post)
how is this cool? It's happened in some real saves before. Also it was already fixed.
