Cursor missing and slower performance in Diablo 2 Resurrected

[1Puck2Puck3Puck4]

Since the latest Steamdeck-Update, the Cursor in Diablo 2 Resurrected became invisible and also the performance got worse than before. The graphics settings are the exact same I didnt change anything and also other settings haven‘t been touched. I know this mist come from the update, because 1 week ago I installed the „beta“ on my stesmdeck, then had the same problem and decided to go back to the stable version where again the cursor appeared again and performance was much better. I dont know how exactly this problem is related to the update but I hope Valve can do something to fix this :(

[Goose Pants]

I’m having the missing cursor issue with Grim Dawn and Titan Quest (both bought and played from Steam, not GOG)

[Ordoferrum]

This has just happened to me as well. Straight after the update. No idea what to do about it.

[zelmon64]

I have a similar performance drop in Fall Guys since the update to 3.6.19. Reverting the OS to 3.5.19 (stable) put it back to normal.

[Time Consumer]

Same issue. Unacceptable!!

Edit: still no cursor

[Milo]

Same issue here!!!

Edit: I found a way to go back to 3.5.19, maybe it's useful for someone...
https://www.youtube.com/watch?v=AN_-Bn1Elz4

[semiten]

same thing，mouse cursor only disappear in 3.6.19，roll back to 3.5.19 can fix it

[Ubeogesh]

I've read somewhere that 3.6 fixed the power management (it allowed too much power before). Is the performance worse with power limiter on or off?

Personally I run D2R on 50 FPS capped, no frame limiter, and I haven't had any sags during my short time with 3.6

[zelmon64]

Originally posted by Ubeogesh:

I've read somewhere that 3.6 fixed the power management (it allowed too much power before). Is the performance worse with power limiter on or off?

I've read the same regarding power management and I don't believe that is the cause (at least not for me). The new power management is supposed to get the same performance at a slightly higher set TDP but I wasn't able to get it back at any TDP. Also reverting to 3.5.19 still uses the new BIOS (and therefore new power management) but the performance goes back to normal.

[Evocaricus]

They really need to fix this. I’ve heard it’s affecting some other games too so maybe that’ll bring it to their attention.
They released 2 updates back to back, and I wasn’t able to notice this. So I can’t even roll it back to 3.5 smh.

[zelmon64]

Originally posted by Evocaricus:

They really need to fix this. I’ve heard it’s affecting some other games too so maybe that’ll bring it to their attention.

Unfortunately the solution might be a system reset (https://www.reddit.com/r/SteamDeck/comments/1gjlw1r/psa_system_reset_since_os_3619/) in which case I don't expect a fix. Are you able to try a reset? I'm hesitant to because I have a lot of non-game stuff set up since it's my main PC.

[Ubeogesh]

I have created a workaround for the disappearing cursor.

For controller binds:

- Add "outer ring binding" to the stick you use to move the cursor with (Left by default, but D2R allows swapping them). Set it to mouse > move by amount and specify 1 pixel in Y or X.

- Then in settings for this joystick, set outer ring size to about 3200 (large amounts won't trigger until you deflect the joystick by a lot, and I found small amounts to work badly too)

- Then in the settings for the "move cursor relative", enable "Hold to repeat (Turbo)" and set repeat rate to the max (1000, i.e. once per 1000ms)

This will force the circular cursor to re-appear whenever you're deflecting your joystick. I have played with this a bit and you barely notice that the issue exists. I don't notice the 1px mouse movement either, because it is overpowered by joystick.

For mouse\keyboard binds with "mouse region" on the trackpad:

- Set "touch" binding on your right trackpad (that uses "mouse region") to Mouse > Move by amount and set either x or y to 1.
- In settings for this "Move Cursor Relative" enable "Hold to Repeat (Turbo)". I have the repeat rate left at default value

This also forces the cursor to be always shown.

[Ubeogesh]

Originally posted by zelmon64:

I've read the same regarding power management and I don't believe that is the cause (at least not for me). The new power management is supposed to get the same performance at a slightly higher set TDP but I wasn't able to get it back at any TDP. Also reverting to 3.5.19 still uses the new BIOS (and therefore new power management) but the performance goes back to normal.

I actually noticed some slowdowns too. It's always locked 50fps when I play solo, but doing some multiplayer baalruns with some fire sorcs does bring the FPS down to low 30s. I haven't noticed this on 3.5, but I didn't do many baalruns there. I run D2R at all lowest settings, except x8 anisotropic filtering, character detail = high, AO = Low and FXAA.

What's a lot more important to me, is that on 3.6 network latency worsened. i am "double teleporting" (teleporting in place once before being able to continue teleporting). This is always an indicator of bad ping. Even on a slow teleporter like an amazon (at 12 frames, i.e. just slightly faster than 2 times per second) this happens. Also in the game list, I see "yellow" ping a lot more often than on 3.5.

[Ubeogesh]

Tried some light 3.5 vs 3.6 performance testing. I find that the hardest area for the game to render is act 3 jungle (spider forest, flayer jungle, great marsh). I seem to have identical performance there, 20-30 FPS when everything is maxed out, 50-80 when everything is bottomed out - on both versions (3.5 and 3.6). Couldn't find a public baalrun to test on it, perhaps the performance degradation is only when there are many players doing things (probably that's CPU performance?)

[Ubeogesh]

Originally posted by Ubeogesh:

What's a lot more important to me, is that on 3.6 network latency worsened. i am "double teleporting" (teleporting in place once before being able to continue teleporting). This is always an indicator of bad ping. Even on a slow teleporter like an amazon (at 12 frames, i.e. just slightly faster than 2 times per second) this happens. Also in the game list, I see "yellow" ping a lot more often than on 3.5.

This was fixed for me by the Steam Deck *Client* update. November 8th update mentions this:
- Fixed a case where WiFi power management settings could fail to be applied at startup.

Pretty sure that was the reason.

I'll still be playing on 3.5 for some time to get a better grasp of performance

[piotrek_1o]

Its still broken...