Fallout 4 (377160)

[smirgol]

Requires xact dlls in order to play voices and some other sounds.

WINEPREFIX=/media/Volume/Steam/steamapps/compatdata/377160/pfx winetricks xact

Requires change to config, so mouse won't jump around:

Fallout4Custom.ini

[Controls]
bBackgroundMouse=1

Two issues remain:
The mouse will leave the window when turning the character around. As soon as the mouse leaves the game window, the character does no longer turn around. I've tried to set "Capture mouse in fullscreen" and also to set a virtual desktop with winecfg, but both to no avail. Setting the virtual desktop caused new problems, but this is what used to fix the problem for me when using WINE - without I have the same problem there and only when using DXVK.

Then, no Bethesda game is ever complete without mods.
In order to make the Fallout 4 (and Skyrim) script extender work, a patch is required to allocate memory from top down, so there are free memory addresses before the Fallout4 binary which the script extender needs to inject itself. Wine allocates the memory for the game binary at the very first address, so there is no space before that to inject anything.

See discussion here: doitsujin/dxvk#363
See patch here: https://github.com/hdmap/wine-hackery/tree/master/f4se

In an ideal world, wine/proton would simply leave some memory unallocated before the binary, or solve the issue in a different way, but mapping top down also does the trick and did not cause any issues for me so far.

Besides these things it does start up for me without the audio hack that is required in WINE, which is a big plus for proton. 👍

[cjwijtmans]

#54

[solenum]

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.

[smirgol]

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. :)

[solenum]

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 :/

[smirgol]

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?

[HughPH]

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.

[solenum]

@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.

[bobintetley]

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

[solenum]

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

See here

[bobintetley]

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.

[solenum]

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.

[cjwijtmans]

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

[bobintetley]

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

[bobintetley]

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!

[austin-calkins]

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.

[Lejoni]

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

[bobintetley]

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.

[smirgol]

@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.

[Lejoni]

@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.

[Lejoni]

@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.

[bobintetley]

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.

[Lejoni]

@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.

[Lejoni]

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.

[GloriousEggroll]

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

[winterwicht]

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

[nijiwar]

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

[HughPH]

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)

[bobintetley]

@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.

[progo]

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.

[CSahajdacny]

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

[progo]

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

[dragonfly-lover]

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

[FlenarnTemp]

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).

[jarrard]

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.,

[FlenarnTemp]

@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.

[kivoli]

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?

[jarrard]

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)

[CSahajdacny]

Have you tried with PROTON_NO_ESYNC=1 %commmand%?

[kivoli]

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.

[jarrard]

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

[Neirth]

@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. #308 (comment)

[waffshappen]

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 ValveSoftware/steam-for-linux#5831 to me but atleast i got it to run for now. Of course would be much nicer with DXVK instead.

[jarrard]

Odd, maybe a bug in DXVK?

[kisak-valve]

Memory Allocation Error

Issue transferred from #5855.
@Osced86 posted on 2022-05-22T22:52:44:

I'm using Proton 6.3 and have recently noted that I'm getting Memory Allocation problem, when using FO4Edit it crashes around 1,5-1,8 gb RAM, when I used an older version I had no problem. Have no idea what can have changed, since it worked before, more then upgraded Proton. Have tried Proton 7 and gives same error.

I've looked at the Proton debug log and found this error: virtual:try_map_free_area mmap() error cannot allocate memory, range 0xf4f60000-0x8ad0000, unix_prot 0x3. Have found this error even when it doesn't crash, but I think it can be connected with my issue.

Hope that someone that can put me in the right direction to fix my problem.

Proton Details.
Proton: 1638789187 proton-6.3-8c
SteamGameId: 377160
Command: ['/home/****/.local/share/Steam/steamapps/common/Fallout 4/Fallout4Launcher.exe']
Options: {'forcelgadd', 'noesync'}
depot: 0.20220329.49
pressure-vessel: 0.20220315.0
scripts: v0.20220311.0-0-gae4cbed
soldier: 0.20220329.0 soldier 0.20220329.0
Kernel: Linux 5.4.0-110-generic #124-Ubuntu SMP Thu Apr 14 19:46:19 UTC 2022 x86_64

[sebaro]

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.

[kisak-valve]

Hello @sebaro, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the crash, 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.

[sebaro]

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.

[csc-chicken]

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

[kayomn]

Replying to #308 (comment)

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.

[damntourists]

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.

[kisak-valve]

Fallout 4: Next Gen Update Gui Scaling Issues on Alternate Screen Sizes (377160)

Issue transferred from #7682.
@deathmarine posted on 2024-04-29T19:08:30:

Compatibility Report

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

System Information

• GPU: Steam Deck (AMD Custom GPU 0405)
• Video driver version: Steam Deck
• Kernel version: Steam Deck 6.1.52-valve16-1-neputune-61
• Link to full system information report as Gist:
• Proton version: 8.0.5

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Logs attached.
steam-377160.log

Symptoms

The UI within the game does not appear to be scaled correctly when the Steam Deck is connected to a different screen. I'm assuming this is due to the window in which the application is running as changes the fallout4perf.ini have no affect.

Reproduction

Connect Steam Deck to an external screen with any USB-C port replicator or dock.
Open vanilla Fallout 4 with latest updates. Controller Optional.
Menu is skewed slight down post loading screens. Menus in game are no longer visible will add screen shots.

[j20001970]

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

[TheEpicNoobZilla]

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.

[j20001970]

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.

[alasky17]

@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]

@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.