this post was submitted on 15 Dec 2023
5 points (100.0% liked)

Pixel Dungeon

1405 readers
1 users here now

This community is a place to talk strategies, tell stories, or discuss anything related to Pixel Dungeon or its many versions.

Rules:

We have a few title tags for standout posts:

Sister Communities:

founded 1 year ago
MODERATORS
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 0 points 11 months ago (2 children)

It's my bad, bad timing: when I posted I did not see the new update. I had this bug for a while, I simply didn't have the time to post about it.

The bug appeared in the previous update, with the crystal caves (not the gnoll ones), and after updating today it seems that the bug is still there to this point.

[–] [email protected] 1 points 11 months ago

I will chime in with not having seen any such thing, can you maybe get video to show exactly what's happening

[–] [email protected] 1 points 11 months ago (2 children)

It is entirely possible that there are some performance regressions in v2.2.0 or v2.3.0, but it really shouldn't be anything so severe that it causes the game to freeze for seconds at a time. You mention it starting from the 6th level, I'm curious, does this persist if you get further in the game on a run, and then restart your device and continue the run? Mainly I'm interested if the issue is related to getting to a certain point in the game, or just playing the game for a certain amount of time.

[–] [email protected] 1 points 11 months ago

It freezes for a fraction of a second, but it creates a very disturbing effect that also creates visual issues.

It seems like it appears after level 5, and gets worse (at least it feels like it) every time I reach a new zone, every five levels.

Restarting the game often reduces the lags temporarily, for maybe less than a minute, but it might just be my imagination. I also feel like when going back to the first zone, after getting the amulet for example, lags are also reduced.

All of this is just a feeling though, I don't have actual metrics on when the freezes happen and how long they are.

[–] [email protected] 1 points 11 months ago (1 children)

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

Gif

[–] [email protected] 1 points 11 months ago (1 children)

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).

[–] [email protected] 1 points 11 months ago (1 children)

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

[–] [email protected] 2 points 11 months ago (1 children)

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.

[–] [email protected] 1 points 11 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.