489
[MOD] SteamDeck upgrade to 32gb of ram
(lemmy.ml)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 07 Aug 2023
489 points (99.0% liked)
Steam Deck
5727 readers
2 users here now
Universal community link
!steamdeck@lemmy.ml
Rules
- (All of lemmy.ml rules applies)
- Post must be related to the Steam Deck
- No politics
- No drama, we're here to enjoy the Steam Deck
- Don't spam emojis in the comments, be constructive
Order
Models
64GB eMMC LCD
- 64GB eMMC SSD
- 1280 x 800 optically bonded LCD
- 7" Diagonal display size
- up to 60Hz refresh rate
- 7 nm APU
- Wi-Fi 5
- 40Whr battery; 2-8 hours of gameplay (content-dependent)
- 45W Power supply with 1.5m cable
- Carrying case
256GB NVMe LCD
- 256GB NVMe SSD
- 1280 x 800 optically bonded LCD
- 7" Diagonal display size
- up to 60Hz refresh rate
- 7 nm APU
- Wi-Fi 5
- 40Whr battery; 2-8 hours of gameplay (content-dependent)
- 45W Power supply with 1.5m cable
- Carrying case
- Steam profile bundle
512GB NVMe LCD
- 512GB NVMe SSD
- 1280 x 800 optically bonded LCD
- 7" Diagonal display size
- up to 60Hz refresh rate
- 7 nm APU
- Wi-Fi 5
- 40Whr battery; 2-8 hours of gameplay (content-dependent)
- 45W Power supply with 1.5m cable
- Carrying case
- Steam profile bundle
512GB NVMe OLED
- 512GB NVMe SSD
- 1280 x 800 HDR OLED display
- 7.4" Diagonal display size
- up to 90Hz refresh rate
- 6 nm APU
- Wi-Fi 6E
- 50Whr battery; 3-12 hours of gameplay (content-dependent)
- 45W Power supply with 2.5m cable
- Carrying case
- Steam profile bundle
1TB NVMe OLED
- 1TB NVMe SSD
- 1280 x 800 HDR OLED display
- 7.4" Diagonal display size
- up to 90Hz refresh rate
- 6 nm APU
- Wi-Fi 6E
- 50Whr battery; 3-12 hours of gameplay (content-dependent)
- 45W Power supply with 2.5m cable
- Carrying case
- Steam profile bundle
- Exclusive startup movie
- Exclusive virtual keyboard theme
Allowed languages
- Undetermined
- English
founded 3 years ago
MODERATORS
I'm supposed to prove a negative? Do you want me to show a video of games crashing
Games that scale up with play (more players, growing environments, etc) tend to use more RAM over time, and especially such games with mods benefit from more RAM.
Anno, various building/construction games like Cities, Arm, DCS, Warzone whatever. Plenty of games will run with 8-16GB but run better with more. Yes, you can play the game with the "required" specs but that doesn't mean they run great, and CPU/GPU isn't always the bottleneck in larger environments.
I played through GoW on Deck but it definitely had a memory leak that would cause crashing after a bit. More RAM would have extended the play time despite that issue, and I've a couple other titles where the odd crash is likely for similar reasons.
a well modded cities skylines can take 64gb or more of ram.
Your being asked to prove a positive.
Your claim is games crash due to ram.
So give an example of a game that crashes due to ram and you are complete.
Proving a negative would be saying no games crash due to ram, and being asked to prove that.
The amount of bad logic in use by everyone in this post has me wondering how people even get to work in the mornings
I literally did give an example, so now you're just being dickish.
GoW (God of War) had - possibly still has, I haven't checked recently - a memory leak condition. Over time, it will start to stutter out and eventually freeze. TLOU apparently also has/had this issue, though I haven't picked that one up yet myself.
More RAM extends the time one can play but in some cases may also get one past a "hump" to the point where it can do collection and reclaim RAM.
In the case of GoW it seems to be a VRAM issue, but since the Deck uses an APU both system and video memory are allocated from the same pool. That also means that one needs to consider VRAM usage overall in terms of performance, as a game that works well with 16GB on a desktop system with a dedicated GPU (that has dedicated memory) won't actually have 16GB available on the Deck as some of that is allocated to the VRAM pool.
And no, your ask originally was that I prove a game "not running" (which is proving a negative, as the positive version would be "show that game X runs") and then tying it back to RAM. To quote: