Hello, Since the Shatteted PD updates of the crystal caves (including beta versions), it seems like the game “lags” as in, seems to skip frames without actually freezing. This happens starting from the 6th level, not before, and stays the rest of the game. The main menu also seems to have the background animations sort of skip the same way but in a less obvious way.

This makes the game a bit annoying to play as sometimes you try to, let’s say, attack, nothing happens so you press again, and suddenly you move where the enemy (who died during the frame skip) previously was, causing a lot of various unintended consequences. The problem shouldn’t be with my phone considering that my system did not change and the game worked perfectly before updating.

Anyone else has this issue?

  • @SolumbranOP
    link
    English
    111 months ago

    Here’s an attempt at a gif, the hosting might be clunky (the stuttering is from the game, not the video):

    Gif

    • 00-EvanM
      link
      English
      111 months ago

      Hm, it’s a bit hard to tell from the GIF, but does some of the skipping happen when you’re just panning the camera and nothing is otherwise happening? If so that does pin things down somewhat, as it means that the error happens even when the game is only processing graphics logic (no game logic).

      • @SolumbranOP
        link
        English
        111 months ago

        Yes, panning also has this stuttering as far as I can tell

        • 00-EvanM
          link
          English
          211 months ago

          Hm, okay, so it’s entirely separate from gameplay logic then. I haven’t made any changes to the game’s core rendering logic in a while as well. I’ll spend a bit of time looking into this, particularly if there is perhaps a memory leak (which would explain why the frameskipping comes on slowly) but I suspect the most likely thing is that this is an issue specific to your device.

          • @SolumbranOP
            link
            English
            111 months ago

            I would agree with the device specific issue, but the bug appeared right after updating (back when the previous update was still in beta) and without any change in my system, thus my suspicions of it being possibly a weird bug.