The Powder Toy

free presure bug by luminosity

luminosity
luminosity
67 / 6
6th Jun 2018
13th Jan 2023
It's Fixed!
fixit felix foxit fixitt fixeeet fexit donotfixpls fixitnow devsfixthis iamsoconfused

Comments

  • Floofy
    Floofy     13th Jan 2023
    thanks to this, I am able to make another bug, it's called everything breaks. Put Cyclone to max and see the strings strech too long
  • csavas
    csavas     27th Jul 2018
    Still not fixed.
  • ddli777
    ddli777     10th Jun 2018
    Another application: ID:2293911
  • dog3454
    dog3454     9th Jun 2018
    the vaccum broke the lines
  • lamyipfu
    lamyipfu     9th Jun 2018
    @jacob1, blueflame's save actually shows pressure leak in my TPT(TPTMP mod only), after C4 explodes, wait a while and the current progressively strengthens.
  • jacob1
    jacob1     9th Jun 2018
    explosivepowder: air simulation is actually not supposed to be affected by order. It keeps a map of the previous frame, and does all the calculations for the next frame based on that. That's why pressure moves around equally in every direction. It could be buggy though, I am aware of at least one other bug that lets pressure go through walls
  • jacob1
    jacob1     9th Jun 2018
    blueflame: I don't see any bug in that save, just C4 exploding
  • jacob1
    jacob1     9th Jun 2018
    Interesting bug ... I'll open an issue about it on github so that i'll remember to look into it at some point. JusticeFighter: Thanks for the minimalistic save, that's always helpful for narrowing down bugs
  • explosivepowder
    explosivepowder     8th Jun 2018
    In other words, the bug is defenitely caused in part at least, by being the last few pixels to get updated.
  • explosivepowder
    explosivepowder     8th Jun 2018
    The fact that the bug only occures in the bottom-right corner is a major clue to what causes it. The Powder Toy updates pixels, in each frame, from the top-left to the bottom-right. It updates as if you are reading, top-left, then moves over one right, one right again, ect until it hits the end then loops to the next line of pixels. The fact this only occures in the bottom-right shows that it is probably dependant on this, else it'd occure in every corner.