Official Game Feedback

  • LBPHacker
    13th April Developer 0 Permalink
    @AtlantisDragon (View Post)
    Oh yeah, this. Thanks for reporting this, this is a known issue, but fixing it is not of high priority right now. Gravity is not treated as a deterministic process, it's currently only best-effort. The issue is possible to fix but it's not clear whether the benefits would be worth the trouble, in view of the complications it might introduce.
    Edited 2 times by LBPHacker. Last: 13th April
  • MachineMan
    14th April Member 0 Permalink

    I was working with BRAY that has all 30 bits turned on and FILT(VBSHIFT) annihilates it instead of shifting it; FILT(VRSHIFT) does still shift it though.

    Edited 2 times by MachineMan. Last: 14th April
  • LBPHacker
    14th April Developer 0 Permalink
    I'm going to need the exact ctypes going in and the exact ctype coming out. I see no problem with how variable shifts work.
  • MachineMan
    14th April Member 0 Permalink

    To turn on all bits, I set the FILT(SET) to -1 and the shifting FILT to 2; the shifting FILT only shifted the BRAY while in VRSHIFT mode; in VBSHIFT mode, it annihilated the BRAY instead.

    Edited once by MachineMan. Last: 14th April
  • LBPHacker
    14th April Developer 0 Permalink
    -1 is not interpreted as 0xFFFFFFFF, which has 32 bits set. FILT naturally operates only on its 30 least significant bits. This is "weirdness due to console foolery", not a bug.
  • abacaxicomuva
    2nd June Member 0 Permalink

    game crashed    std::terminate called without current exception

  • AtlantisDragon
    18th June Member 0 Permalink

    Issue with ambient heat not reseting when pressing Ctrl+u. I noticed it a while back and the most recent example would be this save: id:3120822. If ambient heat is toggled it is instantly set to the max value and pressing Ctrl+u while the save is paused does nothing. What's interesting is that if you unpause it doesn't stay at the max temp value but returns to it if you press Ctrl+u.

    Edited once by AtlantisDragon. Last: 18th June
  • LBPHacker
    18th June Developer 0 Permalink
    The problem is that you have the "environmental" ambient temperature set to 10000K in settings (bottom right corner, check mark button, scroll down). And btw the shortcut is just U, not Ctrl+U.
  • AtlantisDragon
    18th June Member 0 Permalink

    Ah I see, thanks

  • RCAProduction
    10th August Member 0 Permalink

    A few odd issues.

     

    Issue 1. SPRK jumps between GOLD when the particles are separated by 3 empty spaces. It does NOT jump when the particles are spaced by two. Not only this, but it jumps 3 pixels no matter what is between them! INSL, and even the new RSSS! This not only breaks old saves but it just doesn't make any sense to me. Has to be a bug. Iirc it used to only jump 2 spaces as opposed to a normal conductive element only jumping 1, and INSL still worked. Example save, ID:3139723

     

    UPDATE: The downloaded version for Windows has the 2 pixel gap issue, however the new online version does not. Both have the issue that INSL does absolutely nothing to GOLD.

     

    Issue 2 is that when loading a stamp, it is no longer bound to the borders of the window. If you had saved the entire window in the stamp, it was bound to stay within the borders of the window and automatically centered. Same thing with saving stamps in the corners, etc, as it was an easy zero point reference that was effortless. Now it's rather annoying as you have to manually center it. If this was a feature then it should be a toggle option. 

     

    Issue 3 is that when when you set a gravity mode and then erase the screen, the gravity mode is reset to Vertical every time. This changed and I don't know why. If I changed the gravity mode and am working on something it doesn't make sense to reset it to Vertical every time the screen is erased, as I then have to toggle through the options every time. 

     

    The fourth bug is an odd one and I'm not even sure where to look. I use the old "Texter" Lua script for annotating in the game. Activated by Ctrl+t. Just in making this example save I used it. Then I go to use for a second line... And nothing. Ctrl+t no longer works. Restart, turn the script off, turn it back on, run it from the prompt, nothing. Odd! It did this before but just restarting the game would fix it. Now it doesn't... Funky. 

     

    I'm very impressed with the new updates and the changes in the programming, and hopefully these few issues can be addressed in the next update!

     

    Edited 4 times by RCAProduction. Last: 10th August