ValveSoftware
Fallout 3 - Game of the Year Edition (22370)
Already stated by multiple users in the compatibility sheet but I wanted to make a formal report here to see if maybe someone has figured out a workaround.
On first launch, when the wine prefix configuration is taking place the following error pops up:
I tried multiple things like launching in DXD9 mode, installing different combinations of winetricks verbs (xact, msasn1, dxdiag, ...) from WineHQ's entry for Fallout 3, also setting windows compatibility to win XP instead of win 7 among other things, as well as installing .NET 4.5.
Nothing seems to work, the launcher works but once the "Play" button is hit, a fullscreen black window pops up and it freezes, only way to get out is to kill the process from another TTY.
Stack trace for anyone interested: https://gist.github.com/Elkasitu/d7644cecd5746f90ef5c9619175494cb
I got it to run by replacing FalloutLauncher.exe by Fallout3.exe, the game works seemingly randomly:
- The main menu is super laggy
- When launching a new game it can either freeze (with in-game sound) or crash
- If the game reaches the part where the user gains control, then the game will run perfectly
Fallout 3 black screen without xlive.dll
Issue transferred from https://github.com/ValveSoftware/Proton/issues/1483. @Kryuko posted on 2018-09-16T11:16:07:
Compatibility Report
- Name of the game with compatibility issues: Fallout3
- Steam AppID of the game: 22370
System Information
- GPU: GTX970
- Driver/LLVM version: nvidia 396.54
- Kernel version: 1.15
- Link to full system information report as Gist: https://gist.github.com/Kryuko/cbe1d228889d81914fe9d1e149a80f2a
- Proton version: every version
I confirm:
- [x] that I haven't found an existing compatibility report for this game.
- [x] that I have checked whether there are updates for my system available.
Symptoms
Reproduction
Just open the game. You will see the launcher, if you click play you will have a black fullscreen window. Putting the xlive.dll file in the root game directory solve the issue.
Thank you in advance.
Got it working on Intel's GPU with advices from ProtonDB and following registry file:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Wine\Direct3D]
"VideoPciDeviceID"=dword:00000402
"VideoPciVendorID"=dword:000010de
@RussianNeuroMancer
Sorry to bother, but could you please describe the process of applying that registry file?
@danieldukic Just launched regedit inside Proton bottle:
WINEPREFIX=/home/user/.steam/steam/steamapps/compatdata/22370/pfx regedit
Worked for me after installing xlive redist
http://download.gfwl.xboxlive.com/content/gfwl-public/redists/production/xliveredist.msi
env WINEPREFIX="/home/$USER/.local/share/steam/steamapps/compatdata/22370/pfx" WINEPATH="/home/$USER/.local/share/steam/steamapps/common/Proton\ 3.7/dist/bin/wine64" wine start Downloads/xliveredist.msi
Works just fine on my end with Proton 5.0-9 after bypassing xlive.dll with this open source tool. However like many games, it really doesn't like alt-tabbing.
System Information
- GPU: RX Vega 56
- Driver/LLVM version: mesa 20.1.7 with RADV enabled
- Kernel version: 5.8.8-zen1-1-zen
- Link to full system information report as Gist: https://gist.github.com/kattjevfel/fbd4d680c78809f4d484cae72410a50e
- Proton version: Proton 5.0-9
Symptoms
.NET 3.0 error comes up during first time install thingy, but doesn't seem to matter. Needs xlive patched out, just like on Windows. Does not like alt-tabbing (crashes the game)
System Information
- GPU: RX 6600
- Video driver version: Mesa 23.3.0
- Kernel version: 6.6.7-200.fc39.x86_64
- Link to full system information report as Gist:
- Proton version: 8.0-4
- OS: Flatpak
Symptoms
I think a new update removed live from fallout on the latest update so this should be resolved but I was getting some weird blurriness on the proton 8.0 version that I wasn't getting running it thru wine with native Wayland and the new wow64 mode
My bad I just realized that my resolution was set really low on steam in fallout 3 also for new Vegas and fallout 3 the controllers work except for the launcher
I have noticed though that gamescope doesn't seem to work for this game on the flatpak version of steam for some reason though I haven't tested it natively on fedora
I just tested out gamescope and its fixed for me, thanks! I will add that the cursor is big on the launcher but I'm not sure if that's a feature or not for controllers
Also, sorry for no logs btw I took some time to find the directory of where there stored in flatpak, for future reference its in ~/.var/app/com.valvesoftware.Steam/
My setup: OS: Arch Linux DE: GNOME 46 KERNEL: 6.8.7-zen1-1-zen CPU: AMD Ryzen 7 5800X3D 8-Core GPU: AMD Radeon RX 6800 XT (radeonsi, navi21, LLVM 17.0.6, DRM 3.57, 6.8.7-zen1-1-zen) GPU DRIVER: 4.6 Mesa 24.0.5-arch1.1 RAM: 32 GB
Having an issue running this game with the last mutter 46.1, my mouse cannot interact with the game.
- I press play on the mini launcher
- the game goes fullscreen/borderless
- I try to use the mouse it doesn't focus on the game but on the desktop or below app, feels the game does not catch the mouse events or movement, keyboard works.
Once I try to right-click i get the menu from desktop:
Changing back to mutter 46.0 fixes the problem.
Something I noticed when working on this game's launcher for Xalia is that whenever the mouse button is pressed on the launcher, it initiates a move operation, so you can drag the window around from anywhere. This behavior occurs even when clicking on a button, and it's the same on Windows. On Wine, this is translated to a _NET_WM_MOVERESIZE request for the window manager. Maybe Mutter's handling of that request changed. That's just a guess, though.
I've run into what I believe may be a partial regression of Wine Bug 31566 while playing Fallout 3 using Proton on my Steam Deck.
Seemingly at random, the Pip-Boy radio will fail to correctly play a song - instead a low volume "click" approximately every second can be heard. Switching the radio station off and then on again in the Pip-Boy menu temporarily fixes the issue but it always returns (either at the end of the current song or a couple of songs later), the voice announcements between the songs do always play correctly. The issue still occured after switching from Proton 9.0-2 to Proton Experimental though subjectively I got an impression it occured bit less frequently.
As suggested in the above linked bug thread, I tried installing the native windows quartz dll and an mp3 audio filter in the proton prefix (though I chose to use lavfilters rather than l3codecx), protontricks 22370 quartz lavfilters which seems to have resolved the issue.
I assume that either https://github.com/ValveSoftware/Proton/commit/4331a07c30fd45895bf532fcd9c7dced2c99fffc or https://github.com/ValveSoftware/wine/commit/8f59e1a1359b96c9d9171dc5af8d3870625c4582 should have fixed that now in experimental.
On Steam Deck I can't get through the install script due to the complaining about needing .NET 3.0 referenced in the initial report on this, but they've since patched out Xbox Live so that shouldn't be related. Clicking past this leads me to a version of the original DVD autorun launcher (bear in mind this is a steam install) and when I press install it says it can't find the DVD.
I've tried this with stable and experimental proton on my Steam Deck. Weirdly it installed fine on my laptop running Arch.
If you mean GFWL that should be possible to get working with https://github.com/InvoxiPlayGames/gfll-dll
It claims I don't have the game installed & need to insert the CD\DVD media to reinstall
This script resolves that https://github.com/kpmgeek/Fo3_SteamDeck_Install_Fix
¿Does this work for Fallout New Vegas?