this post was submitted on 12 Aug 2023
20 points (95.5% liked)
Steam Deck
14908 readers
159 users here now
A place to discuss and support all things Steam Deck.
Replacement for r/steamdeck_linux.
As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title
The following is a list of suggested flairs:
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.
Some more Steam Deck specific flairs:
[Boot Screen] - Custom boot screens/videos.
[Selling] - If you are selling your deck.
These are not enforced, but they are encouraged.
Rules:
- Follow the rules of Sopuli
- Posts must be related to the Steam Deck in an obvious way.
- No piracy, there are other communities for that.
- Discussion of emulators are allowed, but no discussion on how to illegally acquire ROMs.
- This is a place of civil discussion, no trolling.
- Have fun.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Textures are a little weird because they don't affect performance how you might expect. Once you load a texture into memory, it doesn't take any effort to keep displaying it. The main ways textures will impact performance is the time it takes to actually load them - typically through game startup or loading screens. In theory you can also run into stutters while trying to load textures on the fly, e.g. Skyrim loads objects in a cell system, so you're always loading the next thing in front of you as you walk. If your big textures get paged in and out too much you might notice it.
For the Steam Deck's purposes, this basically means that as long as you have enough VRAM to load all those textures, they're basically free to install. Bad things will probably start happening if you run out of VRAM though. There's probably a way to configure the MangoHud onboard the Steam Deck to show how much RAM+VRAM you're using at any given point. If you have enough headroom, I would feel free to install some texture packs and maybe give them a few stress tests in a city or etc.
As for "what mods should I install" that's a giant subjective rabbit hole. You could try a 1-click modlist setup from Wabbajack, or just use one as inspiration.
Thank you, this is very insightful! I believe the Steam Deck has 1GB of VRAM assigned by default - would that be sufficient for most purposes?
Most guides for the Steam Deck seem to focus on installing Vortex. If I understand correctly, Vortex has it's own 'collections' (i.e. modpacks) whereas Wabbajack modlists are installed using the alternative program ModOrganizer2. Speaking of Wabbajack, I did find this specific guide for Linux/Steam Deck. The Dragonborn modpack in particular sounds interesting...
As another alternative, you can also install mods using the built in mod manager? I'm guessing that is a lot more limited.
1GB is nothing - I would be surprised if that's the most you can get. As for mod managers I'm not sure how best to do it on a Steam Deck. You can get Mod Organizer working tmk, but it's not native. I'm not sure what the built-in mod manager is but yeah I would stick with Vortex and MO2
I know you can turn up the VRAM to 4GB if you like. When I eventually give the modpack a try, I'll see how I get on with the default first.