Comments

ivel236 2nd Sep 2016

Interesting... It's not actual RAM though just virtual RAM right? They could prolly program the variable to hold like 4GB but that would be stupid.
QuanTech 2nd Sep 2016

+dayday24 "edited in a strange way" sounds like haxxx
LBPHacker 2nd Sep 2016

lawl, time to gdb
Wonsz 2nd Sep 2016

When it crashed my CPU usage went from 16% to 30%
dayday24 2nd Sep 2016

Oh, I see. I crashed, it says Memory read/Write error. Implying that either your memory is corrupt, edited in a strange way, or all RAM is used up (Latter is much more likely). So I believe that particals have a RAM adress storing their data, velocity, X,Y, tmp, temp, Heading, life etc.
dayday24 2nd Sep 2016

And Constantly accellerating them causes the velocity numbers to become bigger, and the X and Y changes faster, meaning more memory accessing, and the increased mem use of all of those Photons add up.
dayday24 2nd Sep 2016

Creating two scenarios, 1. You run out of memory, end of story, game crashes. 2. The velocities grow so big that it causes a stack overflow creating an exeption that TPT does not know how to handle, leading to a crash. #1 is much more likely, but I cannot tell for certain what occurred.
JoshSteely 2nd Sep 2016

happened to me too
pyprorekker 2nd Sep 2016

it works for me
Cool4Cool 2nd Sep 2016

I got the bluescreen. The mods should figure out why this is happening... +1

The Powder Toy