The Powder Toy

subframe brainf*ck by xteric

xteric
xteric
6 / 3
21st Nov 2016
22nd Nov 2016
So I discovered this when messing around with subframe ARAY and discovered that for some reason subrame-created BRAY has problems being displayed when erasedd so that the life is random in the rays. Up to you if you call it a bug or feature.

Comments

  • braden1127
    braden1127     21st Mar 2018
    Um, needs more +-<>[].,.
  • danieldan0
    danieldan0     5th Jan 2017
    @CALVIN1390 stop please
  • LBPHacker
    LBPHacker     22nd Nov 2016
    That's just your screen failing to keep up with TPT.
  • xteric
    xteric     22nd Nov 2016
    Never thought about gettinn this much response. The thing I am pointing out is that when playing it frame by frame it seems okay (pressing f key) but when playing the simulation at +200 fps the brightnesseffect doesn't show on a regular basis.
  • powderskye
    powderskye     21st Nov 2016
    tell me why this is somewhat like binary?
  • CALVIN1390
    CALVIN1390     21st Nov 2016
    remove the f*ck because the f*ck is fu*k
  • zaccybot2
    zaccybot2     21st Nov 2016
    @LBPHacker is it actually a bug? In PowderToySDL.cpp it says if(fpsLimit > 2) ... so I feel like it was intentional because in the case where it is not more than 2, it doesn't actually delay, so if it was unintentional then I'm sure it would have been caught by now
  • CuriousPerson
    CuriousPerson     21st Nov 2016
    Scratch that it suddenly started working.
  • CuriousPerson
    CuriousPerson     21st Nov 2016
    Shouldn't an i5-6600 be able to get over 60FPS blank screen? Because Ive tried removing the cap but it will not change my FPS or go above 57-59 flashing between each.
  • LBPHacker
    LBPHacker     21st Nov 2016
    Yep. TPT caps the FPS at 60. You can remove that by entering "tpt.setfpscap(2)" into the console. Its effect is temporary though, you have to do it after every startup. Also, TPT will eat more CPU if you remove the FPS cap. Btw you can set it to any FPS you like, default is 60. There's a glitch somewhere that removes the cap entirely when it's set to 2.