UnsupportedShow Details
Unknown
Game gets stuck in the helicopter mission on regular Proton. Forcing to experimental allowed the mission events to trigger correctly allowing me to complete the game. Did not need to install PhysX manually - Steam does it by default now.
physx
The Gunfighters mission has a game breaking bug. Both helicopters stop moving after the first enemy base is destroyed. Unable to progress in the campaign on Linux.
PhysX is required
Graphic Settings stuck at Medium
The game will not launch unless if PhysX is installed (which is available through Winetricks/Protontricks).
Even though the game won't go above medium graphics settings, the single-player campaign is very playable under proton. Apart from some minor stuttering during the cutscenes, the game runs very smoothly for the most part.
Works now
Solved with updates
One late-game bug prevented me from finishing the whole campaign on Deck. Playing through that scene on Windows and finished on Deck
I modified the button layout to be the same as call of duty button layout. I changed the X button so that a short press would reload and a long press would triggered the use command. I also cahnged the sprint button to be toggle on and off rather than hold. I set the back grip buttons to be lean left and right, and that felt very intuitive.
Not sure if cloud saves are supported by this game, but it did not load my game I had started from years back.
There was a game breaking bug where my commander would not initiate the next event, causing a hault of the campaign. I played through that scene on Windows and was able to continue and finish the game on Deck after that scene. (I had to manually transfer the save file with a USB stick)
Overall very good and very fun, but for some reason I was stuck at the one scene, and that was very frustrating. I've read online that others have had similar problems, so it might not be a Deck thing, but switching to Windows fixed it for me.
Required to copy and paste CD key from Steam general game settings
Changed night vision and dynamic HUD to L5 and R5 while reload and jump to X and A. Lean was also missing, buttoned to R4; toggled sprint as KB+M require holding shift.
Particle effects like smoke, dirt, and fire are pixelated
Framerate dips when loading in new assets or environment
Copy/pasting and touchscreen required for CD key first time pop up; default looks for key in a folder that doesn't exist/translate well on Linux
Starts fullscreen, but KDE panel is showing above the picture. Need to Alt+Tab to focus the game
Sometimes can crash if you Alt+Tab
Good experience out of the box
works perfectly out of the box
for dual nvidia GPU use launch options: __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia %command%
Just buy the game, download and click play.
Tried various proton versions, command line fixes etc. to no avail. Game simply does not start.
PROTON_NO_ESYNC=1 PROTON_USE_WINED3D=1 %command%
Borked…
Does not launch. Says executable not found! Please note, that steam install and game installs are on different disks.
General protection fault! History: Address = 0x7a0295 (filename not found) [in Z:\disk\SteamLibrary\steamapps\common\Medal of Honor\Binaries\moh.exe]
After some tests with these settings: https://github.com/ValveSoftware/Proton/#runtime-config-options
I was able to get color, running DirectX with openGL:
Option to RUN the game:
PROTON_USE_WINED3D=1 %command%
Running with vulkan casued missing textues and screen was just black and white, switching to openGL fixed issues. (tested at 2560x1440 res med settings, semi-stable 60fps)
PROTON_NO_ESYNC=1 PROTON_USE_WINED3D=1 %command%
Since my last report (when I reported getting black screen on launch), I tinkered a bit with the config files (in /steamapps/compatdata/47790/pfx/), turning off Motion Blur and bSmoothFrameRate, as well as changing the resolution to 1280x720 and the game launched again! I'm not sure which one of these solved the issue, but I think it was the resolution as I saw someone on Steam forums complain about the same issue, which is probably not exclusive to Linux.
Only on the first launch it worked.
First launch went perfect out of the box. I played for like 30 minutes and quit. Ever since then I haven't been able to even launch the game. It goes directly into the black screen and the only way for me to kill it is to go to tty and use htop.
Significantly improved performance.
Runs as it does on Windows
Slight pausing but that's due down to shader compile
Bad performance, narrow FOV, too sensitive mouse
Mouse is too sensitive
Performance is pretty bad.
1. Mouse Sensitivity
To fix mouse sensitivity edit this file:
steamapps/compatdata/47790/pfx/drive_c/users/steamuser/My Documents/EA Games/Medal of Honor/Config/MOHAInput.ini
and update this parameter:
MouseSensitivity=10.000000
This will loose mouse sensitivity multiplier and now you can fine-tune sensitivity in the game settings menu.
2. FOV
It seems like there are no easy way to fix the FOV since it's hardcoded by developers.
Unknown(< 1 hour with Proton)Runs without any issue.
Unknown(< 1 hour with Proton)
Didn't need to disable esync, but it definitely gave better frame rates by doing so. Played through entire first level without any sort of glitch or issue!
The game started and was able to play the first level just fine. It was slow at first but Disable Esync (PROTON_NO_ESYNC=1 %command%) to gain a massive performance increase. I was able to play at 1080P, 2K, and 4K with no slowdown after this. This game was broken in earlier versions of Proton so this is a nice improvement!
Only tried the single player but it worked very well.
Unknown(2+ hours with Proton)Disable Esync for that game to run. Also there is issue at first launch, when game tells you that it cannot connect to the server but after few tries it launches. Also to remove this window which requires key, you need to delete everything from input, and paste key which Steam gives you when you are launching the game. And sometimes fps drops, but it's still playable. Mouse is too sensitive and settings seems not working for sensitivity adjustments. This game launches without troubles only first time after computer restart, but after that I'm getting Wine error and I need to "force quit" it. Tested in single player.
Unknown(2+ hours with Proton)Unknown(2+ hours with Proton)3 hours into the single player campaign, everything works without issue.
Unknown(2+ hours with Proton)UnknownSingle player. After a while a bug appears where your helicopter get stuck on a hill. Maybe it's a general game bug. However, therefore it's not playable.
Unknown
Single Player - Tried "PROTON_NO_ESYNC=1 %command%" - Did not work - could not connect to server.
Unknown(2+ hours with Proton)After disabling Esync with the latest drivers, Proton version and kernel the game runs great, note my previous report on how to get past the activation crap. I played through the entire campagne without any issues, the performance is great, I played it in 1440p ultra wide and it was running usually around 60fps. I also played it with Dualshock 3 controller only.
Unknown(2+ hours with Proton)UnknownTo get past the activation server crap you just have to keep trying until it works, it took me about 6 tries to get past that part. Once the game tries to launch it will crash without giving an error.
Unknown
