search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
23.45k stars 1.03k forks source link

Fallout 3 - Game of the Year Edition (22370) #370

Open Elkasitu opened 5 years ago

Elkasitu commented 5 years ago

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:

screenshot_20180824_104742

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.

System Information

Elkasitu commented 5 years ago

Stack trace for anyone interested: https://gist.github.com/Elkasitu/d7644cecd5746f90ef5c9619175494cb

Elkasitu commented 5 years ago

I got it to run by replacing FalloutLauncher.exe by Fallout3.exe, the game works seemingly randomly:

kisak-valve commented 5 years ago

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

System Information

I confirm:

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.

RussianNeuroMancer commented 5 years ago

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
danieldukic commented 5 years ago

@RussianNeuroMancer

Sorry to bother, but could you please describe the process of applying that registry file?

RussianNeuroMancer commented 5 years ago

@danieldukic Just launched regedit inside Proton bottle:

WINEPREFIX=/home/user/.steam/steam/steamapps/compatdata/22370/pfx regedit

superjamie commented 5 years ago

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
shoober420 commented 4 years ago

Compatibility Report

System Information

LOG: steam-22370.log

Symptoms

Black screen window at launch, error during install 7E5CFE48-13DA-43E9-AFDD-F3CB9D47AA61

The "xlive.dll" might be the cause of this (https://bugs.winehq.org/show_bug.cgi?id=23532).

kattjevfel commented 3 years ago

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

steam-22370.log

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)

m1m1k4tz commented 6 months ago

System Information

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 x

wayland

m1m1k4tz commented 6 months ago

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

m1m1k4tz commented 6 months ago

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

m1m1k4tz commented 6 months ago

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 Screenshot from 2024-01-03 20-27-25

m1m1k4tz commented 6 months ago

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/

PickMeNow commented 2 months ago

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. 1) I press play on the mini launcher 2) the game goes fullscreen/borderless 3) 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: image

Changing back to mutter 46.0 fixes the problem.

madewokherd commented 2 months ago

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.