I had a good run but ever since getting to the fire temple it’s crashing every 5 minutes
If you’re using Yuzu, change NVDEC emulation to CPU video decoding on the graphics tab and ASTC recompression to BC3 on the Adv. Graphics tab.
Were you using yuzuEA?
The other thing that helps is increasing the VRAM to 4GB.
That’s actually a misconception, though one that was often propagated so it stuck, unfortunately.
The Steam Deck will dynamically allocate video memory - way below 4GBs, or even larger than 4GBs, regardless of what you set as the UMA framebuffer setting. And it will change this allocation in real time, during each frame, as it monitors memory pressure.
The UMA buffer will indeed give a default “the GPU would like to report that 4GBs of memory are mapped to itself when the driver loads” but the CPU can (and will!) immediately ignore that as soon as needed.
Don’t believe me? If you got 15 minutes to do a little experiment, try setting it at 256MB. 256MB for a device running modern games? No way! It won’t get past the loading screen, right? Well, it will, and the performance will be quite literally identical to setting it at 4GB.
Addendum: some games give warnings of “Your system do not meet the minimum requirements of VRAM” when running on systems with APUs, in that particular case, setting a large UMA buffer will probably work to bypass the warning… But again, performance is similar.
Theoretically I agree with you, but I finally broke down and changed mine due to some instability and I haven’t had a problem since.
It’s completely possible that’s just placebo since my understanding of how it should work says you are right.
Oh, I’m not claiming you’ll get any problems - you won’t, don’t worry, you can set it or leave it be without issues. You don’t have to revert your setting, sorry if my comment gave that impression.
But it will not give you any benefits, really. It’s like setting a different wallpaper - you can do it, it won’t harm anything, but it won’t actually improve games.
My understanding on the advantage for the VRAM change is that RAM gets priority over VRAM. If the systems needs more RAM, it will allocate the VRAM to RAM, and then reallocate back to VRAM, over and over. Increasing the minimum VRAM both keeps the VRAM from dropping below 4GB during high RAM demand and reduces the system swapping RAM between VRAM and RAM. That swapping back and forth can cause stuttering, which is the main thing the VRAM change is trying to fix.
I don’t fault your logic, but unfortunately (and I really do mean unfortunately) that’s not the case. The CPU gets absolute priority and can quickly take memory for itself.
Perhaps on other APU architectures that’s not the case, I wouldn’t know, but with the Steam Deck the CPU is always the maximum priority for memory allocation.
Fire temple was the only place I was crashing on my PC. I just saved repeatedly until I made it through.
I’ve been playing on my Windows PC and Steam Deck (syncthing ftw) and so far so good, but I haven’t gotten to that part yet. I’ll try to remember to report back when I do.
I’ve playing it on the deck by streaming. I get like 20fps if I run it on the deck. Is there a trick I missed to get to 30?
You’ll need a mod to tweak the fps and physic engine to run at 30. There’s a few out there, I’m using 30fps + Dynamic FPS from this github
It runs at 30fps on the real switch so that’s what the physics engine expects.
I do use a dynamic fps mod on my desktop because I get 40-50fps. I’ll try that one out though, the one I’m using doesn’t handle prerendered cutscenes properly. Their speed doesn’t scale with the framerate, so I’m looking for one that fixes that.
+1 for HolographicWing’s TOTK-Mods.
They and bad1dea’s NXCheats have been such a help - https://github.com/bad1dea/NXCheats