yes this is NOT a bug this is somewhat realistic and that is SUPPOSED to happen. Just use common sense of physics... you should have learned this between 7-9th grade i supppose
The lowest FPS i got was 5.46
It's kind of funny how you made such a complicated laggy (for me) save just to raise the temp of CLST to 72 C. lol. I guess no one knew that before though.
wierd, this happens to many so many times and i tried to tame it, but nope its a BUG... there goes 12 saves...
Congrats dude. Awesome work on finding the fix.. Also set temp 350 is glorious even if it is a bug..
fixed. I decided on day (12/1/12)?, I will try to fix this. I just happened to be compiling in debug mode for some reason at the time. I opened a save with CLST, and literally 2 seconds later it crashed with "ununitialized variable" It was so easy after all this work trying to find it before... I don't even know how that happened. Also, !set temp clst 350 lol, the easy way to do it. CLST hates having a temp of exactly 350 I guess it initializes that variable if temp is < 350 and > 350, but not >= 350 like it should. When uninitialized, the varialbe is like -1985729382 or some garbage value, and it's velocity is set to that, causing the bug. Expect it in 84.3 or 85.0, whatever the next version will be.
ok, I just had it happen to me. In tpt++, it isn't as bad at all. If it was tpt, every element would emit 256 pressure and the whole screen would fill up with either 256 or -256 pressure as soon as you drew something (even after hitton clear sim)
tothemyers: That would be 2fps. Also, it wouldn't be possible to create an option. If you know how to compile, you can easily change it though. Gadamlu: ok, it's happened like that to me too, but using an extremely powerful explosive not in normal tpt.
What I saw was just pressure being released out of the bottom of the brick, but I'm not sure if that was what you were talking about. :/