MagicBeanDev/Longshot

Watch

Fork 98

Game: Game Crashes and Performance Issues on Steam Deck #401

New issue

Open

opened 2026-11-14 09:36:54 +00:00 by pablo2735 · 1 comment

pablo2735 commented

2026-11-14 09:36:54 +00:00

Longshot version

v3.0.0-rc.3

Channel

Release

What kind of problem

Crash, freeze or black screen

What happened

The game loads the save file without any problems, but once I start playing, I experience frequent stuttering and sudden position changes (teleporting or moving unexpectedly). Eventually, the game crashes.

I am playing on a Steam Deck. The main issue seems to occur during gameplay rather than when loading the save file.

Could you please investigate this issue and let me know if there is a possible fix?

Thank you for your help.

Where in the game

How often

Sometimes

Graphics card and driver version

steam deck

CPU, RAM and operating system

steamos steam deck

Changes from the defaults

No response

longshot_log.txt

Screenshots or video

No response

Before you send it

The problem is still there on the newest release or nightly.
I searched the open issues for it.
I'm not attaching game files, keys, the game's executable, its .bin caches or saves.

### Longshot version v3.0.0-rc.3 ### Channel Release ### What kind of problem Crash, freeze or black screen ### What happened The game loads the save file without any problems, but once I start playing, I experience frequent stuttering and sudden position changes (teleporting or moving unexpectedly). Eventually, the game crashes. I am playing on a Steam Deck. The main issue seems to occur during gameplay rather than when loading the save file. Could you please investigate this issue and let me know if there is a possible fix? Thank you for your help. ### Where in the game aa ### How often Sometimes ### Graphics card and driver version steam deck ### CPU, RAM and operating system steamos steam deck ### Changes from the defaults _No response_ ### longshot_log.txt l ### Screenshots or video _No response_ ### Before you send it - [x] The problem is still there on the newest release or nightly. - [x] I searched the open issues for it. - [x] I'm not attaching game files, keys, the game's executable, its .bin caches or saves.

longshot_log.1.txt

1.1 MiB

longshot_log.2.txt

618 KiB

longshot_log.3.txt

784 KiB

longshot_log.txt

1.8 MiB

longshot_log.1.txt

1.1 MiB

longshot_log.2.txt

618 KiB

longshot_log.3.txt

784 KiB

longshot_log.4.txt

607 KiB

longshot_log.txt

1.8 MiB

longshot_log.4.txt

607 KiB

pablo2735 added the

kind

bug

label

2026-11-14 09:36:54 +00:00

dukenheimer commented

2026-11-15 17:37:52 +00:00

Contributor

Thanks for the report. To say more we need your longshot_log.txt (in the game folder) from a session that crashed, and your settings: the Quality preset, output and render resolution, frame generation, and whether the game is on the microSD card or internal storage.

The most likely cause, from our Deck runs: running out of memory.

On current main (a00c485c, newer than rc.3) at default settings, our Steam Deck OLED reached 11.2-11.4 GB and was stopped for memory in all 3 starts (218-246 MB left).
When memory runs out, SteamOS's earlyoom kills the game, which looks like a crash. The stutter before it fits too: under memory pressure, frames of 100-400 ms come up, and movement can jump.
To check after a crash, run journalctl -b | grep -i earlyoom in desktop mode's Konsole. A line there means memory.

Fixes in review, not in rc.3 or rc.4 yet:

#225 (a Steam Deck profile): on the same Deck its runs finished at 7.8-7.9 GB, 12.2-12.5 fps at 1280x800 with frame generation off.
#223 gives memory back under memory pressure.

What measured better meanwhile:

Internal storage rather than microSD: 15-20% fewer fps on the card in #386's measurement.
A higher GPU clock: in Steam's performance overlay, set a manual GPU clock of 1600 MHz. That was +30% fps on our Deck (15.2 → 19.8 real), at more power (19 W against 10-14 W at stock).

Thanks for the report. To say more we need your `longshot_log.txt` (in the game folder) from a session that crashed, and your settings: the Quality preset, output and render resolution, frame generation, and whether the game is on the microSD card or internal storage. **The most likely cause, from our Deck runs: running out of memory.** - On current main (a00c485c, newer than rc.3) at default settings, our Steam Deck OLED reached 11.2-11.4 GB and was stopped for memory in all 3 starts (218-246 MB left). - When memory runs out, SteamOS's earlyoom kills the game, which looks like a crash. The stutter before it fits too: under memory pressure, frames of 100-400 ms come up, and movement can jump. - To check after a crash, run `journalctl -b | grep -i earlyoom` in desktop mode's Konsole. A line there means memory. **Fixes in review, not in rc.3 or rc.4 yet:** - #225 (a Steam Deck profile): on the same Deck its runs finished at 7.8-7.9 GB, 12.2-12.5 fps at 1280x800 with frame generation off. - #223 gives memory back under memory pressure. **What measured better meanwhile:** - **Internal storage rather than microSD:** 15-20% fewer fps on the card in #386's measurement. - **A higher GPU clock:** in Steam's performance overlay, set a manual GPU clock of 1600 MHz. That was +30% fps on our Deck (15.2 → 19.8 real), at more power (19 W against 10-14 W at stock).