PlayableShow Details
Unknown
Not a long game and you should play Resident Evil 2 first. RE3's first part is before RE2 and after the middle is after RE2.
I Iike to have a L3 as the run button. Also turned on Gyro (as joystick) with a low sensibility for micro ajustments in my aiming. Also lowered the joypad sensibility a bit for better aiming.
I played mostly at 40 fps to have a stable 40. But this game when you get to the second to last boss, you have to be above 45 fps or the boss will just not stop running. You can play this game with fps disabled or just cap it between 45 and 50 perhaps for a more stable run.
In game settings, I left everything as default except FidelityFX Super Resolution 1.0, which I turned off. No need for scaling here. You get a sharper and clear image.
In the Steam Deck Performance tab: Allow Tearing: On, TDP Limit: Off, Manual GPU Limit: 1600 mhz. Now the fps is the tricky part, for a stable perfect fps, cap it at 40 but like said there is a bug with the boss before the last one where he will not stop running around the area. You need to be above 45 fps. I just disable fps toggle and played to the end. This last part ran very well. It's in the city the fps can go up and down.
Only the first cutscene is out-of-sync, which is due to it being pre-rendered.
I would recommend binding the D-Pad to the back buttons, just to make swapping weapons a bit easier.
Perfect experience OOTB
No tinkering had to be done. It booted straight away, and I finished the game without experiencing any bugs, crashes or stutters.
I changed the game's default graphics settings and capped it at 60 Hz for a smooth experience:
- Disabled FSR 1.0 upscaling (The Steam Deck OLED is capable of plaything the game at native resolution)
- Anti-aliasing: FXAA+TAA
- Texture: High (4 GB), Filter Quality: High (ANISO x4)
- Mesh Quality: Medium
- Shadow Quality: Medium, Shadow Cache: On
- Screen Space Reflections: On
- Subsurface Scattering: On
- Volumetric Light Quality: Medium
- Particle Lighting Quality: High
- Ambient Occlusion: FidelityFX CACAO
- Bloom: On, Motion Blur: Off, Depth of Field: On
The game complains about graphics memory, but this can be ignored, as I played through the entire game in long sessions with these settings without any problems or crashes.
Runs perfect
Played the whole game without issues. Keep in mind to turn off mangohud for this game as it will make the game crash.
Did not have any problems when playing.
Runs very well on Steam Deck
DXVK_HDR=1 ENABLE_HDR_WSI=1 gamescope -f -w 3840 -h 2160 -r 120 --hdr-enabled --hdr-debug-force-output --hdr-sdr-content-nits 600 -- env MANGOHUD=1 gamemoderun %command%
Initially I used Proton experimental if not mistaken, but literally the last cutscene was crashing the game, chaging to Proton GE 9.4 worked
I tried it on Windows 11 and ALT Linux, found no problems. Excellent optimization
mangohud %command%
Small shadow errors and occasionally facial hair + eyeballs would freeze in place while the rest of the model moved
Played on the dx11_non-rt beta, with DX12 selected in the in-game Rendering API options.
The game itself is playable but I experienced some minor graphical errors. I haven't really bothered trying to fix them besides changing the Proton version and in-game settings.
Great experience, played it half and half on Deck and Desktop. Rolled credits on Deck. Cloud saves work perfectly.
Low/Medium settings with High (0.5gb) textures. Runs at 60fps almost all of the time. No FSR used (FSR 1 looks really bad at this res) and normal rendering. 12-15w in most instances. On Steam Deck OLED this game has perfect HDR that adds maybe half a watt.
The map become a little hard to decipher and glitches a little once zoomed out but zoomed in its completely legible.
Had to use Proton GE due to Codec issue
Use GE-Proton to avoid a video playback error with normal Proton.
Just works.
may crash with ray tracing like resident evil 2 but I never tried it. ymmv
PROTON_ENABLE_NVAPI=1 mangohud %command%
I had frequent artifact issues when playing with Carlos at the Hospital. The artifacts usually affect Carlo's hair and flashlight, and occasionally the entire screen is engulfed by an artifact.
I didn't notice a pattern between crashes.
11wt, 44fps cap in portable mode
crashes after a while
beat the RE2 with 69 saves!!! Since it will crash in any minute i just closed the game and run it again in order to reset the countdown before the crash. RE3 have the same issue
After switching the proton version to 7.0.6. the game was playable, any other proton version crashed the game for me.
At somepoint in the endgame, the textures of the room strarted stretching which forced me to reload the last save.
Overall my game crashed once, and it hard crashed my computer. It was during a quite cpu intensive moment, so that could have been the reason for the crash.
I had some issues here and there, but overall it was an enjoyable experience. You might need to tinker more or less depending on your hardware I suppose
When the user frequently saves, there is no real issue. Altough freeze/crashes is annoying, but not very common.
Uncertain. Felt like it was not synced during gameplay, might be the same on Windows tough (not that noticeable)
Seemed to crash with fullscreen, altough freezes occured with borderless windowed mode.
Must disable vsync to avoid mouse lag.
The game crashed from time to time when using fullscreen. In Borderless Window mode the game isntead froze and required restart. This happened a couple of times, but happened a few times during the the full playthrough but had a lot of problems during the (spoiler ahead) hospital section, after you get to play as Valentine again. (I explored the hospital as Valentine, crashes occured mainly when entering different rooms)
Weak 'yes', I'm uncertain if changing to Experimental made any differences for me (I did experience the crashes/freezes on both Experimental and Proton 8.0-3)
Crashed often mainly when loading in new places
Other than crashing, the game ran fine. I was able to complete the story of the game and I seem to have been crashing more in the beginning of the game and at the end of the game, the mid-game seemed decently stable. Also I seemed to only be crashing when a new area was being loaded in.
two places in the game crashed the game if I went to fast into it (walking slow went ok)
Finished the game without any bigger issues. Had more or less stable 60 FPS with quality settings (without RT).
gamemoderun VKD3D_CONFIG=dxr11 %command%
Using Proton Experimental, the first cutscene does not load. Using the the GE-Proton7-55, everything works normally.
Throughout my playthrough, the game freezing approximately 6 times. Usually after loading some new area.
Just install and play.
The older DX11 version works well. Current DX12 version looks blurry.
The DX12 version of the game looks blurry, appears to start in windowed mode at a lower resolution and then streches it out to fullscreen. In-game resolution setting has no effect. DX11 version works as expected.
Same as above
Audio seemed to get out of sync during cutscenes
runs smoothly at 60 on balanced graphics preset, possible it would struggle in more demanding areas like boss fights and outdoor zombie bits
played a bit of the hospital section on my deck, mostly filing this since there aren't any other reports as i didn't truly test the game. given how strong the RE engine is and that the 2 remake is verified, i struggle to imagine this game would ever be unplayable, though graphics settings may have be fiddled with until it runs well in all encounters and areas. it appeared i would have a good 2-2.5 hours on battery on the settings i ran it at, though as i wasn't truly testing i didn't really watch/check it. runs well! strange its marked as unsupported!
Final boss glitches if below 60 FPS
Played through the whole game on deck, capped at 45 FPS on medium settings.
Please note that you will have to uncap your framerate at the final boss, otherwise it glitches.
Manually forced compatibility layer to Proton 7.0-4
In one run, grenades caused visual glitches when pointing camera at explosion area. In another section (of the same run), bloom effect accompanying explosion did not fade afterwards; metalic surfaces kept shining.
Game froze in one instance after last boss fight. Required relaunch.
Although not perfectly, it does run well enough to be enjoyed.
