#54

I get the exact same mouse issue, done lots of digging and found no current workaround. As far as I can tell it's specific to multimonitor setups (could be otherwise though, I've seen users with single monitors not having these issues).

I think setting wine to emulate a virtual desktop is a viable fix for the mouse issue, but for me (and others, it seems) it causes everything to render as black boxes and I cannot get past the launcher.

Yes, I'm on a three monitor setup, which I forgot to mention.
I'm always amazed by so many developers seemingly having only one monitor. I could not live and code without three monitors anymore. :)

Update on this,

I'm using the latest beta of Proton (which you can enable via settings->steam play on the steam client), and running the game in a virtual desktop now works, and with the 'capture mouse in fullscreen' solves the mouse issue as long as you apply the config changes mentioned by @smirgol

WINEARCH=win64 WINEPREFIX='/path/to/steam/steamapps/compatdata/377160/pfx' winecfg

Edit; It seems that this is only true when I let it load up the virtual desktop on my left-most monitor, doing it on any other results with the same black rendering and inability to get past the launcher :/

I can confirm that.
When enabling the virtual desktop, it will only work if it is started on the first monitor (left), not on the second (middle), not on the third (right).

As a workaround I disabled my first monitor, so my middle monitor is now the first one, and then it works - also enabled "capture mouse in fullscreen".

Maybe someone can look into why virtual desktop only works on the first monitor?

My mouse issue was that it behaved like a gamepad joystick (so moving the mouse left would make the character spin - at high speed - until moving it back to centre) but it was solved with the same changes described above regarding emulated desktop and capturing the mouse. I did not need to change my fallout config.

I still don't get voices (and some other sounds) even with xact.

@smirgol Perhaps we should check other Proton games we have installed with a virtual desktop and see if they behave the same way? I'm pretty sure its a bug effecting all games on a multi-monitor setup.

Fallout 4 fails to start after the launcher for me with Proton 3.7.3 and 3.7.4 beta due to missing nvapi64:

(Debian 9.5 stable, GTX 1080, driver 384.130)

167480.850:0030:0031:trace:module:load_dll looking for L"C:\windows\system32\nvapi64.dll" in L"Z:\home\gaming\.steam\steam\steamapps\common\Fallout 4;C:\Program Files (x86)\Steam;C:\windows\system32;C:\windows\system;C:\windows;.;C:\windows\system32;C:\windows;C:\windows\system32\wbem"
167480.851:0030:0031:trace:module:get_load_order looking for L"C:\windows\system32\nvapi64.dll"
167480.851:0030:0031:trace:module:get_load_order_value got standard key n,b for L"nvapi64"
167480.851:0030:0031:trace:module:load_builtin_dll Trying built-in L"nvapi64.dll"
167480.851:0030:0031:warn:module:load_builtin_dll cannot open .so lib for builtin L"nvapi64.dll": /home/gaming/.steam/steam/steamapps/common/Proton 3.7 Beta/dist/lib/wine/nvapi64.dll.so: cannot open shared object file: No such file or directory
167480.851:0030:0031:warn:module:load_dll Failed to load module L"C:\windows\system32\nvapi64.dll"; status=c0000135
167480.851:0030:0031:trace:seh:NtRaiseException code=c0000005 flags=0 addr=0x141d1783c ip=141d1783c tid=0031
167480.851:0030:0031:trace:seh:NtRaiseException info[0]=0000000000000000
167480.851:0030:0031:trace:seh:NtRaiseException info[1]=0000000000000000
167480.851:0030:0031:trace:seh:NtRaiseException rax=0000000140003110 rbx=0000000000018130 rcx=0000000000000000 rdx=000000000023f8b0
167480.851:0030:0031:trace:seh:NtRaiseException rsi=0000000000000000 rdi=0000000000000b18 rbp=000000000023f930 rsp=000000000023f830
167480.851:0030:0031:trace:seh:NtRaiseException r8=00000000000fc008 r9=000000000000002a r10=0000000000000002 r11=0000000000000000
167480.851:0030:0031:trace:seh:NtRaiseException r12=000000000023fd88 r13=0000000000000001 r14=0000000146219900 r15=00000000000009c0

@bobintetley looks like your drivers are seriously out of date, you want to be using 396.51 or 396.54.

See here

I'd rather stick to the Debian distro bundled drivers if I can. I have Fallout 4 running just fine with wine 3.6-ge on the same machine so I don't think the drivers are an issue in this case. The debug trace I posted above shows that FO4 has a dependency on nvapi64.dll which is not present in proton 3.7 - there's a stub for nvapi in later versions of wine.

Interesting, because it works for the rest of us in Proton 3.7.

You should really reconsider updating your drivers though, your current ones are over 5 months old and there are huge performance boosts in .54 due to some old "resource leak" issue that has existed in the Nvidia drivers for a while.

also the new drivers contain lots of vulkan fixes which proton relies on. You are only hurting yourself.

Ok ok, you convinced me - I'll upgrade my drivers ;D

Just to report back, I updated my drivers to 390.77 (by moving to Debian buster) and bizarrely the nvapi64.dll error went away. I have absolutely no idea why that should be the case, but that seems to have fixed it and FO4 starts for me with Proton now.

As others have found with other games, I had to add library overrides for xaudio to get sound working and run the game in a virtual desktop with the capture mouse/fullscreen option to prevent the mouse escaping the game. After all that, it works great!

I followed the steps here to fix the mouse issue. and the steps from this video to fix the audio issues.

the first comment in this thread mentions xact. I also needed to override xaudio2_6 and xaudio2_7 and set them both to native in order to fix my audio completely.

I only have one monitor, and any combination of grab mouse in full screen and virtual desktop does not work for me. I can still only turn about 90 degrees in each direction before it gets "stuck".
This is very odd as I don't remember having this issue when trying the game with wine-staging alone.

Btw. if anyone have trouble finding the games ini files they are under:
/home/[username]/.steam/steam/steamapps/compatdata/377160/pfx/drive_c/users/steamuser/My Documents/My Games/Fallout 4

If you're using a virtual desktop, make sure the game is in full screen mode rather than windowed. Also, make sure the virtual desktop size matches the full screen resolution of your desktop.

@Lejoni : it's not the [steamuserid] but the game's steam id, which is 377160. ;-)

Sometimes for me it helps to click with the left mouse button and then I can turn around as much as I want. Usually happens after alt-tabbing out of the game. Not sure if it helps you, but it's worth a try.
FWIW: I play in windowed mode, virtual desktop set at my native resolution, grab mouse enabled.

One more thing that is sometimes useful to know:
When your TAB key no longer works ingame, usually after alt-tabbing out of the game and back, switch out of the game to a different app, bring up the app selector (Alt-Tab) and click the Fallout4 app icon with the mouse.

@smirgol Ah thanks. For some reason I thought steam used one prefix for all games. I'm glad they don't :)
I never tried clicking will try that :)

The issue with TAB no longer working I have encountered many times in Skyrim. Sometimes it simply helps if I press and release alt a few times. It's like the game think alt is constantly pressed.

@smirgol Hmm now when I went to try clicking it worked before I clicked while in game world.
Only thing I can think of is that I clicked continue to load instead of pressing E on main menu.
I have no virtual desktop but have grab mouse on in fullscreen and game in fullscreen.

Sound starts to get really messy after a while tho. and there are some lighting issues in certain areas where I can only see light effects on the top half of the screen. Might be fixable by turning down some settings.

I had issues with sound dropping out and going mute after about 20-30 minutes of play (sometimes a lot less). I just tried setting the launch options to:

PULSE_LATENCY_MSEC=60 %command%

Since then, I haven't had sound drop out on me. It could just be good luck but I've had two separate 2 hour sessions and a few shorter ones since then and sound has remained stable so far.

@bobintetley
PULSE_LATENCY_MSEC=60 %command% made it even worse for me
so I tried PULSE_LATENCY_MSEC=30 %command% and now sound seams nice and stable :)

I managed to get esp mods to work. Just had to create plugins.txt and populate it manually.

Only issue I have left now is the odd lighting bug on bottom half of the screen.
It only happens indoors and only while looking in certain directions.

Here is a picture of the graphical bug I have: https://imgur.com/a/OWR0EaF

This is now the only imperfection I have left. Otherwise the game runs flawless.

anyone having any issues with the game not loading saves or starting a new game? i get to the main menu and try to load a save or start a new game and it just loops forever on the loading screen

@Lejoni
solution for the black horizontal line
https://kver.wordpress.com/2017/03/29/tearing-with-nvidia-proprietary-drivers-on-plasma-try-this/

Unfortunately, despite by all written in this topic , whit Proton I still have a problem with missing conversation audio(all other sound work) , and after around 30 minute begin serious micro-stuttering(fps is around 50-100).
Installation through the Lutris there no problems.
steam-377160.log
system info

To go back to something that hasn't been tweaked, with the latest Proton Beta (3.7-6) my mouse is still completely crazy unless I run FO4 in a window, and there's no conversation sound (and possibly other missing sound)

@nijiwar @HughPH have you overridden xaudio 2.7? You'll need to do that via winecfg

I also had some success fixing sound dropping out by setting PULSE_LATENCY_MSEC=60. I've not found a fix for the mouse issue outside of running the game in a virtual desktop.

@GloriousEggroll yes and same issue with Skyrim SE. I haven't tired Oldrim yet though.

@winterwicht I will try that. But if it works it would be strange as it's not "normal" tearing.
It is only the lighting effects that has that tearing. The textures are fine. And the lightning tearing does not occur in all places of the game. But as I said will try it nonetheless.

@Lejoni should do the trick, i had the same effect and its gone after that. And you should turn off compositors own tearing

for the sound problem, i found another "maybethis" tip:

in falloutprefs.ini set iMaxDesired=0
2 hour session without problems.

next: i am on a triple monitor setup, Proton Beta 3.7.6
No bBackgroundMouse=1 necessary for me, if i do that, the mouse turns only 180°.

@winterwicht Im not using KDE.
For me the 180° mouse problem disappears if I left click once in game.

I have not had any more problems with sound sins I started to use launch option:
PULSE_LATENCY_MSEC=30 %command%

I can't get this game to get past the loading screen for the life of me.

I open the game
I go to new game
infinite loading loop.

I open the game
I go to load save
infinite loading loop.

Also the audio option is greyed out in the settings with an infinite loading circle next to it.

I have not modified anything in regards to the game. I've tried removing and reinstalling it. Tried both Proton 3.7 beta (latest) and Proton 3.7.

Arch Linux, using steam-runtime
vega 64 on llvm 7 and mesa 18.3-git
threadripper 1950x
kde

anyone having any issues with the game not loading saves or starting a new game? i get to the main menu and try to load a save or start a new game and it just loops forever on the loading screen

@GloriousEggroll Have you come across anything to get the game started yet?

Unfortunately, despite by all written in this topic , whit Proton I still have a problem with missing conversation audio(all other sound work) , and after around 30 minute begin serious micro-stuttering(fps is around 50-100).
Installation through the Lutris there no problems.
steam-377160.log
system info

Reinstall Proton , delete and create new prefix , lower all audio sliders half(i think this is the key for my case) and for now no problem with the sounds. Stutter is less.

After just installing xact, adding the bBackgroundMouse=1 setting enabling virtual desktop and full screen capture. The game runs, it starts up correctly but the mouse teleports as I move it. (Well the perspective, I cant see the cursor)

System Information

• GPU: RX 570
• CPU: Ryzen 7 1700
• Driver: OpenGL version string: 4.5 (Compatibility Profile) Mesa 18.3.0-devel - padoka PPA
• Proton Version: Proton 3.7-6 Beta
• Distro: Ubuntu 18.04
• Kernel: 4.15.0-34-generic

Other details

Other then that the game works quite well, and at a playable framerate, additionally the audio works at least in game, It doesn't happen for the main menu but that might be a setting. Also audio works for the occasional Special cutscenes.

Edit

Discard the mouse issue, I was unaware it the ini file was in compat data.
Also only some audio works, (not related to settings) knife sounds and run sounds seem to work, but not npc's.

I had the black screen cash problem too, right after clicking play it'd black screen then crash. It seems to be related to d3d11, probably need newer drivers. I'm on kubuntu 17.10, so can't use the latest mesa. Anyway, if you can't get that working with vulkan you can use "PROTON_USE_WINED3D11=1 %command%" to fix the problem for now. At least it worked for me.

@Technolem weird, considering the fact I'm on the new 410 drivers myself and getting that issue.. will try and see if what you said has any affect for me.

Log, couldn't edit my original post since it was transferred.

https://ghostbin.com/paste/njmhh

Works for me with the same issues as others have noted: Silent Sounds, Mad Mouse, and No Networking.

No Networking means "creation club" and "mods" are not available on the main menu, and the "News/Tips" do not appear on top/right of the main menu screen.
This seems to be because the Proton builds do not contain libgnutls.so, and instead try to link the specific version libgnutls.so.26, which does not exist on my distribution.

If you have this problem, create a symbolic link in /dist/lib64/libgnutls.so.26 to your distribution's libgnutls.so ; Obviously, a change to Proton's link behaviour would likely be better.

This works for me, although the connection seems to drop quite regularly and require me to log in to Bethesda.Net again.

Mad Mouse, as noted in the first post by @smirgol , can be tamed with an ini file setting. I still get the effects where one or both axes of motion get locked to a narrow range unless I run fullscreen at the native resolution of the monitor.

Even then, switching away from Fallout4 and back again locks the mouse. This can be resolved for me by bringing up the Pip-Boy UI, making any selection with the mouse, and dismissing the Pip-Boy UI. Mouse then works properly again.

Silent Sounds is the lack of the XAudio Windows API implementations in Wine/Proton. Again, as noted above you can load the Microsoft libraries using winetricks to get this working after a fashion; but eventually the sounds will lock up/loop, and the game hangs if you try to return to the desktop.

I find that a clean reboot and playing the game with no other sound-using applications running gives the best results, sometimes many hours without sound hangs. Problems most often occur with a high density of sounds being played, such as when storing all junk in a workbench or being near rapid fire turrets.

This seems like threading incompatibilities between what the Microsoft XAudio libraries expect and what Proton can provide by using OpenAL. An alternative would be to integrate FAudio ( free software implementation of XAudio ) into Wine/Proton, but I'm not sure when, or if, that will happen.

Update: I have the same problem in Skyrim SE as I do on Fallout 4 on threadripper: Game hangs infinitely on loading loop.

@GloriousEggroll i had a same issue, on archlinux you need to increase limit for max open files per process. See: https://github.com/ValveSoftware/Proton/blob/proton_3.7/PREREQS.md#fd-limit-requirements

@Salamek I've already done this a long time ago as I've been using esync before proton on wine. Additionally this only applies if you run the game with esync. The problem persists even if you disable esync. Vanilla WINE also has the same issue. I did not have this issue until I tried on a threadripper system.

Just for further proof:

[gloriouseggroll@shittywok ge-wine]$ ulimit -Hn
1048576

Hello @chargedupR, INTEL-MESA: warning: Haswell Vulkan support is incomplete and eventfd: Too many open files in your log looks concerning. For the first part, you can effectively disable intel vulkan support by moving /usr/share/vulkan/icd.d/intel* somewhere out of the way. For the second part, please give https://github.com/ValveSoftware/Proton/blob/proton_3.7/PREREQS.md#fd-limit-requirements a read.

So you're saying just move this (https://i.imgur.com/IqrU7dL.png) the intel ones out and it should essentially fix my first problem, hopefully? Okay. I will try that right now.

Edit: Also for the second advice you seemed to have given me to read, I increased my esync and all of that stuff. Fallout 4 now starts. I get mouse spasms and the audio is broken pretty much.

Added the thing to the config. I now get the 180 issue. running WINEPREFIX=/home/user/.local/share/Steam/steamapps/compatdata/377160/pfx winetricks xact seems to make my audio work, which caused stuttering for me which I fixed with PULSE_LATENCY_MSEC=60 %command% on the launch options.

Setting Mouse capture in full screen window and Emulate a virtual desktop in Winecfg and also bBackgroundMouse=1 on the Fallout4Custom.ini, realy fixes the mouse problem. But the game seems to run very freezed, dropping a good amount of FSP. I've the impression that it's running more smooth without the Emulate a virtual desktop. So, I'll be without it and keep playing with the joystick for now...

System Information

GPU: GeForce GTX 1060 6GB/PCIe/SSE2
CPU: AMD® Fx(tm)-6300 six-core processor × 6
Driver: nvidia-driver-396
Proton Version: Proton 3.7-6 Beta
Distro: Ubuntu 18.04
Kernel: 4.15.0-36-generic

Edit about the performance with Emulate a virtual desktop:
Looks like that disabling the Steam Overlay on Steam client settings and in Winecfg Graphics tab check Automatically capture the mouse in full-screen windows and Emulate a virtual desktop (and set your desired resolution) then uncheck Allow the window manager to decorate the windows and Allow the window manager to control the windows made the trick to almost matches its performance with the non virtual desktop (the default) one. Now I'm playing with mouse. :)

I'm sorry if this is a stupid question, or been answered before, but I couldn't find any info about this anywhere.

Where is the Fallout4Custom.ini file located? I know on Windows it's in /Documents/My Games/Fallout 4

And I managed to find the Fallout4Prefs.ini inside the /steamapps/common/Fallout 4/Fallout 4/

But I can't find the Fallout4 or Fallout4Custom.ini

@breadland Its should be located on the wine prefix, under the steamuser. Like follows:
/<whatever_path_you_put_your_SteamLibrary>/Steam/steamapps/compatdata/377160/pfx/drive_c/users/steamuser/My Documents/My Games/Fallout4

@Victoralm Thank you! Worked perfectly for me and now my mouse doesn't go crazy. I'll post these instructions on scpr.netify.com since no one else there has really gone into detail about where to find the .ini's.

There's still some minor issues, performance isn't as good as Windows, and I notice some vertical tearing, and there's this translucent brownish pixelated overlay that shows up when I look at certain buildings, usually ones that aren't lit.

Oh, and the game hangs on exit and the process never closes. No matter how long I want. SO I have to manually end the process each time I exit by using System Monitor.

But yeah, I can actually play it now!

@breadland Glad it works. I think it will be perfect when the mouse problem has been solved for good and script extender come to work !

@breadland Glad it works. I think it will be perfect when the mouse problem has been solved for good and script extender come to work !

Just need that pesky mouse fix :/

Just adding my experiences. I have a lot of the same things, but the mouse thing is weird for me. I have it working well with the mouse fix. However, I cannot play full screen then i cannot turn to right more than 180. But does not happen in window mode. Mods work, but not creation club. Cannot talk to the servers. Performance full screen quite good on amd 8350 and gtx titan... but kinda bad in window. With wine staging, i dont have the same mouse issue. if i move the mouse too far right, then i start slewing the desktop. Needed to add the xact and pulse tweak for sound to work correctly.

Summary:
What works:

1. manually installed mods (nexus mod manager just dies). Creation club does work with wine-staging
2. almost all game play i have done.
3. sound/music

What doesnt work:

1. creation club
2. mousefix stablizes mouse but unplaybable due to 180 degree bug to right in full screen (oddly no issue going to left)
3. nexus mod manager .. i figure only a matter of time.

Watching this thread very closely.

With Current Proton 3.7-7, I have ran Xact on my Fallout 4 prefix, tried setting both xaudio_6 & 7 to native or native builtin my audio will eventually die. Explosions, Rain, Gun shots, entering a room. It's going to die.

Issue Report

• Name of the game with issue: Fallout 4
• Steam AppID of the game: 377160

System Information

• GPU: Driver: NVIDIA Corporation GeForce GTX 1070/PCIe/SSE2
• Driver Version: 4.6.0 NVIDIA 410.57
• SSD: 960 PRO M.2 1TB NVMe
• Kernel version: 4.18.12-arch1-1-ARCH
• Proton version: 3.7-7 Beta
• Steam - System Information
• PROTON_LOG - steam-377160.log

I Confirm:

• [x] that I have checked whether there are updates for my system available.
• [x] that I have followed the steps in the "PREREQS.md"

Steps To Reproduce

1. Run the game
2. Open console and type "player.additem OOOE6B2E" (Gives the player 1000 mini nukes)
3. Then type "tgm" (Toggle God Mode)
4. Fire as many nukes as you can in as short a time as possible
5. Bug occurs

Symptoms

• The game audio loops indefinitely whatever audio was playing when the bug occurred.
• The game doesn't quit when selecting quit from the main menu or in game start menu when I attempt to quit the "Fallout4.exe" hangs indefinitely.
• The game is still playable everything but the audio and quiting seems to work just fine.
• The Proton_log spams this output exactly when the bug occurs
  16371.927:001f:0025:err:hid_report:process_hid_report Device reports coming in too fast, last report not read yet!.

@Zixxik I can confirm that I have the same problem. Audio works on Proton 3.7-7 if I set xaudio_6 and 7, but it eventually dies. Like for example when a super mutant attacked me, their weapon sound kept on looping and some other sounds stopped, aftera minute or two everything including the looping gun sound stopped playing.

Can only be fixed by restarting. I also have the latest 18.2.2-1 mesa and vulkan drivers on Antergos.

The game seems to hang on exit. I have to find the [Fallout4.exe] <defunct> process and kill it by hand.

The 180 mouse bug seems to only be for full screen. Also, this makes no difference if 1 monitor, or 2. If set Full Screen=0, and bBorderless=1 then it works without this issue.

xaudio 7 works fine then crashes, however, if used with a bluetooth headset, it does not crash, and send audio into "dummy" mode. (Latest Manjaro).

Creation Club, and "Mods" are greyed out, cannot access either of these. Most of the game is working fine with the exception of aforementioned issues.

Since updating to proton 3.16-1 the game never starts up after clicking play in the fallout 4 launcher. Proton 3.7 still works fine. Proton log
Linux arch 4.18.14-1-ck #1 SMP PREEMPT Sun Oct 14 12:54:45 MST 2018 x86_64 GNU/Linux

warn:module:load_dll Failed to load module L"d3d11.dll"; status=c0000135
warn:module:load_dll Failed to load module L"dxgi.dll"; status=c0000135
This looks like the lines of interest in that log.

Got it working after deleting proton 3.16 and the prefix and letting them both download again.

Anyone else getting this? Checked the log and it looks potentially like some sort of access violation that's causing the process to crash and hang.

Log can be found here:
https://gist.github.com/Kayomn/f1040d19b182565d2e560048a8ab9d96

@Kayomn I get that when starting up, but eventually it loads into the menu. Something is stopping it from loading properly. My guess is its the common audio bug and you need xact.

For AMD GPU needed patch for xserver https://gitlab.freedesktop.org/xorg/xserver/merge_requests/48
Without this path the game will stuck at start.

The game started freezing from time to time amd I'm getting this output from the Proton log file:

158434.379:0026:0037:trace:seh:execute_cfa_instructions 7bc91cec: DW_CFA_expression %xmm14 7bcf7580-7bcf7582
158434.379:0026:0037:trace:seh:execute_cfa_instructions 7bc91cec: DW_CFA_advance_loc 5
158434.379:0026:0037:trace:seh:execute_cfa_instructions 7bc91cf1: DW_CFA_expression %xmm15 7bcf7586-7bcf7588
158434.379:0026:0037:trace:seh:dwarf_virtual_unwind next function rip=0000000000000000
158434.379:0026:0037:trace:seh:dwarf_virtual_unwind   rax=00007fffffe80000 rbx=0000000000000000 rcx=00000000272ee870 rdx=000000007bcbb020
158434.379:0026:0037:trace:seh:dwarf_virtual_unwind   rsi=0000000000000000 rdi=0000000000000000 rbp=0000000000000000 rsp=00000000272effe0
158434.379:0026:0037:trace:seh:dwarf_virtual_unwind    r8=00000000272efb50  r9=000000007bcbb030 r10=0000000000000000 r11=00007f520b7bd080
158434.379:0026:0037:trace:seh:dwarf_virtual_unwind   r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000
158434.379:0026:0037:trace:seh:RtlRestoreContext returning to 7bcbb020 stack 272efde0

After kill the Fallout4.exe process:

158890.532:001e:001f:trace:module:MODULE_InitDLL (0x7f08941e0000 L"imm32.dll",PROCESS_DETACH,0x1) - CALL
158890.532:001e:001f:trace:module:MODULE_InitDLL (0x7f08941e0000,PROCESS_DETACH,0x1) - RETURN 1
158890.532:001e:001f:trace:module:MODULE_InitDLL (0x7f08951e0000 L"user32.dll",PROCESS_DETACH,0x1) - CALL
158890.532:001e:001f:trace:module:MODULE_InitDLL (0x7f08951e0000,PROCESS_DETACH,0x1) - RETURN 1
158890.532:001e:001f:trace:module:MODULE_InitDLL (0x7f0895020000 L"version.dll",PROCESS_DETACH,0x1) - CALL
158890.532:001e:001f:trace:module:MODULE_InitDLL (0x7f0895020000,PROCESS_DETACH,0x1) - RETURN 1
158890.532:001e:001f:trace:module:MODULE_InitDLL (0x7f0895050000 L"gdi32.dll",PROCESS_DETACH,0x1) - CALL
158890.532:001e:001f:trace:module:MODULE_InitDLL (0x7f0895050000,PROCESS_DETACH,0x1) - RETURN 1
158890.532:001e:001f:trace:module:MODULE_InitDLL (0x7f08956e0000 L"rpcrt4.dll",PROCESS_DETACH,0x1) - CALL
158890.532:001e:001f:trace:module:MODULE_InitDLL (0x7f08956e0000,PROCESS_DETACH,0x1) - RETURN 1
158890.532:001e:001f:trace:module:MODULE_InitDLL (0x7f0895780000 L"ntoskrnl.exe",PROCESS_DETACH,0x1) - CALL
158890.532:001e:001f:trace:module:MODULE_InitDLL (0x7f0895780000,PROCESS_DETACH,0x1) - RETURN 1
158890.532:001e:001f:trace:module:MODULE_InitDLL (0x7f08957e0000 L"advapi32.dll",PROCESS_DETACH,0x1) - CALL
158890.532:001e:001f:trace:module:MODULE_InitDLL (0x7f08957e0000,PROCESS_DETACH,0x1) - RETURN 1
158890.532:001e:001f:trace:module:MODULE_InitDLL (0x7b420000 L"KERNEL32.dll",PROCESS_DETACH,0x1) - CALL
158890.532:001e:001f:trace:module:MODULE_InitDLL (0x7b420000,PROCESS_DETACH,0x1) - RETURN 1
158890.532:001e:001f:trace:module:MODULE_InitDLL (0x7bc20000 L"ntdll.dll",PROCESS_DETACH,0x1) - CALL
158890.532:001e:001f:trace:module:MODULE_InitDLL (0x7bc20000,PROCESS_DETACH,0x1) - RETURN 1
158890.535:000e:0020:trace:module:LdrShutdownThread ()
158890.535:000e:0020:trace:module:MODULE_InitDLL (0x7fa666b70000 L"rpcrt4.dll",THREAD_DETACH,(nil)) - CALL
158890.535:000e:0020:trace:module:MODULE_InitDLL (0x7fa666b70000,THREAD_DETACH,(nil)) - RETURN 1
158890.535:000e:0065:trace:module:LdrShutdownThread ()
158890.535:000e:0065:trace:module:MODULE_InitDLL (0x7fa666b70000 L"rpcrt4.dll",THREAD_DETACH,(nil)) - CALL
158890.535:000e:0065:trace:module:MODULE_InitDLL (0x7fa666b70000,THREAD_DETACH,(nil)) - RETURN 1
158890.536:000e:0010:trace:module:LdrShutdownThread ()
158890.536:000e:0010:trace:module:MODULE_InitDLL (0x7fa666b70000 L"rpcrt4.dll",THREAD_DETACH,(nil)) - CALL
158890.536:000e:0010:trace:module:MODULE_InitDLL (0x7fa666b70000,THREAD_DETACH,(nil)) - RETURN 1
158890.709:000e:000f:trace:module:LdrShutdownProcess ()
158890.709:000e:000f:trace:module:MODULE_InitDLL (0x7fa666ab0000 L"userenv.dll",PROCESS_DETACH,0x1) - CALL
158890.709:000e:000f:trace:module:MODULE_InitDLL (0x7fa666ab0000,PROCESS_DETACH,0x1) - RETURN 1
158890.709:000e:000f:trace:module:MODULE_InitDLL (0x7fa666b70000 L"rpcrt4.dll",PROCESS_DETACH,0x1) - CALL
158890.709:000e:000f:trace:module:MODULE_InitDLL (0x7fa666b70000,PROCESS_DETACH,0x1) - RETURN 1
158890.709:000e:000f:trace:module:MODULE_InitDLL (0x7fa666ad0000 L"advapi32.dll",PROCESS_DETACH,0x1) - CALL
158890.709:000e:000f:trace:module:MODULE_InitDLL (0x7fa666ad0000,PROCESS_DETACH,0x1) - RETURN 1
158890.709:000e:000f:trace:module:MODULE_InitDLL (0x7b420000 L"KERNEL32.dll",PROCESS_DETACH,0x1) - CALL
158890.709:000e:000f:trace:module:MODULE_InitDLL (0x7b420000,PROCESS_DETACH,0x1) - RETURN 1
158890.709:000e:000f:trace:module:MODULE_InitDLL (0x7bc20000 L"ntdll.dll",PROCESS_DETACH,0x1) - CALL
158890.709:000e:000f:trace:module:MODULE_InitDLL (0x7bc20000,PROCESS_DETACH,0x1) - RETURN 1
pid 21128 != 21127, skipping destruction (fork without exec?)

Tested reverting commit 1312c6642851d4a0c5de9a71c824800935f96691 in vanilla wine 3.16 as mentioned on this bug report: https://bugs.winehq.org/show_bug.cgi?id=45984 and it fixes the infinite loading on my threadripper system in both fallout 4 and skyrim se

Audio seems to be fine with the latest FAudio library, so hopefully this will be merged in future proton releases.

However, still mostly unplayable due to the mouse issue mentioned multiple times.
Jumps all over the place without adding bBackgroundMouse=1 to Fallout4Custom.ini.
But adding this setting, creates new problems with mouse capture, causing the mouse to leave the screen. Tried enabling both capture in full screen window and virtual desktop, and just either one enabled. Neither seem to fix the mouse leaving the screen or limiting movement.

When the mouse issue is properly fixed, this will be perfectly playable on my end.
Preferably a solution which doesn't involve the need for bBackgroundMouse.

@btn21 Care to share a workaround for FAudio?

For me, the 3.16 beta does not fix any of the existing out-of-the-box problems ( sound/mouse/networking ), but also introduces a regression, presumably in DXVK.

The new issue may ( or may not ) be the same as some other people have, which they describe as a "black line".

The issue occurs most of the time, but is occasionally not present. It is not, strictly speaking, a black line; rather, the screen is split into exact upper and lower halves, with each half being rendered differently.

The upper half appears to be rendered correctly, whereas the lower half does not render all the decals, and does not render some of the lighting, leaving it noticeably darker than the top half. If you move the camera so that a previously incorrectly rendered area is in the top half of the window, you can clearly see the difference.

Another aspect of the issue is that it also depends on the camera position; the issue is present when the camera is pointing towards the horizon, but if you move the camera view direction far enough towards either pole, the issue disappears. The issue may also be world-location dependent, as sometimes moving forward ( while looking at the horizon ) will cause the issue to disappear, but if you then turn round, looking back to where you came from, the issue is again present.

Edit: Would probably help to say this is with a 1070ti on an X79 motherboard, using the 396.54 drivers.

Edit 2: Full Steam Info, as requested. https://gist.github.com/etonbears/3af66022819240ef22ba46eeea853352

===============================================================================
Diamond city market showing the split-screen rendering, Note that it applies to the scene, but not to the foreground actor, so it is not related to screen tearing, before anyone suggests that!

===============================================================================
Note the blue-painted floor below the center of the first image; moving the camera to position it above the center, in this second image clearly shows the difference in lighting.

===============================================================================
Moving the camera direction down towards the floor, and the split-screen disappears,

===============================================================================
Moving the camera direction up towards the sky, and the split-screen disappears,

===============================================================================
Moving forward with the camera level with the horizon, sometimes the split-screen disappears...

===============================================================================
... but look behind you and it is still present.

I have the same issues, here is my System information: https://gist.github.com/djhi/e1d78f1fea5ce511ace8dd1240a72f88

Alkaris, other temporary fixes are 1) lowering your mouses polling rate (if you have gaming mouse) or 2) making the window run in virtual desktop sometimes fixes it.

I managed to get esp mods to work. Just had to create plugins.txt and populate it manually.

@Lejoni that's strange I'm still having issues installing them. What path are you using exactly for the Plugins.txt file ? Is it the /.steam/steam/steamapps/compatdata/377160/pfx prefix directory of Fallout 4 ? How did you populated them exactly ?

I had the "black line" half screen tearing issue described by @etonbears occurring pretty much all the time indoors. Changing 'bComputeShaderDeferredTiledLighting=1' to '0' in Fallout4Prefs.ini completely solved this issue for me at least.

File should be located in /path/to/steam/steamapps/compatdata/377160/pfx/drive_c/users/steamuser/My Documents/My Games/Fallout4/

All in all I've gotten the game to play just fine now, with only the minor audio hiccup occurring every now and then.

Things I've had to do to get the game working fine on my machine (fixes taken from this thread and various other sources online):

Installed xact:
WINEPREFIX=/path/to/steam/steamapps/compatdata/377160/pfx winetricks xact

Changed some winecfg settings:
WINEPREFIX='/path/to/steam/steamapps/compatdata/377160/pfx' winecfg

Under the "Graphics" tab:

• Enabled "Automatically capture the mouse in full screen windows"
• Enabled "Emulate virtual desktop" with resolution set to native monitor resolution.

Under the "Libraries" tab:

• added overrides for 'xaudio2_6' and xaudio2_7' (setting these to 'native'. I had no/intermittent audio without this change)

Steam launch options:
Added "PULSE_LATENCY_MSEC=70 %command%" to launch options (I have horrible audio with lots of crackling without this parameter).

Added the following to Fallout4custom.ini
[Controls]
bBackgroundMouse=1

And the aforementioned change in Fallout4prefs.ini
Changed 'bComputeShaderDeferredTiledLighting=1' to '0'

One issue I still have is that the game "hangs" upon 'exit to desktop' from in-game. However, exiting to main menu first and THEN exiting the game is a fairly reliable workaround.

Full Steam info:
https://gist.github.com/Zoetrap/3f0fc6d113c5fef9cdf7d623ea5e81c8

@Zoetrap got it some hours ago, appreciate the answer though. Cheers.

@etonbears @Zoetrap could one of you please upload a savegame at the location where the visual issue can be observed?

@doitsujin No savegame, but after some research it seems that the issue I had at least isn't strictly linux/proton related, and has affected Windows users too.

Found a YT video showing the issue:
https://www.youtube.com/watch?v=HoQloNAziQ0

From a fresh install I had to run the game once, then edit

/steamapps/compatdata/377160/pfx/drive_c/users/steamuser/My Documents/My Games/Fallout4/Fallout4.ini

and add bBackgroundMouse=1 under the [Controls] section in order for the mouse fix to work.

For anyone willing to try, This is a custom version of Proton I've been working on:
https://github.com/GloriousEggroll/Proton/releases/tag/Proton-3.16-GE

Fallout 4, Skyrim SE, and the Script Extenders for both should work, as well as audio, without any fiddling (apart from the fallout 4 mouse config).

Place it in ~/.steam/compatabilitytools.d/, restart steam then select Proton-3.16-GE in the steam play drop down options.

Everything is on github:
https://github.com/GloriousEggroll/Proton

It includes:
Fallout 4 and Skyrim SE patches
Ethan Lee's FAudio - no xaudio2_7 override necessary (override should be removed if you already have it set).

Various other patches:
Elite Dangerous Patch set
Path of Exile patch
SpinTires patch
Magic the Gathering Arena patch

It was compiled in a Debian Stable VM inside docker as per the Proton README.

@GloriousEggroll I'm testing Proton-3.16-GE but for me there is no audio at all, same as the normal proton without the xaudio2_7 override.

I deleted the $HOME/.steam/steam/steamapps/compatdata/377160/pfx old folder before trying Proton-3.16-GE. Also, it seems less stable than the stock Proton (half of the time I started it it just got stuck on a black screen.

To avoid pollute this thread please consider enabling the issue tracker on your github page, so we can continue the discussion there.

@etonbears @Zoetrap could one of you please upload a savegame at the location where the visual issue can be observed?

If you like, but it is any/every game, with or without mods, even before being frozen in the vault.

The following image is directly before producing the attached save, which should be about as simple as it is possible to be.

Save1_4D074315_47726F676E616B_PrewarVault111_000013_20181125225623_1_2.zip

As mods could cause errors and some of then make change on savegames that can't be reversed only by uninstall the problematic mod. I put some work to make a simple script to easy use the Fallrim on Linux. Hope it helps someone.

A reliable repro case for the sound stuttering on my system -- attach with gdb to Fallout 4 (gdb -p `pidof Fallout4.exe`), and after a moment, detach. Stuttering will be present from then on (even if the game is only displaying the title screen). When I do this suspend-and-resume with PULSE_LATENCY_MSEC=60, on my system, the issue is less-severe, but can still be seen a bit.

Alkaris: Using ALSA (pure ALSA, not ALSA back to pulseaudio -- pasuspender used to suspend PulseAudio and confirming that paplay invocations block and that PulseAudio has no Fallout 4 audio stream), I see a bit of stuttering immediately after suspending and resuming Fallout 4 with gdb, and have seen it show up briefly/sporadically, but I have yet to see the persistent-stuttering-once-stuttering-starts in very limited testing. I was able to produce the "all sounds stop playing" issue with ALSA; unfortunately, I lack a reliable repro case for that.

With PULSE_LATENCY_MSEC=120, I also was not able to produce persistent stuttering that I normally suffered after a gdb suspend and resume: there's just a short bit of stuttering after resume and then it stops. I have also not seen the "all sounds stop playing" issue yet under PULSE_LATENCY_MSEC=120, either, but then, I have no reliable repro case, so that may be purely luck-of-the-draw.

With no PULSE_LATENCY_MSEC setting and running with PulseAudio, it's trivial for me to produce persistent stuttering with gdb, so 120 ms of buffer time seems to be at least a partial workaround.

I'll follow up if I can produce either persistent stuttering or all sounds cutting out with PULSE_LATENCY_MSEC=120, but if people can live with that much audio latency, it might be worth trying it as a workaround.

EDIT: Still haven't seen persistent stuttering with PULSE_LATENCY_MSEC=120. Managed to produce the sound cutting out with PULSE_LATENCY_MSEC=120. Loss of sound may be less-frequent, but it can definitely still show up.

With the last 3.16-5Beta of proton, the game freezes when it reaches the menu screen after the initial video. Supposedly, with this proton version that includes FAudio this game should work much better if I'm not mistaken.

Here it is:

steam-377160.log

Will this issue fixed in future versions of proton? I see that @flibitijibibo recomends to use system libraries instead of the Steam runtime's

For Ubuntu 18.04, Compiling FAudio with FFMpeg and Debug options gets past the lockup on the menu screen, but there is no spoken audio, presumably because of the following assertion:

Assertion failure at FAudio_FFMPEG_init (/home/roger/tmp/FAudio/src/FAudio_ffmpeg.c:83), triggered 1 time:
'0 && "WMAv2 codec not supported!"'

Steam_System_information.txt

This behaviour is also observed in SkyrimSE, which uses roughly the same engine. Clearly, Proton will need FAudio compiled with WMA support eventually.

If you're getting no in-game audio dialogue from characters and radios its because you didn't add the DLL override in your winecfg for xaudio2_7 by adding this you should get full audio support as normal.

Of course, but the ultimate goal of SteamPlay/Proton is install and play, with no fixes and workarounds. We post this problems here to help the devs to conquer this objetive

There is no need of using winecfg.
Just use this on the game launch options.
WINEDLLOVERRIDES="xaudio2_7=n,b" %command%

I solved most audio issues of my games with this...
Including the typical cracky audio after several hours of gameplay. (Prey, Murdered: Soul Suspect and Borderlands, for example)

I want to try the new Proton, but I am waiting for the new Nvidia PPA drivers.. ¬¬

I want to try the new Proton, but I am waiting for the new Nvidia PPA drivers.. ¬¬

Nvidia 415.23 driver are in the Ubuntu PPA now:
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa

Ahhhh.... the command you use in Launch option works fine

Fallout 4 keeps freezing for me at random intervals.

PROTON_LOG: https://gist.github.com/Unaccounted4/4ca1cb0b71d476af11a1c11c1780f1a9

System Specs: https://gist.github.com/Unaccounted4/954612d4858a74bc69036c992dbb4de2

EDIT: Update
Copying the FAudio dlls, as suggested in the ProtonDB entry for this game, has stopped these random freezes for me.

Anyone knows how to solve this graphics issue ? It seems that it is related to lighting.

https://i.imgur.com/nSLiXmH.jpg
https://i.imgur.com/8MySoi3.jpg
https://i.imgur.com/dAPpbtC.jpg
https://i.imgur.com/h13Gi5h.jpg

Fresh install of Fallout 4, STEAM set to use Proton 3.16-6 Beta. No sound at all in main menu, video has sound, and character creation only sound I can hear is the shower, no voice or music.

@BloodyIron You need to build FAudio yourself and replace the libFAudio.so* provided by Proton (iirc because WMA support can't be added due to license issues).

Just run

git clone git://github.com/FNA-XNA/FAudio.git && cd FAudio && mkdir build && cd build && cmake .. -DXNASONG=OFF -DFFMPEG=ON && make

and than copy libFAudio.so, libFAudio.so.0 and libFAudio.so.0.19.05 inside the folder /dist/lib64/ of your proton installation (eg. <Your Steam Dir>/steamapps/common/Proton\ 4.2\ Beta/dist/lib64).

You're missing the point of why I'm posting those results. I'm trying to point out that there's gaps in automating the setup for this game for Steam Play, which is the whole point of Steam Play. If I wanted to clone git repos and other such things, I'd just use luitris, PlayOnLinux, or WINE raw. But no, we're talking about Steam Play, a function that's meant to streamline all of that annoying stuff.

If the issue is really a WMA license, I don't think we will see any automation in the short time. I hope to be wrong.

No sound with PROTON 3.16-7

@leinardi Thanks. My Proton 3.16 directory doesn't have a libFAudio.so included, is that normal?

@Alkaris Oh, it seems Steam decided to install Proton 3.16 two times (in both of my Steam library folders). I found it now, just checked the wrong folder. Thanks

With the last version of Proton (4.2), when I move the mouse to turn, the screen goes crazy

@leillo1975 This issue was there since the beginning. Just add the text below to your Fallout4Custom.ini.

[Controls]
bBackgroundMouse=1

@leillo1975 This issue was there since the beginning. Just add the text below to your Fallout4Custom.ini.

[Controls]
bBackgroundMouse=1

Thanks a lot for this info. This is the first time I experienced this problem. Before, I can use the mouse to see normally. Are there more people with this problem in 4.2 and that with previous versions the mouse worked correctly?

Have you checked the PROTONDB report? Everyone is having that problem.

Have you checked the PROTONDB report? Everyone is having that problem.

I played normally with another proton versions (except the audio issues)

I too am experiencing issues with the mouse, however, I have no problems playing with a wired xbox 360 controller. Also, I could not get the audio to work just by installing xact as mentioned above.

Audio still occasionally dies after a while (using the xaudio override). Typically in the middle of a battle with a lot of explosion and gunfire sounds. Kinda feels like the sound engine thingy hits some sort of "cap" and just crash. The game will continue running just fine afterwards, but with no sound (at least for the next 10 mins or so before I couldn't stand the silence and relaunched the game).

Just use the FAudio fix instead of the xaudio one, it solved all my audio issues and I had the same that you have. See here: https://github.com/ValveSoftware/Proton/issues/308#issuecomment-456849130

@leinardi I actually found & tried your exact solution before reporting the issue, but alas I also had the issue with my own compiled libFAudio.so as well (which was v0.19.05 as opposed to Proton 4.2-5's v0.19.04).
Like, both would play sound just fine, it's just that it'll typically eventually fail in mid battle.

Have you wiped FO4 proton container before trying the FAudio fix? I had to do it because the xaudio changes were interfering. My advice is backup your save, wipe the container and be sure to replace the libraries on the right proton version (the one you are using for FO4).

I forgot, try to copy all 3 the libFAudio files from the build directory

Have you wiped FO4 proton container before trying the FAudio fix? I had to do it because the xaudio changes were interfering. My advice is backup your save, wipe the container and be sure to replace the libraries on the right proton version (the one you are using for FO4).

That I did not do. I'll try it again later tonight after testing out some heavy mods later.

I forgot, try to copy all 3 the libFAudio files from the build directory

I did this, however.

Also am I supposed to leave the dll overrides on?

I don't think so, for me I just had to create a vanilla proton container starting the game once (it had no sound) then I just copied the FAudio files over the proton install, started the game again and it just worked perfectly.

Huh, I kinda left the dll overrides on, even after using my own build, lmao

Hmm, actually I can't hear any sound now without the overrides.

Are you sure you are replacing the files on the same proton installation that FO4 is using? This is how my folder looks like:

Ah yeah, lmao, thanks. I did replace those files alright, but the ones in lib instead of lib64. I've done it to the ones in lib64 and I can confirm I can hear things now even without the dll overrides. :+1:

Good, and my guess is that you won't have any issue with sound dropping during battles or rain or, like it was for me, when you store all the junk on the workbench using the shortcut T.

Mods are fortunately working just fine (Unique NPCs, and some others, for the curious), although it ended up making the game take an eternity to start.
Too bad F4SE still needs patching wine/proton, kinda prevents me to use some kick ass mods, cause it's too much of a pain for me to compile myself.

I'll be playing the game now and I'll be sure to send feedback in a couple hours or so.

If the feedback will be positive please consider giving a thumbs up here for visibility (I have the feeling that most of the people keep using the bugged xaudio fix): https://github.com/ValveSoftware/Proton/issues/308#issuecomment-456849130

Sure thing. I've been playing for over 2 hours, fought with some raiders, and so far sound is still working great. I noticed that I also didn't get one of those stutters/statics which I used to get with xaudio override.

I had a very similar issue as @BobbyWibowo , I had setup the xaudio fix through the command line AND through winecfg. Even though I had built FAudio and copied it over to lib I was still having issues. I discovered I had messed something up by running

bpaluch@desktop $ ~/.local/share/Steam/steamapps/common/Proton 4.2/dist/lib64 $ lsof *                                                                                                        
COMMAND     PID    USER  FD   TYPE DEVICE SIZE/OFF     NODE NAME
wineserve 25522 bpaluch mem    REG    8,1  2021415 22948575 libwine.so.1.0
services. 25530 bpaluch mem    REG    8,1  2021415 22948575 libwine.so.1.0
winedevic 25533 bpaluch mem    REG    8,1  2021415 22948575 libwine.so.1.0
plugplay. 25542 bpaluch mem    REG    8,1  2021415 22948575 libwine.so.1.0
winedevic 25548 bpaluch mem    REG    8,1  2021415 22948575 libwine.so.1.0
explorer. 25556 bpaluch mem    REG    8,1  2021415 22948575 libwine.so.1.0
Fallout4. 25612 bpaluch mem    REG    8,1  2021415 22948575 libwine.so.1.0

As you can see no libFAudio file opened by Fallout4 . After removing from command line AND going into winecfg and removing the library overrides for xaudio I saw

 bpaluch@desktop $ ~/.local/share/Steam/steamapps/common/Proton 4.2/dist/lib64 $ lsof *                                                                                                        
COMMAND     PID    USER  FD   TYPE DEVICE SIZE/OFF     NODE NAME
wineserve 25522 bpaluch mem    REG    8,1  2021415 22948575 libwine.so.1.0
services. 25530 bpaluch mem    REG    8,1  2021415 22948575 libwine.so.1.0
winedevic 25533 bpaluch mem    REG    8,1  2021415 22948575 libwine.so.1.0
plugplay. 25542 bpaluch mem    REG    8,1  2021415 22948575 libwine.so.1.0
winedevic 25548 bpaluch mem    REG    8,1  2021415 22948575 libwine.so.1.0
explorer. 25556 bpaluch mem    REG    8,1  2021415 22948575 libwine.so.1.0
Fallout4. 25612 bpaluch mem    REG    8,1   221056 22948576 libFAudio.so.0
Fallout4. 25612 bpaluch mem    REG    8,1  2021415 22948575 libwine.so.1.0

Mouse issues are still present on a multi-monitor setup, the mouse hits the edge of the game window and stops moving (thus stopping the camera/locking your view to a small radius).

Works fine with a gamepad, though.

Have you wiped FO4 proton container
My advice is backup your save

@leinardi: What's the files and folders I need to purge/copy here?

I had to delete <Steam-folder>/steamapps/compatdata/377160/pfx/. I just copied back the saves after starting it once.

That just broke the whole game for me. Cannot get past the launcher anymore. :(

Strange, afaik, with a full stock proton, the game should start with no audio. At least this is what happened to me.

Some suggestion:

• Update your graphic drivers
• Delete and redownload your Proton directory on Steam
• Make sure to use the lastest Proton version on FO4
• Validate the cache of FO4 and remove any mod until you get to work again

If you get the game to start with a full stock proton and FO4 is just missing the audio, copy the FAudio files from my previous post.

I'm trying to play the Steam version of the game using Proton 4.11-2 and launch options "WINEDLLOVERRIDES="xaudio2_7=n,b" PULSE_LATENCY_MSEC=90 PROTON_NO_ESYNC=1 %command%"

Unfortunately, I am unable to get my PS4 controller to work with the game. Keyboard and mouse work fine.

Here's a good one: View angle dependant decals. As in puddles/bullet holes/blood splatter.

I'm on Manjaro (i7-6700 / GTX1050Ti (430.40) / Proton 4.11-2), running the stock (no mods) game on stock Ultra/Borderless and needed the ini-tweaks mentioned before including the "bComputeShaderDeferredTiledLighting=0" to fix "view angle dependand lights". :smile: Also used protontricks to enable the virtual desktop and additionally installed faudio through it, which get's rid of fiddling with files. Still requires the latency fix though. Also threw a "iShadowMapResolution=512" the fallout4prefs.ini for a ridiculous performance boost even all settings were set to Ultra (without motion blur) in the launcher.

So here's some screenshot of what I mean:
Raider with splats
Splats gone away by looking slightly up

I've been looking for more people reporting this for quite a few days and all I've found is people complaining about how ugly the fake puddles are and "here's a mod to remove them!". Thing is: That's not the problem here.
It expands to everything being dirty desks, dirty vault floors, splats on walls, bullet holes, etc.
After pseudo playing (more like testing stuff) the game for some 90 hours and hacking away on the ini file, I've wiped the prefix, checked file integrity, added the mouse fix and touched nothing else to no avail. :+1:

Any ideas are welcome... :)

Edit: "bComputeShaderDeferredTiledLighting=0" has no impact on decals.

I've added the mouse fix (to not make it go wild) to the config and added the audio fix to my startup options, but what ultimately makes this unplayable is that the mouse gets "stuck" on edges when using multiple monitors. Seems the only solution is to play with a gamepad or disconnect all other monitors (which is completely unacceptable).

@Kattus I get the same issue and I've just found that tabbing out and in a few times seems to fix it for me, tabbing out in my case means just toggling through my virtual desktops as I run bspwm, so give that a shot I suppose and see if it works for you.

Also try the old alt+enter twice, that solves the issue in other games for me. (Such as battlefield bad company 2)

@exezin Sadly alt+tabbing didn't work, neither did togging virtual desktops (I'm on KDE), and alt+enter isn't a thing in Fallout 4. :/

Oh and virtual desktop just gives me a black screen.

@Kattus double check under game properties that its using the latest Proton release, you should be able to force the version. Also emulating a virtual desktop in Proton seems to not work at all for any multi-monitor setup unless you have the virtual desktop on the left-most monitor.

@exezin yeah it's the latest version, 4.11-2, it didnt work when I last tried as well on 4.2.

For clarification, this doesnt happen on any other game. Skyrim:SE included.

The problem of missing lights and splats is still present on proton 4.11-3.

Looks like the missing lights and splats were solved with proton 4.11-6.

Game was working perfectly on Proton 4.11-7 with a few tweaks: Virtual Desktop, bBackgroundMouse in FalloutCustom.ini, etc. However with most recent release, Proton 4.11-8, the game crashes before the main menu.

The issue from https://github.com/ValveSoftware/Proton/issues/308#issuecomment-535939265 has fixed itself. The only relevant updates were to llvm 9.0 and mesa 19.2.4 but downgrading these packages in lockstep back to llvm 8.0.1 and mesa 19.2.0 doesn't reproduce the issue so i assume that dxvk was updated in the proton bundle.

I seem to be having issues loading saves while using proton 4.11.10, I can sometimes get one to load but it takes many tries at starting the game and getting it to load. When setting PROTON_LOG=1 it shows an 'overflow' error. I'll try to reproduce this and upload a log to hopefully help.

steam-377160.log

I seem to be having issues loading saves while using proton 4.11.10, I can sometimes get one to load but it takes many tries at starting the game and getting it to load. When setting PROTON_LOG=1 it shows an 'overflow' error. I'll try to reproduce this and upload a log to hopefully help.

between last night and this morning, it seems to be working fine... after turning on proton logging.

I was able to reproduce it now.

Proton 4.11-10 - game working without tweaks on a multi-monitor setup now. But sound effects stopped working after a few minutes in one session (background noises running but not dialogue or guns). Game also cannot quit to desktop, hangs and requires force-closing.

@howels, I'm experiencing the same. I'm no expert but I have afeeling the timing of this log line is related.

130382.603:0036:0050:err:seh:setup_exception stack overflow 1664 bytes in thread 0050 eip 00007f8dd55d269a esp 0000000039b00f90 stack 0x39b00000-0x39b01000-0x39c00000

I'm still getting no sound at main menu in Fallout 4 using Proton 4.11-11, was really hoping this would get piped into Proton main by now :/

Not able to start new game/load saved games at all. Just swap usage shoots up while the game hangs, though the sound still plays.

Another issue I found with FO4 and possible affecting other games (SkyrimSE is fine).
If you run the proton script outside of the link of the game in steam, the game Fallout4 CANNOT see steam. It physically thinks steam is not running so if you are doing modding (which these games are built for) then you need to run steam again via proton within steam.... yep old loop de loop bug.

This should be fixed, really infuriating bug!

The flicky decals fixed in 4.11-6 are back in 4.11-11. :)

Got this setup and installed finally, with f4 script extender as well as DLL linking (current staging patches break it).

Haven't seen decal flicker issue yet, is it when you shoot at objects the decals are not placed correctly? what doe they look like when shot at walls?

As described in my old post:

It expands to everything being dirty desks, dirty vault floors, splats on walls, bullet holes, etc.

Due to the updates, I'm only enybling v-sync through dxvk.conf as it works better still than the games own iPresentInterval option.

I've just reset the prefix just in case, put the settings on Ultra and disabled godrays. The issue stays the same. Here's a gibby super mutant for variety: :slightly_smiling_face:

System in a gist!

I dunno what I'm looking at, whats with the massive division down the middle of the screen? is the left showing decal working while right shows that it doesn't render at all? (current issue)

Also there is a decal mipmap setting that is recommended to be set to -1 which might have a effect (remember it was option in the fo4 launcher mod from nexus)

It's 2 screenshots merged to one. Left half with visible decals and right half with missing decals caused by looking slighly down.

Found these settings for decals here which seem to be the default:

[Decals]
bAllowDecalsOnAlpha=1
bBackgroundInitializeGeometryDecals=1
bDecalMultithreaded=0
bDecals=1
bForceAllDecals=0
bSkinnedDecals=1
fDebrisDecalTimer=2.0000
uMaxSkinDecalPerActor=25
uMaxSkinDecals=100

Unfortunately they didn't fix the problem. :slightly_smiling_face:

Try using the below mod if it runs within your prefix to set some stuff up based on its recommendations and test again.
www.nexusmods.com/fallout4/mods/102/?

Hmmm, blood decals seem to appear for me, only started a test run game and went to red rocket, that dog across the bridge has blood on ground and several mole-rats I killed produced blood splatters also.

I did use that config tool, only needs dotnet4.0, I think maybe if you install 472 it breaks,.

I'm trying to keep it vanilla to see it on the compatibility list eventually. :slightly_smiling_face:
Modding, though probably fixing alot of stuff, should be secondary imo. :wink:

Actually I forgot to mention I'm using proton-tkg 5.0rc4 custom build without staging enabled.

Could you try the pre-built one (it has staging) on the proton-tkg releases and see if the problem persists with that? because if wine5-0rc4 fixes the problem then maybe we don't need to worry about it so much.

Issue still present in 4.11-12. :wink:
EDIT: ...and 5.0-5 :grin:

Anyone have problems with this game and excessive memory usage? I have a vram of 11GB but it gets eaten up with texture mods on. Kinda crazy really. Wondering if there is a nvidia driver bug happening.

Whenever I use the Creation Club part of the main menu, I consistently get thrown out after a short while with an error message "$CreateAcct_BNET_WINHTTP_INVALID_SERVER_RESPONSE" (there’s a screenshot of how the screen looks like at https://www.reddit.com/r/fo4/comments/8hec4q/createacct_bnet_winhttp_invalid_server_response/).

I can reboot into Windows and browse the Creation Club interface to my heart’s content, but as soon as I load back into Linux and run FO4 via Proton (I just tried again now with 5.0-1, but it’s been an issue with all prior Proton versions I’ve tried too), I can maybe look at a couple of the CC items before being kicked out.

(If I press Esc on the shown screen, I get redirected to the main menu and can choose "Creation Club" again which will log me back in for a short a while.)

Yeah I don't think I've tried to access the creation club in FO4 under Linux. I'll give it a try sometime.

I experience the same behavior with Creation Club, you can use your creation points and obtain the free items but it logs out randomly. And its even worse on Skyrim SE.

Hi

i have a problem of stuttering with Fallout 4 - High Resolution Texture Pack, low fps.
I tried window and full screen ( 1280x720 - 1980x1080 ) with quality details low - Ultra. On windows 10 work well.
Someone can help me?

Bye Lele

Ubuntu mate 19.10 64bit
CPU: Quad Core Intel Core i7-4790K
ram 16gb
Graphics GeForce gtx 970
driver NVIDIA 435.21
Proton 5.0.4

The high resolution Texture pack consumes more VRAM than the GTX970 has available.

@CSahajdacny
thank you!!! without change Graphics card there no solutions i think...

@GhChancellor You can uninstall the texture pack. The difference is barely notable. The game ran fine on my old 1050Ti so it should run at least as good or even a little better for you.

As for myself:
The decal problem persists in 5.0-5b


Here's a log: steam-377160.log :smiley:
Sysinfo: https://gist.github.com/7HEPOW/0125ce709d167eb5ea3a0bbbd27d0f4c

20.05.14 Edit: Tested with 5.0-7 and 5.8-GE-2-MF with the same results persistent on all quality presets from the launcher. :smile:
20.06.08 Edit: Present in 5.0-8 aswell. :smile:

@7HEPOW without "high resolution" pack work very with my 970

I think I may have 2 different issues which I have not seen mentioned elsewhere.

This is on Arch Linux with FX8350/RX590.
Mesa 20.0.4 LLVM 9.0.1, also tried with ACO.
Screenshots are on ultra settings, but it's the same on low.

steam-377160.log

Hi @kisak-valve, yes this seems to have completely fixed it, thank you very much!

Gotta say that the performance is terrible though, even on low settings.

Isn't there a way to see what's blocking DXVK from working right?

I'm experiencing problems with decals too. I found that if I use PROTON_USE_WINED3D=1, it will display decals properly. The game is largely unplayable using DX, but it shows the issue isn't specific to the game's configurations.

FO4 uses PhysX/Nvidia FLEX for decals and debris "shot off" of surfaces and, since it works with DX but not Vulkan, presumably PhysX is having problems with Vulkan?

You can turn PhysX/Nvidia FLEX off in the Fallout4 ini files and test.

You can turn PhysX/Nvidia FLEX off in the Fallout4 ini files and test.

Yeah, you sure can. Why would you though? It already doesn't work with DXVK. That's what I'm trying to change.

I can confirm that using the latest tkg build fixes decal flickering for me.
https://github.com/Frogging-Family/wine-tkg-git/releases/tag/5.8.r0.g7d92cd31
Runs native with radv/aco.

How can I fix these blocky edges?
Disabling bComputeShaderDeferredTiledLighting= seems to fix it but I kinda want to play the game with decent lighting otherwise I rather play another game until it gets fixed. Thanks in advance.

These are most likely the god rays doing their work. :smile: 2 ways to fix it:

1. Disable god rays in the advanced options on the launcher (which is obviously a question of taste) or
2. Follow these steps from PCGW to optimize god rays:
   https://www.pcgamingwiki.com/wiki/Fallout_4#God_rays_performance_fix_and_no_pixelation

Disabling bComputeShaderDeferredTiledLighting comes with it's own problems like no lights rendered at some distance. So it's best to switch that back on unless your shadows are broken. :wink:

Edit: Or what @jarrard says, if you're on "team red" :smile:

That looks like a AMD shader issue that is present on windows even with Fallout4. NVIDIA users generally don't have that issue.

@Tripp7 Hi, I had the same issue on my RX 580 GPU. It turned out that I had been using amd-vlk instead of RADV. So I removed amd-vlk and it solved my problem (Games are now using RADV, it can be verified by turning on DXVK hud).

moved the game from HDD to SSD (both ext4), now I see this message:

("Unable to find an INI file" : for SEO)

Removing prefix does not help.
The missing files are:

.../steamapps/compatdata/377160/pfx/drive_c/users/steamuser/My Documents/My Games/Fallout4/
Fallout4Custom.ini
Fallout4.INI
Fallout4Prefs.ini

If anyone ever faces the issue, here is a simple fix:

• rename Fallout4Launcher.exe to Fallout4Launcher.exe.bak
• rename Fallout4.exe to Fallout4Launcher.exe
• run the game once (it will start windowed), change any setting
• exit and rename the files back to what they were
• done, enjoy the game

Hi.

Same decal issue.

5.6.19 kernel, nvidia 440.82, vanilla GOTY edition, no mods, no HD texture pack. All protons tried, and 1.1 and 1.2 vulkan dxvk's.

This is a horrible bug report, sorry I don't understand the running-thread to keep track of them all vs. individual, feel free to delete this. I did turn off [NVFlex] PhysX and even antialiasing and atmospherics, and there's no change. I also bumped all the fallout4 & fallout4prefs decal timing related values to double or triple. (not that I thought it would work, but hey why not?)

I previously do not remember having this decal disappear/reappear thing, but now all I can see is it not working. It's frustrating. You guys think it's dxvk, so starting there, and I initially thought so, after trying with the PROTON_USE_WINED3D=1 -- ludicrously funny because it drops to single-digit framerate @ 4k, but a quick 'winetricks d3dx11_43' helped enough to take screenshots... using the native override makes it slightly playable -- and as I said I thought did work correctly, have examples of a dozen decals persisting as they should. And then it did something different, the reason I'm posting, maybe a clue - the decal only partially de-textured "flickered"? So the specular layer flickers but the diffuse stays?! See below. At first I thought it was just a delayed load-in because how slow it is this way, but wiggling the mouse a couple pixels, turns it on and off just like it does with Vulkan/dxvk, 'cept apparently only one layer?

This testing brings forth other game-breaking graphic artefacts; horrible lighting, really washed out/contrasty textures, half-screen diagonal texture tearing/missing, even totally a black textureless city when exiting an from inside-space cell. Not going to bother reporting those, this is **unplayable** this way, I'll just pretend we have an old-school censored German version of a game when gore and blood wasn't allowed, and go back to Vulkan soon as I submit this.

Hubris Comics studio with glow blood, ghoul blood, human blood decals on many surfaces and bodies.

BADTFL regional office raider spatter diffuse no specular

BADTFL regional office raider spatter specular applied

Interesting enough I can only get this working with proton-GE now, normal proton just closes down. I use proton-GE 5.0 because it still has support for Mod Organizer 2, whereas newer versions of wine/proton broke it for some reason.

If I try to load the game with normal proton 5 it crashes out before getting to main menu. Very odd.

I try to load the game with normal proton 5 it crashes out before getting to main menu.

Same for me. I get the launcher working and then clicking Play it crashes immediately. My settings have been reset after switching to Proton 4 and refuses to launch there as well. World of Warcraft has stopped launching as well. I've got no clue.

Yeah the steam log seems to spit out loads of dribble that I can't make any real sense of. It seems to just crash all by itself.

Got it running great with mod organizer 2 and mods with GE-5.0-1 however, even have a few DLL mods going. (you need to n,b them in winecfg however)

I've been testing lately and noticed the decals are not appearing correctly for me either. When you get close to them they appear sometimes however.

Anyone find a fix? I remember not always having this issue so there must be a specific reason for it. I am using Proton-GE-5.0 but with latest dxvk.
@Anaglyphic
UPDATE: I found this mod which might help the issue? or highlight the source. (nexusmods.com/fallout4/mods/46749)

So i've gone ahead and changed permissions to 777 and chown player1:users -R while still getting the same results. It looks to be only games on my ext4 drive that would use proton. Otherwise, my NTFS SSD works fine. Any ideas i can try?

I found a post in on steam
more specifically symlinks from within the pfx directory
ln -s ../drive_c c:
ln -s / z:

Cannot get Fallout 4 to start on Proton 5.13 Nvidia drivers 390 Linux Mint 20 Low latency 5.4 kernel

I get the splash and options window but no game title screen

UPDATE: got it to work with PROTON_USE_WINED3D11=1 PROTON_NO_ESYNC=1 %command% launch settings but omg it's SLOW even on LOW (not to mention 80GB download, OMG)

I also don't have audio just have to use subtitles

UPDATE: Audio works with WINEDLLOVERRIDES="xaudio2_7=n,b" PULSE_LATENCY_MSEC=90

UPDATE: Uninstalling (no disable option wtf?) high resolution texture pack DLC improves performance a little but still slow as f

I found solution for sound.

WINEPREFIX="/home/dis/.steam/steamapps/compatdata/377160/pfx" winetricks --force xact_x64

• You need to install xact 64bit!!!
• you have to check error ('Permission denied') in console:
  c:/windows/system32/x3daudio1_0.dll: Permission denied
  you have to remove all 'denied' files

cd /home/dis/.steam/steamapps/compatdata/377160/pfx/dosdevices/c:/windows/system32
rm ./x3daudio1_*
rm ./xactengine3*
rm ./xaudio2_*
rm ./xapofx1_*

• repeat the installation and rm until all errors are fixed.

after it Fallout 4 runs with

WINEDLLOVERRIDES="xaudio2_7=n,b"

I can get FO4 to start on latest proton.
Unfortunately the newer proton versions do not like Mod Organizer 2 so much and will often fail to load stuff with the vfs.

Stick with Proton-5.0-GE-1 if you want better mod support. (will likely require dotnet installed)

Do you still experiment issues with RADV?

I have a 6800XT now so can probably test this under RADV sometime. I'm not sure what the issue was with RADV.

@jarrard Would be appreciated, thanks!

I keep forgetting about testing this one. I believe I'm meant to be testing for texture and decal flicker issues.

Unfortunately I've encountered some rather bad performance issues with RDNA 2 (maybe earlier cards I do not know) which I've talked about in the KCD issue tracker. So I've spent allot of time trying to figure that out, the issues use to exist under windows driver also but have since been mostly fixed.

I'll post back here my results with this game on 6800XT.

The game runs brilliantly but the missing NPC audio is still not fixed after all this time.

As mentioned, you can fix this by using without quotes "WINEDLLOVERRIDES="xaudio2_7=n,b" %command%" in the game's custom launch options, but since this is still a hugely popular game, I suspect people will want to play this on the Steam Deck.

Is this likely to be fixed in the next release of Proton?

it's meant to be fixed via faudio, but for some reason normal protons don't have that fully implemented.

@ivyl @aeikum @kisak-valve please let us know if there is a chance to solve it in the next Proton release.
CC @flibitijibibo @rbernon

Same with Skyrim SE please.

Greetings, I have tried to run Fallout 4 on my machine with Fedora 35.
The introduction I have been able to play with a magical fluidity. But when I'm breaking out of the bunker to the surface, I get crashed pretty wildly by a memory access violation error.

Attached log of what happens:
https://pastebin.com/80y7hjA1

Also attached link of the characteristics of my equipment according to steam:
https://pastebin.com/EE53qavr

Hello people. The game runs on my old hardware alright, I was glad to learn a few weeks back.

But does the game eat and leak memory! Very often my 24 gigabytes are all saturated, a small swap space too, and it just freezes. I can't do anything but invoke REISUB and lose my unsaved progress (on Survival no less).

If the memory leaks then it happens within 30-45 minutes of gameplay. When it doesn't happen to leak, I can play as much as I want without a hitch.

I don't think it's Proton's fault. What I thought instead to ask if there's possibly a trick or two to manage this memory situation from linux capabilities/Proton/kernel point of view. Set up ulimits, set up a prodder that could anticipate the problem, something?

Create a gist with the system specs.

System specs from Steam: https://gist.github.com/progo/43701656541d179efc87f0e74eb3a774

Here you go. I notice some of the specs aren't technically correct in the automatic report but I guess it's business as usual.

But does the game eat and leak memory! Very often my 24 gigabytes are all saturated

Mods can cause this issue. If this is default non-modded game then yes it shouldn't happen.

Mods can cause this issue. If this is default non-modded game then yes it shouldn't happen.

This is a vanilla GOTY version that includes all the official DLCs, no mods.

Have you tried with previous versions of the driver, like 470.86 or 460.91.03?

I ran 460.67 before updating to 495.44. This happened Nov 29.

WOW! I can confirm that using ProtonGE 7.0RC2 the game doesn't require any workaround to listen audio.

Game works using ProtonGE 7.0RC3 without workaround for audio needed.

Creation Kit, modding suite for the game does not work flawlessly, it has a single crash source making it near unusable, which I've tracked to be related to context menus, as if a secondary followup menu appears, it wil not crash, however if it is to close the "Select Form" window directly following confirmation, it will.

0218:fixme:imm:ImeSetActiveContext (0x4603d0, 1): stub 0218:fixme:imm:ImmReleaseContext (0000000000010176, 00000000004603D0): stub 0224:fixme:imm:ImeSetActiveContext (0x4403d0, 0): stub 0224:fixme:imm:ImmReleaseContext (000000000002013A, 00000000004403D0): stub Unhandled exception: page fault on read access to 0xffffffffca686d6f in 64-bit code (0x0000000140f8b662).

When it comes to modding tools in games and wine; they have not received much attention so compatibility is certainly patchy. For a very long time mod organizer 2 didn't work correctly with wine/proton until I actively brought attention to the issues on said modding tools github/winedb.

You should try Creation Kit under Lutris (who whatever tool) using Wine to see how it runs and to see if its related to proton specifically.,

@jarrard Yeah, modding tools sadly haven't gotten much attention, however, in this case I was able to actually make it work in the end (barring some annoyances).

This tested on Pop!_OS 21.10.

It's currently running through Lutris with Proton-7.0rc3.GE-1 and DXVK_1.9.3 as well as a modified version of Nukem's Fallout 4 Creation Kit patches (patched out darkmode as it caused a instant crash) and running with that winhttp.dll file as a override, I also had to use regsvr32 to register the 64bit FlowchartX DLL, as the Creation Kit itself failed this on its own - with all that it runs comparable (and in several instances better than on Windows 10) with only two minor annoyances:

• On each boot it generates a 40KB .dmp file.
• It does try to crash, bringing up assertion windows (which if closed down or clicked "OK" on, will crash it), but if left alone, it operates perfectly.

Unfortunately the game crashes back to desktop for me basically after the first loading screen. I can start the program and in the menu start a new game which leads to a mostly black loading screen. After about 30 seconds it crashes. Curiously it seems to take much longer if I switch from 165 Hz (VRR) to 60 Hz but that’s just an aside.

Things I tried: Proton version chosen by Steam (6.3, log file), Proton GE 7.0RC3, with and without ESYNC, with and without the Audio-DLL-Override, installed xact using protontricks (not necessarily in that order and certainly not every possible combination). Rebooted to make sure there are no post-update shenanigans in play.

What I still have to try out is physically unplugging all but the main display device. I turned off my other monitor and set the HDMI output going to the AV receiver to off but you never know. Also there’s an Index attached …

I would assume that this access violation is to blame:

441.160:0144:0190:trace:seh:dispatch_exception code=c0000005 flags=0 addr=000000000073C669 ip=000000000073C669 tid=0190
441.160:0144:0190:trace:seh:dispatch_exception  info[0]=0000000000000001
441.160:0144:0190:trace:seh:dispatch_exception  info[1]=00000000985d0000
441.160:0144:0190:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised

Proton log and Steam system information: https://gist.github.com/kivoli/697cabcb7d8fc5951ad661d2cfbb3ed6

Haven’t seen anyone else mention a similar crash on neither ProtonDB nor here (as far as I could tell). Suggestions?

Unfortunately the game crashes

All sounds like a ulimit and related problem to me. A common issue that people keep hitting to this day. When a game opens too many files it does what you describe. I use lug_helper 1st option to sort that out on any OS install (qol tool)

Have you tried with PROTON_NO_ESYNC=1 %commmand%?

All sounds like a ulimit and related problem to me.

user@host ~ % ulimit
unlimited

So I guess that’s probably not it?

Have you tried with PROTON_NO_ESYNC=1 %commmand%?

Yes but just for the sake of it I tried again today. Same result though.

ulimit -Hn and sometimes vm.max_map_count can affect things.

@jarrard, it seems that there really is some kind of memory leak, I am affected by the same problem and I have tried to set wider limits to ulimit and vm.max_map_count and it seems that it does not solve the problem.

I remind you that a few weeks ago I attached all the stacktrace generated by the runtime itself. https://github.com/ValveSoftware/Proton/issues/308#issuecomment-984164776

This game has a very, very specific issue with steam in-home streaming for me.

It ONLY works when i use WineD3D instead of DXVK - and only when i first start it over vnc on the linux host that runs it.

Full Setup and how to cause it details:
The Host for streaming is a 2700X+RX480 based Tower that runs Fedora 35. It has a fake displayport output and is being remote controlled with VNC and in-home streaming for games.

Client is a Fedora 35 Laptop.

If the game is started with:

Proton 6.8 / 7 / Experimental / GE-75 (prefix cleaned each time) then:
The launcher runs fine
The game freezes on the first frame and only shows 50% of the total content. Even if i start it over vnc and then connect.
Music plays fine so it -is- sending something and its purely a failure to capture game content.

If i:
Enable WineD3D
Start the game over VNC
Wait until the start video plays (if i dont it shows on the other side but only 50% of it - as if it was still using the launcher resolution)

Then and only then does it stream.

It sounds a lot like https://github.com/ValveSoftware/steam-for-linux/issues/5831 to me but atleast i got it to run for now. Of course would be much nicer with DXVK instead.

Odd, maybe a bug in DXVK?

It doesn't start for me with Proton E, it crashes after I click the play button in the launcher. It works fine with Proton 7.

steam-377160.log
Steam - System Information

Edit:
It works with OpenGL, "PROTON_USE_WINED3D=1"

Edit2:
I think it's a shader cache issue, if I delete it (steamapps/shadercache/377160) it starts.

After update yesterday, fallout 4's audio stop working again. For testing I test my main machine Manjaro and test machine linux mint after update all not working, no wonder in bottles or in lutris.Right now I need to roll back to older snapshots from timeshift

Replying to https://github.com/ValveSoftware/Proton/issues/308#issuecomment-1134009167

This issue is persisting on 7.0-5 and experimental.

Given the allocation size limit that seems to be imposed, I'm wondering if this is a 32-bit large address aware issue.

Removing all directories under ~/.steam/steam/steamapps/shadercache/ solved this issue for me. Never encountered it until I recently updated steam and ran a game from the library. I was encountering this issue while trying to run Battlenet under Bottles.

Compatibility Report

• Name of the game with compatibility issues: Fallout 4
• Steam AppID of the game: 377160

System Information

• GPU: Radeon RX 6650XT 8GB
• Video driver version: Mesa 24.2.6
• Kernel version: 6.6.61 LTS
• Link to full system information report as Gist:
• Proton version: Experimental

I confirm:

• [ ] 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.

Symptoms

Running the game (Fallout 4) with Proton Experimental opens the launcher, but the options are not click-able.
Older version of Proton (e.g. Proton 9.0-3) do not have this issue, so I consider it a regression in Proton Experimental.

Reproduction

1. Set Steam Play compatibility tool to Proton Experimental
2. Launch the game
3. All 4 options in the launcher are not click-able

You can workaround this with gamescope, but with it you won't be able to move camera idk why, but mouse buttons will work during gameplay, but not the camera. So at time of writing if you want to use newest proton (or GE-16+) you have to launch the game with gamescope to set up options like texture quality, AA etc. then you download f4se and disable gamescope so you can play this game. Steam Deck mode (SteamDeck=1) is not affected by this since it skips launcher and loads Deck preset.

You can workaround this with gamescope, but with it you won't be able to move camera idk why, but mouse buttons will work during gameplay, but not the camera. So at time of writing if you want to use newest proton (or GE-16+) you have to launch the game with gamescope to set up options like texture quality, AA etc. then you download f4se and disable gamescope so you can play this game. Steam Deck mode (SteamDeck=1) is not affected by this since it skips launcher and loads Deck preset.

Using gamescope doesn't solve unclickable options in launcher for me unfortunately.

BTW, I was using Proton Experimental without problem until recent updates, so it might be a regression that unexpectedly introduced not long ago.

@j20001970 Have you tried experimental-bleeding-edge? There is a known regression with other bethesda launchers that was introduced with the last experimental release and should be fixed by the next one. Currently the fix is only in bleeding-edge. If the clicking is not fixed by the next experimental release/current bleeding-edge, please let me know.

I'm hoping this is the same regression, but regardless, thank you for reporting this! It is very helpful to us even if in this case, it is already known :)

@j20001970 Have you tried experimental-bleeding-edge? There is a known regression with other bethesda launchers that was introduced with the last experimental release and should be fixed by the next one. Currently the fix is only in bleeding-edge. If the clicking is not fixed by the next experimental release/current bleeding-edge, please let me know.

I'm hoping this is the same regression, but regardless, thank you for reporting this! It is very helpful to us even if in this case, it is already known :)

Hi, I switched to bleeding-edge and launcher options works again! Glad to know that it will be fixed in next experimental release.

Trying to run 1.10.163 instantly crashes in steam, and gog version crashes after intro video. Running 1.10.984 works, but that version doesn't work with a lot of mods so I wanna run 1.10.163 which crashes.
steam-377160.log, gog version log, and system info

Is there a solution to get around launcher and straight to the game? The game executable is broken on linux and crashes when its not launched from the game launcher and virtual desktop.

Is there a solution to get around launcher and straight to the game? The game executable is broken on linux and crashes when its not launched from the game launcher and virtual desktop.

Rename Fallout4Launcher.exe to Fallout4Launcher-backup.exe

Create a symlink pointing to Fallout4.exe and name it Fallout4Launcher.exe

Then go to ../steamapps/compatdata/377160/pfx/drive_c/users/steamuser/Documents/My Games/Fallout4/ and add or modify the Fallout4Custom.ini file. Add or modify the [General] section with the following:

sIntroSequence=
fChancesToPlayAlternateIntro=0
uMainMenuDelayBeforeAllowSkip=0

Then simply run the game as normal.

Alternatively and for being safe from Bethesda's future updates change the launch options in the game's properties to this:
bash -c 'exec "${@/Fallout4Launcher.exe/Fallout4.exe}"' -- %command%
This also works for many other games that don't force the launcher on you like Borderlands 2 for example 😉

Alternatively and for being safe from Bethesda's future updates change the launch options in the game's properties to this: bash -c 'exec "${@/Fallout4Launcher.exe/Fallout4.exe}"' -- %command% This also works for many other games that don't force the launcher on you like Borderlands 2 for example 😉

You still have to modify or add the Fallout4Custom.ini file, skipping all intro movies, or it won't put you straight into the game.

@Topeaka Thank you for the report! Edit: we figured out the problem. Unfortunately, the root problem is a game bug. You should be able to work around this to play the game by selecting the text boxes using the built-in controller instead of manually opening the OSK. If you navigate to the text boxes and hit "A" to open, it should open a separate "submit text" box and inputting your name there should avoid the crash.

Could you try putting this in the launch options for your game to see if this fixes the problem: SteamDeck=1 %command%

Also - are you using desktop mode or "gaming mode"?

Hi,
Thanks for your updated comment, the initial suggestion didn't work, and the work around doesn't work either in desktop or in steamdeck mode.
However, i pugged in a keyboard to get past this stage and that work.
Hopefully I won't need to enter any text in the future.

As of August 2026, with proton stable 10.0-4 audio issues still persist.

faudio 20.7 installed through winetricks resolves the issue
xact is not required or working anymore

Relevent Proton logs for default proton without faudio:

59273.953:0198:01ec:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\msdmo.dll" at 00006FFFFA260000: builtin
59273.953:0198:01ec:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\wmadmod.dll" at 00006FFFFA290000: builtin
59273.953:0198:01ec:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\winegstreamer.dll" at 00006FFFFA1D0000: builtin
0:00:00.040298140 121629 0x7f6fec09ac90 ERROR   protonmediaconverter lib.c:300:dump_fozdb_open: Env MEDIACONV_AUDIO_DUMP_FILE not set.
0:00:00.040324009 121629 0x7f6fec09ac90 ERROR   protonmediaconverter audioconv.c:862:audio_conv_change_state: Failed to open dump fozdb, ret -11.
0:00:00.040381909 121629 0x7f6fec09ac90 ERROR                   WINE wg_transform.c:868:wg_transform_create: Failed to create winegstreamer transform.
0:00:00.801786605 121629 0x7f6fec09ac90 ERROR   protonmediaconverter lib.c:300:dump_fozdb_open: Env MEDIACONV_AUDIO_DUMP_FILE not set.
0:00:00.801817824 121629 0x7f6fec09ac90 ERROR   protonmediaconverter audioconv.c:862:audio_conv_change_state: Failed to open dump fozdb, ret -11.
0:00:00.801878408 121629 0x7f6fec09ac90 ERROR                   WINE wg_transform.c:868:wg_transform_create: Failed to create winegstreamer transform.

@NarkyAbyss I haven't seen anyone bring up audio issues recently. Can you specify what steps will lead to the issue appearing? what are the symptoms? does it disappear entirely? does it pop, or timestretch or is it something else entirely?

@simifor Sound effects and video audio are working, but music and other audio like voices are not working. It is mostly the same issue reported in the past in regards to xact.

System config at time of testing:
Operating System: openSUSE Tumbleweed 20260630
KDE Plasma Version: 6.7.1
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1
Kernel Version: 7.0.12-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 7 5700X 8-Core Processor
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: Intel® Arc
Proton 10.0-4
sniper_platform_3.0.20260714.251853

I have not tried any other distro or configuration, so ther is a chance this could be an issue with opensuse

this is also the case for Skyrim special edition (same engine) https://github.com/ValveSoftware/Proton/issues/4#issuecomment-5200057763

@NarkyAbyss The thing is, xact hasn't been required by users for a long time now. Main menu music works as do voices over here, this was recorded with proton experimental, but 11 and 10 behave the same for me. Given that no one else has reported these issues recently I think something in your setup might be a factor.

https://github.com/user-attachments/assets/43bf73f2-1aad-4c49-a25a-f8c14be1a54d

@simifor I suspect as much. xact and winedlloverrides didn't fix the issue when I tried. which was the old solution.

I even deleted and recreated the prefix from scratch. only faudio manually installed to the prefix (~/.steam/root/steamapps/compatdata/377160/pfx)

whatever edge case I have, at least this solution works and others can find it here.