This game will need this bug to be fixed in LLVM 7 in order to run on the RADV driver.
https://llvm.org/viewvc/llvm-project?view=revision&revision=340171 Fixed upstream and patcher says it is being backported to LLVM7
seems to play perfectly here too with one caveat - when I start the game there is a message saying it was unable to reach the game's servers. probably same issue as #162
https://gist.github.com/Cuddlypuff/a518019d119623d9a1b7552e284c1f6d
Metal Gear Solid 5: TPP (287700)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/1131.
@NaltanHusky posted on 2018-09-01T14:50:07:
Crashes on startup.
Running Debian 9
EDIT: There was a whitelist request for this game. I'm guessing that it worked for them because they have an nvidia gpu... I'm using an AMD cpu/gpu
<log dump trimmed due to gratuitous length, see [#1131](/issue/ValveSoftware/Proton/1131) for the log. please use a gist for large pastes>
Ubuntu 16.04, NVIDIA GTX 970, Proton 3.7-5 Beta:
| Test | Result |
|---|---|
| Singleplayer | Working as expected |
| Local Co-op | N/A |
| Online Multiplayer | Partially working^ |
| Configuration | ... |
|---|---|
| Input | Steam Controller |
| Display | 1920x1080 |
| Fullscreen | Yes |
| Preset | Medium^^ |
| VSync | Enabled |
| API | DX11 |
^ Unable to connect to online servers
^^ Default graphics preset is High
NOTE: Frequent screen tearing if Vsync setting is Disabled
How are you guys launching the game?
I can't get the game to launch as it can't make connection with the servers.
It complains that "the server is not reachable, check your internet connection". If I try launching the game with Steam in offline mode (or by unplugging my ethernet) as a way to potentially work around this, it states that "Steam is currently in offline mode, for the first launch go in online mode".
Tried with both 3.7-3 and 3.7-6 to the same result.
@DougTy - I started the game with default Proton and it just ran. Didn't do anything special on top of that. I did get a network error in the game menu, but I assume this only affects the online components of the game. I was able to spawn and run around in my base (although I didn't try starting a new game)
Nope, not working on Debian. Characters are completely messed up.
Tested on Debian Stretch AMD64 / 390.77 / KDE with locale FR.
Reborn OS (Arch Linux)
AMD FX, Nvidia Geforce GTX 950 v.396.54-1
Proton Beta 3.7-4/5/6
When I start the game there is a message saying it was unable to reach the game's servers.
Hello @jaubin, if possible, please retest with nvidia 396.51 or newer.
When they're available on Debian I will.
Envoyé depuis Yahoo Mail pour Android
Le lun., sept. 10, 2018 à 22:58, kisak-valve[email protected] a écrit :
Hello @jaubin, if possible, please retest with nvidia 396.51 or newer.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
I am also having a connection issue, Manjaro Linux.
Any workaround or fix?
I am also also having a connection issue on solus linux.
Any workaround or fix?
steam system information: https://hasteb.in/ewapoqal.yaml
double-checked if anything had changed since my last report since so many people have trouble starting the game, but the game loads fine on my end still (tried with 3.7-6 this time, no difference). I still get the popup at the beginning saying I won't be able to use online features, but I can play the singleplayer game fine.
same sysinfo as before
What do you click when you get the popup?
I get "Retry" or "next".
Retry just makes the pop-up loop over and over and 'next' leads me to a link which isn't overly helpful because there is nowhere for me to paste the code?
(Also, I am using 3.7-6 BETA at this time also, thanks!).
I'd like to add a quick edit that the link provided above is of no use to me (or @DougTy because it is for a different issue altogether).
@tunanachos I don't think we're talking about the same popup - I think you're getting the outside-of-game popup that complains about not being able to reach some server, my game starts fine, but then from within the game it warns that I won't have access to the online features (there's no choice after that except to acknowledge it and continue)
@Cuddlypuff No I don't think we are, I'm aware MGO isn't really viable but that isn't my issue.
Me and @DougTy cannot launch the game at all, instead (assuming he has the same issue as me) you get a pop-up stating that it cannot connect to servers (I assume DRM?).
Is it worth me making a post about this somewhere other than what I've done here? Seems like I am not the only one facing this issue (not to mention it's a bit annoying MGS:V plays so well with Linux+Proton but the DRM is stopping us), forgive my question - I don't often use Github etc, confuses me lol :)
@tunanachos I think @kisak-valve has been merging issues of the same game under the same report, unless they're officially supported games then they track all separate issues independently.
Did you ever start the game on any other platform? I had started the game using Lutris previously, and my Proton session is able to find that cloud save and run from there, so maybe that's where our experience differs?
Just brainstorming here: For those who have it working, had you launched the game at least once on Windows before? Maybe it does some sort of setup the first time you start it, which doesn't work on Linux.
Gave me a warning about inaccessible online mode, but apart from that it works just fine for me on Ubuntu 18.04 with Proton 3.7.6. I had played it on Windows first though, hence my question.
@DanMan not on windows, but I had started the game previously though Lutris without issues (no idea what versions of wine/dxvk i wouldve been on)
@tunanachos I think @kisak-valve has been merging issues of the same game under the same report, unless they're officially supported games then they track all separate issues independently.
Did you ever start the game on any other platform? I had started the game using Lutris previously, and my Proton session is able to find that cloud save and run from there, so maybe that's where our experience differs?
@Cuddlypuff Thanks for the reply
I had a go at installing it with Lutris but that was even more-so uneventful (forgive me, I fail to remember what happened but the abridged version is, it didn't work) .
I can reinstall it and maybe try running it in a console and see what the issue is, but as far as I can tell, it's just bypassing/connecting the DRM to the server which is my main issue (Running it purely with Steam+Proton).
I wonder if it has anything to do with my WM? I use i3wm and sometimes I feels as if games don't like it.?
@DanMan I don't think this is the case, I may be wrong but unless you mean a VM Linux and Windows would be installed in entirely different locations, with different paths - most likely both OS's wouldn't hop over and check the other, if that makes sense? (happy to be wrong on this).
Just brainstorming here: For those who have it working, had you launched the game at least once on Windows before? Maybe it does some sort of setup the first time you start it, which doesn't work on Linux.
I've played through the game on windows already. but I reinstalled it for linux. It won't get past downloading Microsoft redistributable
According to [a comment in #162](https://github.com/ValveSoftware/Proton/issues/162#issuecomment-421111573), Proton is based off of wine 3.7 & a large network issue was fixed in 3.9. Perhaps when @Cuddlypuff ran the game first in Lutris with system native wine >3.7, it activated the game's DRM there, so that pre-launch popup doesn't come up anymore when running the game in Proton because it's already activated.
I've actually tried the game with wine-staging 3.15 and it plays fine, no such issue, so I'm thinking this is just a case of Proton being based on too old a version of wine.
Hi @DougTy are you now able to play MGS:V without issue now? How did you go about setting it up? Just a usual Wine directory? No extra libs or anything?
I can happily redownload it and give it another go, especially if one of the only other people I've found with the same issue as me has now got it working.
@tunanachos Kinda. It works decently well with wine-staging 3.15 & DXVK 0.71. Lighting is a bit weird but the game launches & plays fine, however it seems to constantly corrupt my saves. I'll play the game without issue for however long I want, but upon launching the game a second time it claims my saves are corrupted and forces me to start from the beginning again. I haven't really put too much effort into debugging this so perhaps someone could get it to work -- though this isn't a Proton issue and should probably be taken up on AppDB instead.
There is no network error with wine-staging, but I definitely can't get the game to run in Proton still, even when using the game's compatdata folder as my WINEPREFIX with wine-staging first. Proton always claims that I have no internet connection. I believe Proton will need to be rebased to a newer version of wine in order to fix this.
Mmm, I might give it a couple of months and see if any progress has been made. I'd rather run it through Proton for simplicity sake and this save-game issue is off-putting to say the least (I have a bunch of Windows games I'm working through at the moment that work great with Proton, so I'm not lost for time killers).
I don't know whats worse; being able to play but not save or not being able to play at all...
Guess you could just tab out and leave your PC on forever until you're ready to quit lol.
Thanks for the reply, I'll see whats happening around Christmas if there isn't much of an update.
-Cheers
@Cuddlypuff No I don't think we are, I'm aware MGO isn't really viable but that isn't my issue.
Me and @DougTy cannot launch the game at all, instead (assuming he has the same issue as me) you get a pop-up stating that it cannot connect to servers (I assume DRM?).
Is it worth me making a post about this somewhere other than what I've done here? Seems like I am not the only one facing this issue (not to mention it's a bit annoying MGS:V plays so well with Linux+Proton but the DRM is stopping us), forgive my question - I don't often use Github etc, confuses me lol :)
I've got the same error on Arch Linux when I started it with steam-native but it works with steam-runtime. I still get the ingame warning about the failed connection tho.
@DougTy Same issue with me. It loads and plays perfectly, aside from the servers not resolving, but after extended periods of play the game starts corrupting my saves. I started backing up my files after every session and stepped through the missions. Your results may vary, but after mission 6 "Where Do the Bees Sleep" it seemed to start corrupting my saves.
From what I've read online, there seems to be a rich history of this game corrupting saves due to the game state in relation to the companions. All the complaints seemed to peter out after 2015, so my guess is the devs fixed those issues. Running it through proton might have revealed a few more.
4.18.10-arch1-1-ARCH
AMD Ryzen 5 2600 (12) @ 3.400GHz
NVIDIA GeForce GTX 1070 Ti
Seems to run just fine with NVIDIA GeForce GTX 1050Ti, but after several hours of gameplay some sound issues show up, like crackling and echo, this is also happening with a few other titles like Outlast 2 and Dark Souls Remastered, strangely enough this issues appears after several consecutive hours of gameplay and is remedied by restarting the game. All system sounds are perfectly fine and no linux-native games have this issue.
Sounds like exactly the reason why you'd either want to install xact via winetricks, or wait for FAudio.
for those who have problems: give the game a first launch in "steam runtime" mode! after that it should be able to run also in "native steam" ;) your welcome
but i get also the message that i am not be able to connect to servers for some online features....singlplayer just runs perfect though...
any solution on that?
Game starts fine for me, gamepad works and performance is great. However, online mode doesn't work at all, whenever you start the game it tells you it can't connect to the servers. Also whenever I change the graphics options, the whole screen starts to flicker like crazy and I have to restart the game. The settings will be accepted and the game runs fine after restarting, though.
Proton Version: 3.16-4
Proton Log: steam-287700.log
Sysinfo: https://gist.github.com/NoXPhasma/9ed85e6b0602b656c812acd013ee121f
I can't play because menu elements are in the wrong position and most text is upside down. Also up/down in menus are inverted.
On ProtonDB, some other users have the same issue and one of them said this happened after they installed SteamVR and they fixed it by completely reinstalling steam. Unfortunately I have a very slow internet connection so I can't really reinstall everything or remove SteamVR since I use it and it's quite heavy.
Is there some trick to maybe hide SteamVR integration to the game or replicate the environment in which there is no SteamVR somehow?
Hello @fazo96, please copy your system information from steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. Additionally, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.
Hi,
Same issue there. Seems to be driver-related. Recent NVidia drivers are required.
My system info :
Informations de l'ordinateur : Fabricant : Unknown Modèle : Unknown Type : Ordinateur de bureau Aucun écran tactile détecté
Processeur : Fabricant du CPU : GenuineIntel Marque du processeur : Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz Famille du processeur : 0x6 Modèle du processeur : 0x3c Révision processeur : 0x3 Type de processeur : 0x0 Fréquence : 4000 Mhz 8 processeurs logiques 4 processeurs physiques HyperThreading : Pris en charge FCMOV : Pris en charge SSE2 : Pris en charge SSE3 : Pris en charge SSSE3 : Pris en charge SSE4a : Non pris en charge SSE41 : Pris en charge SSE42 : Pris en charge AES : Pris en charge AVX : Pris en charge CMPXCHG16B : Pris en charge LAHF/SAHF : Pris en charge PrefetchW : Non pris en charge
Version du système d'exploitation : Debian GNU/Linux 9.6 (stretch) (64 bits) Nom du noyau : Linux Version du noyau : 4.9.0-8-amd64 Éditeur du serveur X : The X.Org Foundation Version du serveur X : 11902000 Gestionnaire de fenêtres X : KWin Version d'exécution Steam : steam-runtime-beta-release_2018-11-23
Carte graphique : Pilote : NVIDIA Corporation GeForce GTX 1070/PCIe/SSE2 Version du pilote : 4.6.0 NVIDIA 390.87 Version OpenGL : 4.6 Profondeur de couleur du bureau : 24 bits par pixel Taux de rafraîchissement du moniteur : 60 Hz ID fabricant : 0x10de ID périphérique : 0x1b81 Révision non détectée Nombre de moniteurs : 1 Nombre de cartes vidéo logiques : 1 Résolution de l'affichage principal : 1920 x 1080 Résolution du bureau : 1920 x 1080 Taille de l'affichage principal : 20.04" x 11.26" (22.95" diag) 50.9cm x 28.6cm (58.3cm diag) Bus principal : PCI Express 16x Mémoire vidéo principale : 8192 Mo Modes MSAA pris en charge : 2x 4x 8x 16x
Carte son : Périphérique audio : Realtek ALC892
Mémoire : RAM : 32122 Mo
Divers : Langue de l'interface : Français LANGUE : fr_FR.UTF-8 Espace disque total disponible : 938580 Mo Plus grand bloc disponible sur le disque dur : 60727 Mo Casque VR : aucun détecté
Rapports d'échec récent :
Le samedi 1 décembre 2018 à 16:30:34 UTC+1, kisak-valve <[email protected]> a écrit :
Hello @fazo96, please copy your system information from steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. Additionally, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
The nVidia 390.xx driver series is unsupported by Proton, please retest with nvidia 396.54 or 410.xx.
(Just noticed I've already recommended this...)
Or even 415.xx would probably do!
I can't play because menu elements are in the wrong position and most text is upside down. Also up/down in menus are inverted.
On ProtonDB, some other users have the same issue and one of them said this happened after they installed SteamVR and they fixed it by completely reinstalling steam. Unfortunately I have a very slow internet connection so I can't really reinstall everything or remove SteamVR since I use it and it's quite heavy.
Is there some trick to maybe hide SteamVR integration to the game or replicate the environment in which there is no SteamVR somehow?
Here is my system information @kisak-valve : https://gist.github.com/fazo96/03943c8a666b5ae529db6adbbf846cee
Not sure if it helps to know but other Proton games run just fine, even the ones requiring transform feedback such as GORN on SteamVR.
This is the log file, at the end I force closed the game because I did not want to sit through the unskippable cinematic at the start for the milionth time. The bug is noteceable almost immediately after starting the game due to some unreadable dialogs rendering. Also I tried disabling the steam overlay and nothing changed
@fazo96, there's a lot of INTEL-MESA: warning: Haswell Vulkan support is incomplete lines in your log which hints that the game is using your Intel chipset to render. Please temporarily move /usr/share/vulkan/icd.d/intel_icd.*.json somewhere out of the way and retest.
Here's the new log with the intel files removed. I also tried disabling the steam overlay.
It did not work and the issue is still there. I don't think any game is rendering with the Intel graphics because I play at 2540x1440 and get good performance with high settings in other proton games.
@kisak-valve I tried something else: I installed the game using Lutris, so it runs on Wine + DVXK using Steam for Windows inside wine (proton/steam play not used at all)
The game runs perfectly.
Wine version: tkg-3.19-x86_64 (installed using Lutris)
DXVK version: 0.91
Everything else is the same as before except I updated my drivers to the latest Vulkan Beta, version 415.18.04
Running the game in Proton though Steam for Linux still has the same distorted graphics as before.
Running the game in Wine through Lutris works perfectly.
I think this makes the problem specific to Proton. If I have time, I'll try uninstalling SteamVR from Proton which according to another user fixes the problem with this game.
@kisak-valve I can confirm uninstalling SteamVR fixes my problem, the game on Proton now runs just as well as DXVK + Wine, however only if SteamVR is not installed.
Maybe this could be fixed by a flag that hides SteamVR to the game? The game has no VR elements that I know of.
I can also confirm that uninstalling SteamVR fixes the rendering issues with upside-down text and the game runs fine now. Though I don't understand how that could be related.
With Proton 3.16-6 the online mode works now without any problem. The screen flicker after changing the graphics option is also gone. With that all remaining issues are fixed for me now.
Sysinfo: https://gist.github.com/NoXPhasma/4273d8bfe7dc611fb74967ea44936989
Proton: 3.16-6
With Proton 3.16-6 the online mode works, the glitches when changing graphics options are fixed, and the glitches when SteamVR is installed are gone as well!
While online works now that is only one issue, using a mouse and keyboard is still impossible. I got to have a controller plugged in or the camera pans out of control, and the mouse won't navigate the map.
This stems from a windows bug that is "exacerbated" under wine: https://steamcommunity.com/app/287700/discussions/0/527274088389275023/
Can anyone can figure out a solution to this?
I can also confirm that uninstalling SteamVR fixes the rendering issues with upside-down text and the game runs fine now.
Agreed, the application now appears to be working as expected with Proton 3.16-6 once SteamVR is uninstalled:
One problem I have is with the Steam overlay. If you bring it up, the same XB1 gamepad input is also still registered in the game. Especially evil on the title screen where you can delete your progress by activating a single menu item.
@DanMan Is this really a Proton specific behavior or does that happen on Windows as well? I've never palyed this game on Windows, so I have no idea. But for what I can say about other games, if the game pauses on Windows in Steam Overlay, it does the same with Proton for me.
Hi,
The same phenomenon (reversed chars, unplayable game, and so on) also appears w/ NVidia 410.93 driver.
My env :- Debian Buester w/ KDE- Driver 410.93- Locale : french
Le mardi 1 janvier 2019 à 14:11:19 UTC+1, NoXPhasma [email protected] a écrit :
@DanMan Is this really a Proton specific behavior or does that happen on Windows as well? I've never palyed this game on Windows, so I have no idea. But for what I can say about other games, if the game pauses on Windows in Steam Overlay, it does the same with Proton for me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Still upside down characters with Proton 4.2.2 and Buster and NVidia 410.93. (LOCALE is French, running on KDE)
Any idea ?
Okay I've found the bug :- If SteamVR is installed, the game is completely borked.- Without SteamVR all is fine.
Le mardi 12 mars 2019 à 06:26:43 UTC+1, Julien Aubin [email protected] a écrit :
Hi,
The same phenomenon (reversed chars, unplayable game, and so on) also appears w/ NVidia 410.93 driver.
My env :- Debian Buester w/ KDE- Driver 410.93- Locale : french
Le mardi 1 janvier 2019 à 14:11:19 UTC+1, NoXPhasma [email protected] a écrit :
@DanMan Is this really a Proton specific behavior or does that happen on Windows as well? I've never palyed this game on Windows, so I have no idea. But for what I can say about other games, if the game pauses on Windows in Steam Overlay, it does the same with Proton for me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
I have started playing this recently with proton 4.2-3 and it runs very well out of the box, however it crashed on my randomly twice so far. The crashes might be audio related, as voices started looping until the sound completely disappeared and the game ultimately crashed. Haven't found a way to reproduce this yet and i'm not sure how to gather more info.
Had another random crash, here is the log file generated by PROTON_LOG=1:
steam-287700.log
FWIW it also crashes the same way with 3.16-9.
OK, i upgraded my bios and removed my slight cpu and ram overclock and now the crashes are gone.
For some reason the overclock causes MGS5 to crash while it ran stable for hundreds of hours with other demanding games, no idea what's going on there.
Anyways, the game now runs perfectly out of the box with porton 4.2-3, sorry for the noise.
This game wont start for me (show it's running and than close) with proton 4.11 and 4.2.
What i tried already:
Link for steam.log https://gist.githubusercontent.com/haterino/0d7cae34281f5210f4402372e62b2568/raw/8f69c9c5916204344f50ba027e5d23fe25709e6c/steam-287700.log
My steamapps is located on other drive, the same as the "/", since it is ext4 and ssd. "~/.steam/" is on an ext4 hd.
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 3 2200G with Radeon Vega Graphics
Speed: 3500 Mhz
4 logical processors
4 physical processors
HyperThreading: Unsupported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
Debian GNU/Linux bullseye/sid (64 bit)
Kernel Name: Linux
Kernel Version: 5.2.4-towo.3-siduction-amd64
X Server Vendor: The X.Org Foundation
X Server Release: 12004000
X Window Manager: KWin
Steam Runtime Version: steam-runtime_0.20190711.3
Video Card:
Driver: X.Org Radeon RX 570 Series (POLARIS10, DRM 3.32.0, 5.2.4-towo.3-siduction-amd64, LLVM 8.0.1)
Driver Version: 4.5 (Compatibility Profile) Mesa 19.1.2
OpenGL Version: 4.5
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID: 0x1002
DeviceID: 0x67df
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 1366 x 768
Desktop Resolution: 1366 x 768
Primary Display Size: 16.14" x 9.06" (18.50" diag)
41.0cm x 23.0cm (47.0cm diag)
Primary VRAM: 4096 MB
Sound card:
Audio device: ATI R6xx HDMI
Memory:
RAM: 7983 Mb
hillo@hillo-pc:~$ python --version Python 2.7.16+ hillo@hillo-pc:~$ python3 --version Python 3.7.4
Can't find any applicable solution whatsoever
MGSV (287700) Crashes Immediately After Launch
Issue transferred from https://github.com/ValveSoftware/Proton/issues/2940.
@lo4952 posted on 2019-08-02T16:25:02:
<!-
steam-287700.log
PROTON_LOG=1 %command% to the game's launch options and drag$HOME/steam-$APPID.log into this issue report -->MGSV crashes immediately after launch, logs show the error "wine: Unhandled page fault on read access to 0x000005e7 at address 0x7f4bfc0d45b3 (thread 0056)" on line 645 of steam log.
Occurs on every launch of MGSV. Have already tried verifying file integrity, using other versions of proton.
Crash not reproducible here.
GPU : RTX 2070 SUPERDriver : NVidia 430.34Kernel : 4.19.0-5Proton : 4.11-1
Debian Buster.
Le vendredi 2 août 2019 à 18:37:13 UTC+2, kisak-valve [email protected] a écrit :
MGSV (287700) Crashes Immediately After Launch
Issue transferred from #2940.
@lo4952 posted on 2019-08-02T16:25:02:
Compatibility Report
System Information
I confirm:
<!-
steam-287700.log
Symptoms
MGSV crashes immediately after launch, logs show the error "wine: Unhandled page fault on read access to 0x000005e7 at address 0x7f4bfc0d45b3 (thread 0056)" on line 645 of steam log.
Reproduction
Occurs on every launch of MGSV. Have already tried verifying file integrity, using other versions of proton.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Crash not reproducible here. GPU : RTX 2070 SUPERDriver : NVidia 430.34Kernel : 4.19.0-5Proton : 4.11-1 Debian Buster. Le vendredi 2 août 2019 à 18:37:13 UTC+2, kisak-valve [email protected] a écrit : MGSV (287700) Crashes Immediately After Launch Issue transferred from #2940. @lo4952 posted on 2019-08-02T16:25:02: Compatibility Report - Name of the game with compatibility issues: Metal Gear Solid V: The Phantom Pain - Steam AppID of the game: 287700 System Information - GPU: GTX 1060 6GB - Driver/LLVM version: nvidia 430.40 - Kernel version: 5.0.0-23-generic - Link to full system information report as Gist: Full Info Report - Proton version: 4.11-1 I confirm: - [ X ] that I haven't found an existing compatibility report for this game. - [ X ] that I have checked whether there are updates for my system available. <!- steam-287700.log - Please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into this issue report --> Symptoms MGSV crashes immediately after launch, logs show the error "wine: Unhandled page fault on read access to 0x000005e7 at address 0x7f4bfc0d45b3 (thread 0056)" on line 645 of steam log. Reproduction Occurs on every launch of MGSV. Have already tried verifying file integrity, using other versions of proton. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Fixed the error by reinstalling various libraries, ended up being an issue with a bad install of DXVK.
Fixed the error by reinstalling various libraries, ended up being an issue with a bad install of DXVK.
And would you care to explain how exactly you did that?
Fixed the error by reinstalling various libraries, ended up being an issue with a bad install of DXVK.
And would you care to explain how exactly you did that?
The built-in DXVK library as part of nVidia 430 was insufficient for this game specifically, despite working with many other DXVK-requiring titles. Instead, I followed the guide on this site and used the debian packages. Once those were installed everything worked great.
Yes, thank you. It seems that for me on the newest Manjaro KDE release (manjaro-kde-18.0.4-stable-x86_64) it works out of the box. It seems that Proton has issues running games from NTFS drives and moving the game to my ext4 SSD main drive and it runs perfectly out of the box.
If SteamVR is installed, the game is completely borked.- Without SteamVR all is fine.
EDIT: This issue now appears to be resolved with Proton 4.11-11, many thanks to all involved!
This issue still exists, with general text and menu options appearing upside-down when SteamVR is installed, as reported by @jaubin and others:


Library > Tools within the Steam client and install SteamVRLibrary using the Steam client and press the Play buttonAnybody else having issues launching the game with 4.11-8?
When launching the game, a window of the game appears with the 3 loading dots at the top right. These dots do not move, and the screen is then frozen. Tried this multiple times with the same result. To get it working I had to run MGS5 with Proton version 4.2-9.
Launch game.
Hello @barbrastreisand, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.
Same here, it does work with WINEDLLOVERRIDES=dxgi=n on Proton 4.11-8 though.
Proton log:
steam-287700.log
Still not working for me, even with WINEDLLOVERRIDES=dxgi=n set as a launch option.
Hiere the WINEDLLOVERRIDES was necessary to make things work.
Using NVidia blob 430.40 w/ NVidia GF 2070S on Debian Buster / KDE / French.
Le jeudi 14 novembre 2019 à 20:23:17 UTC+1, barbrastreisand <[email protected]> a écrit :
Still not working for me, even with WINEDLLOVERRIDES=dxgi=n set as a launch option.
steam-287700.log
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
If you're setting it in the Steam launch options, I think you need to set it like this: WINEDLLOVERRIDES="dxgi=n" %command%. Notice the quotes, they're important here.
WINEDLLOVERRIDES="dxgi=n" %command%
I don't have it with quotes and it works here. Anyhow, quotes are usually unnecessary in this position (unless Steam does something in an non-standard way). Unless the quotes were put around %command% I don't see why it would make a difference
So I added %command% to the end of WINEDLLOVERRIDES=dxgi=n and it works now. Is %command% just something you need to put at the end of any Launch Options? Did I miss this somewhere?
So I added
%command%to the end ofWINEDLLOVERRIDES=dxgi=nand it works now. Is%command%just something you need to put at the end of any Launch Options? Did I miss this somewhere?
I think it is required when you are setting environment variables, as otherwise what's in the launch options field is simply appended to the regular command line.
C:\...\mgsvtpp.exe WINEDLLOVERRIDES=dxgi=n does nothing as the WINEDLL bit is not interpreted by the MGSVTPP.exe executable. If for instance you were to set an hypothetical --debug launch option instead, I think you could just type "--debug" in the field and the launcher figures out it needs to append that to the command line.
The WINEDLLOVERRIDES workaround should no longer be required with Proton 4.11-10.
Proton 4.11-11, having mouse issues with a graphics tablet connected (Huion instead of Wacom, but maybe related to #3162?). Launching the game with a tablet connected results in both camera and map cursor moving left and upwards. Unplugging the tablet fixes the camera, but not the map cursor. Launching without a tablet connected causes no issues.
Logfile with a tablet connected:
steam-287700.log
System information:
Gist
I get constant network problems and frequent disconnects. Using 4.11-12.
For me the colors are extremely washed out in this game. Its runs with very good performance, but the colors are completely off.
Arch Linux with Nvidia 440.44 on an Optimus Laptop and Proton 4.11-12.
With 5.0-3, there is still a problem with the network.
steam-287700.log
I think this line is the most telling.
11420.060:0030:0065:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
And then all the following.
11420.981:0030:0065:fixme:winhttp:set_cookies unhandled attribute L"HttpOnly"
@sakuramboo, I doubt any of these have to do with the constant network issues. NTLM is the protocol to authenticate Windows machines in a local network (file shares), while HttpOnly refers to a feature of cookies that tell a navigator not to accidentally send cookies over HTTP too.
i change the save path of the game check the video and it's works with me
https://www.youtube.com/watch?v=2iLEZsxDxH8&feature=youtu.be
MGSV:TPP Crashes after second mission
Issue transferred from https://github.com/ValveSoftware/Proton/issues/4767.
@SirRolls posted on 2021-04-20T21:48:22:
After extracting Miller, the ending cutscene plays, but crashes after attempting to load the next
Hello @SirRolls, wine: Unhandled division by zero at address 00007F8EB29DDE3A (thread 02b8), starting debugger... looks like a line of interest in your log.
Looking into it, and trying a few things i cant seem to get it to work on the zen kernel. I'll give it a shot on a stock kernel
EDIT: Looking into, it looks like an architecture mismatch (32/64bit) I'll see if its a library problem
Edit2: Interestingly, lowering the proton version to 5.10 has seemed to fix the issue. Included below is the output from 5.10
steam-287700.log
@kisak-valve
I lowered the version to 5.13 and it works but it definitely doesn't work with 6.3; looks like a regression :/
Hello @ThisNekoGuy, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.
@kisak-valve Sorry for being late to respond
I've already progressed passed this point and the game only permits for one save file; do you know if there's something I can do to work around this to get back to you on the log and other data?
You can get savegames for many levels here: https://steamcommunity.com/sharedfiles/filedetails/?id=523041722 but
pirated copies are known for some gamecrash problem with the first mission
Just sayin'. The game might actually try to detect pirated copies and running it through certain Proton versions might cause a false positive.
I've had savegame corruption issues before, like I said further up. But currently it works fine with 6.10-GE-1 for me.
Might want to try the 6.3-5 RC, because MGS5 is listed among the improved games. I think there's a video cutscene right after the mission that was mentioned
Just sayin'. I've had savegame corruption issues before, like I said further
up. But currently it works fine with 6.10-GE-1 for me.
Hi,
There are also some savegame corruption issues in the game after a very
specific mission if you do some specific action. Forgot which one :
That particular bug was supposedly fixed a long time ago though: https://www.rockpapershotgun.com/metal-gear-solid-v-quiet-bug
For me it happened a lot earlier in the game at 2 different times.
The games still plays the cutscene in Phantom Limbs at 2 or so fps. Same with the chapter 2 trailer, only time I've noticed it.
I was revisiting this yesterday, playing on Proton 7.0-4, and I noticed the FMV cutscenes play back at double speed and audio pitch, which, albeit hilarious, is kind of a problem. It's also annoying to reproduce, because the first FMV is after the initial 20+ minute long hospital escape sequence. I switched to GE 7-31, I'll just keep playing and hope I encounter another FMV to test.
Update: Tested some other Proton versions.
In Proton 5.13, the cutscene is skipped, pretty seamlessly. Someone who didn't know better wouldn't notice the cutscene was missing...
In Proton 6.3, the cutscene renders slowly at ~1FPS
In Proton 7.0 and onward (including Experimental bleeding edge and GE), the cutscene plays at 60 FPS (double speed.)
Here's a save file if any developers would like to reproduce the issue faster.
It's in a .tar.gz with three files, since I don't actually know which one of them is the save itself vs. the character avatar data, etc.
This should be placed in $STEAM/userdata/bunchofnumbers/311340/remote
Then simply hit Continue at the main menu and skip the first two in-engine cutscenes. Then the mfplat video will play.
save.tar.gz
I was revisiting this yesterday, playing on Proton 7.0-4, and I noticed the FMV cutscenes play back at double speed and audio pitch, which, albeit hilarious, is kind of a problem. It's also annoying to reproduce, because the first FMV is after the initial 20+ minute long hospital escape sequence. I switched to GE 7-31, I'll just keep playing and hope I encounter another FMV to test.
Still affected in Proton 8.0-2. 😐
Interestingly, at the current GE the prerendered cinematic intro to Chapter 1 just got skipped entirely after showing the first frame for about half a second
Using proton 8.0 or experimental:
After a while of playing, there starts to be a micro stuttering every a random number of seconds (every more than 30 seconds)
Metal gear online - controls don't work
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7458.
@mangonebula posted on 2024-01-29T19:29:53:
On steamdeck
The controls on the steamdeck don't work. The game thinks that is in keyboard and mouse mode. The joysticks don't move the character or allow you to look.
The controls work fine in the main game, but metal gear online is unplayable
METAL GEAR SOLID V: THE PHANTOM PAIN problems when changing chapters
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7918.
@cain-dev posted on 2024-07-21T20:48:13:
Can't cause i've changed chapters now
The game breaks or fast forward after doing any mission to change chapters
Just go to any mission that ends a chapter, things will break or fast forward
Attaching logs:
WINEDEBUG=+xinput,+plugplay,+dinput,+hid,+rawinput PROTON_LOG=1 %command%
SDL_HIDAPI_DISABLE_LIBUSB=1 SDL_HINT_HIDAPI_LIBUSB=1 SDL_HINT_JOYSTICK_HIDAPI=0 SDL_HINT_JOYSTICK_HIDAPI_STEAM=0 SDL_JOYSTICK_HIDAPI=0 SDL_JOYSTICK_HIDAPI_PS5=0 SDL_JOYSTICK_HIDAPI_STEAM=0 SDL_HINT_JOYSTICK_HIDAPI_PS5=0 WINEDEBUG=+xinput,+plugplay,+dinput,+hid,+rawinput PROTON_LOG=1 %command%
steam-input.rules)WINEDEBUG=+xinput,+plugplay,+dinput,+hid,+rawinput PROTON_LOG=1 %command%
Game freezes when changing chapters, after Chapter 1 title appears, goes into black screen and doesn´t pass from that.
OS: Arch Linux
KERNEL: 6.12.7-zen1-1-zen
CPU: AMD Ryzen 7 5800X3D 8-Core
GPU: AMD Radeon RX 6800 XT (radeonsi, navi21, LLVM 18.1.8, DRM 3.59, 6.12.7-zen1-1-zen)
GPU DRIVER: 4.6 Mesa 24.3.2-arch1.1
RAM: 32 GB
I remember playing from start to finish, guess something broke in the last proton versions , tried proton 9.0, experimental and proton-ge.
Anyone know a way to continue to play the game?
stutter
Same here. Did you fix this?
Nope, I was able to progress by using Proton 8, but the cutscene doesn´t work, there was another cutscene after rescuing Miller that plays at double the speed and the voice is very distorced, kinda like robot type.
I think the game used to work with <workaround removed by moderator> / Media Foundation installation but for some reason now it doesn´t work, tried a bunch of combinations. It really seems missing a codec or something to render properly just don´t know how to install it and have it working like the old days.
Hello @PickMeNow, the workaround you mentioned is legally problematic and has been removed.
Replying to https://github.com/ValveSoftware/Proton/issues/124#issuecomment-2564731649
Seconding this issue.
Replying to [#124 (comment)](https://github.com/ValveSoftware/Proton/issues/124#issuecomment-2241778216)
Why are only certain Linux users missing this video codec? Apparently only some are missing it because the game has great rating on ProtonDB.
There are hundreds if not thousands of different Linux distributions, and the game is nearly a decade old at this point, and does not receive regular updates. Switching to an older version of Proton (ie Proton 8.0) as mentioned above may fix the issue.
Using Steam Flatpak 1.0.0.83 (Steam Stable 1751405894) on Aurora (KDE spin of Universal Blue, based on Fedora Silverblue) I can confirm that switching chapters crashes on proton experimental and hotfix. Downgrading to Proton 9.0 in Steam's 'force compatibility tool' fixes the issue for me.
Hello @dryya, can you check how the game behaves with Proton 10.0? Please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.
@kisak-valve to contribute here is the gist with the requested information:
https://gist.github.com/slashmach1/45a0f73947905c872a07a612db5f7764
While this may be a separate issue without its own report I noticed launching the game is significantly delayed taking 5 minutes or more to launch without error or indication that the game is open. This delay however is mitigated partially by disabling split_lock_detection via the kernel cmdline or split_lock_mitigation via sysctl. This reduces the delay to about 1 minute.
Thanks @slashmach1 , I don't know of an easy way to trigger one of the problematic cutscenes without deleting my save and re-playing through the (long) prologue. How did you test?
@dryya im using fedora with btrfs snapshots pre and post game. disabling cloud saves when testing only
While this may be a separate issue without its own report I noticed launching the game is significantly delayed taking 5 minutes or more to launch without error or indication that the game is open. This delay however is mitigated partially by disabling split_lock_detection via the kernel cmdline or split_lock_mitigation via sysctl. This reduces the delay to about 1 minute.
Same here.
I'm not sure it's related to Proton, as this delay occurs with the few versions I tested (8.0-5, 9.0-3, 9.0-4; Proton-GE), some (9.0-X) reported as working fine on protondb.
Thanks for your fix... I'll gladly provide any log or do tests if it helps solving this.
Specs :
Arch Linux 6.16.0-arch2-1
NVIDIA GeForce RTX 3060 580.76.05
Using X11
METAL GEAR SOLID V: THE PHANTOM PAIN (287700) won't render
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9005.
@hakobi0 posted on 2025-08-26T02:09:54:
The game doesn't render, but input does register as it the game is running, audio can be heard when pressing enter for example.
Start the game with Proton Experimental
@hakobi0 commented on 2025-08-26T02:10:38:
Forgot to add, this is what I get every time I try to open the game.
Hello @hakobi0, the NVIDIA 470 series video driver is too old to be used with DXVK bundled with Proton Experimental. Please update your video driver series and retest.
I'm having the same problem as @hakobi0 with a Radeon RX 6700XT with mesa 1:25.2.4-1 and linux-firmware-amdgpu 20250917-1 (both are the latest on Arch Linux). Game used to work fine
Hello @fedebenelli, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.
MGS V stopped launching on Steam Deck after the June 9, 2026 Steam update.
AppID: 287700
Depot: 287701
New manifest: 8183974873990090295
Previous manifest: 2518831260221836800
BuildID observed in Steam logs: 23407568
Error:
"Failed to load SteamAPI"
The game was working before this update. Depot 287701 had no public manifest updates since March 23, 2021, so this looks like a regression from the June 9, 2026 update.
Tested and failing:
Workaround:
Important log lines from failing Proton versions:
BuildID 23407568
Depot 287701: manifest 8183974873990090295
Loaded .../MGS_TPP/mgsvtpp.exe
Loaded .../MGS_TPP/steam_api64.dll
Steam_SetMinidumpSteamID: Caching Steam ID: ... [API loaded no]
Testing comment to read recent comments
the game should be back to working on proton bleeding edge https://github.com/ValveSoftware/Proton/wiki/Proton-Versions#proton-bleeding-edge
proton experimentalx5 2026-06proton 8.0x3 2026-06proton 10.0-4x1 2026-06proton 7.0-6x1 2026-06proton 9.0-4x1 2026-06proton hotfixx1 2026-06proton 10.0x1 2025-07proton 9.0x2 2025-07proton 9.0-2x1 2024-07proton 7.0-4x2 2023-05proton 8.0-2x1 2023-05proton 5.13x1 2022-09proton 6.3x1 2022-09proton 7.0x1 2022-09proton 4.11-12x1 2020-01PROTON_LOG=1x10 2025-10SDL_JOYSTICK_DEVICE=/dev/input/js0x1 2024-09SDL_HIDAPI_DISABLE_LIBUSB=1x1 2024-09SDL_HINT_HIDAPI_LIBUSB=1x1 2024-09SDL_HINT_JOYSTICK_HIDAPI=0x1 2024-09SDL_HINT_JOYSTICK_HIDAPI_PS5=0x1 2024-09SDL_HINT_JOYSTICK_HIDAPI_STEAM=0x1 2024-09SDL_JOYSTICK_HIDAPI=0x1 2024-09SDL_JOYSTICK_HIDAPI_PS5=0x1 2024-09SDL_JOYSTICK_HIDAPI_STEAM=0x1 2024-09WINEDEBUG=+xinput,+plugplay,+dinput,+hid,+rawinputx1 2024-09WINEDLLOVERRIDESx2 2019-12WINEDLLOVERRIDES=dxgi=n`x4 2019-11WINEDLLOVERRIDES="dxgi=n"x2 2019-11WINEDLLOVERRIDES=dxgi=nx1 2019-11SDL_JOYSTICK_DEVICE=/dev/input/js0 %command%x1 2024-09SDL_HIDAPI_DISABLE_LIBUSB=1 SDL_HINT_HIDAPI_LIBUSB=1 SDL_HINT_JOYSTICK_HIDAPI=0 SDL_HINT_JOYSTICK_HIDAPI_STEAM=0 SDL_JOYSTICK_HIDAPI=0 SDL_JOYSTICK_HIDAPI_PS5=0 SDL_JOYSTICK_HIDAPI_STEAM=0 SDL_HINT_JOx1 2024-09WINEDLLOVERRIDES="dxgi=n" %command%x2 2019-11steam_api64.dllx1 2026-06
Arch Linux (4.18.3-arch1-1-ARCH)
NVIDIA GTX 970 (Nvidia 396.54)
Proton 3.7
System Information