Steam for Linux

Steam for Linux

osced86 Jun 1, 2019 @ 1:25am
Fallout 4 won't launch (Proton 4-2-5)
Hi, I've recently purchased Fallout 4 as I've found comments about it should be able work on Ubuntu. Unfortunately I can't even get the game to launch, When I try to start the game nothing happens, have tried starting it via a terminal and got no output. Have been looking through lots of advice but nothing have helped me yet. As the game won't launch I got the feeling that something might be wrong with Proton. Tried some beta versions of Proton (3.16 and 3.17 but did not work either.

Hope someone here can help me understand what's the problem. See below for my computer information:


Processor:
CPU- Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz

OS:
Ubuntu 19.04 (64 bitar)
Kernelnamn: Linux
Kernelversion: 5.0.0-15-generic
X Serverleverantör: The X.Org Foundation
X Serverversion: 12004000
X Window Manager: GNOME Shell
Steam Runtime: jenkins-steam-runtime-beta-release_0.20190320.2

Graphics
Drivers: NVIDIA Corporation GeForce GTX 1650/PCIe/SSE2
Drivers Version 4.6.0 NVIDIA 430.14
OpenGL-version: 4.6
Skrivbordets färgdjup: 24 bitar per pixel
Skärmens uppdateringshastighet: 60 Hz
Leverantörs-ID: 0x10de
Enhets-ID: 0x1f82
Revision ej upptäckt
Antal skärmar: 1
Antal logiska grafikkort: 1
Primär skärmupplösning: 1920 x 1080
Skrivbordsupplösning: 1920 x 1080
Primär skärmstorlek: 20.08" x 11.30" (23.03" diag)
51.0cm x 28.7cm (58.5cm diag)
Primär buss: PCI Express 16x
Primär VRAM: 4096 MB
MSAA-lägen som stöds: 2x 4x 8x 16x

Audio
Sound card: Realtek ALC887-VD

Memory
RAM: 15950 MB



< >
Showing 1-11 of 11 comments
x_wing Jun 1, 2019 @ 8:07am 
There are many workarounds reported on protondb. Did you try setting WINEDLLOVERRIDES="xaudio2_7=n,b" PROTON_NO_ESYNC=1 %command% as startup options?

BTW, you must disable god rays in the game config. It seems to crash the game too (I think you can do it from game options once the game starts).
Last edited by x_wing; Jun 1, 2019 @ 8:07am
osced86 Jun 1, 2019 @ 8:30am 
Thank you for your taking your time responding. Unfortunately I've tried most of the solutions I found on Protondb. I tried your suggestion with both these options and something different happened now steam says the game is running, better than before when nothing happened at all.

I also got some information in the log now:

ERROR: ld.so: object '/home/saced/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/saced/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/saced/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/saced/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.

ERROR: ld.so: object '/home/saced/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
28292.569:0027:0028:trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\KERNEL32.dll" at 0x7b420000: builtin
wine: Felaktigt EXE-format för Z:\home\saced\.local\share\Steam\steamapps\common\Fallout 4\Fallout4Launcher.exe.^M

Not sure what these errors means, maybe you have a clue? Have looked around and it appears bad EXA format may be because of running Wine 32 instead of 64. From what I learned proton has there own version of Wine, not sure what I can do.

I think I've disable god rays in some settings in the beginning.
Last edited by osced86; Jun 1, 2019 @ 8:43am
Aoi Blue Jun 1, 2019 @ 6:27pm 
From https://www.protondb.com

Use the following launch parameters in your game advanced settings under Steam:
WINEDLLOVERRIDES="xaudio2_7=n,b" PROTON_NO_ESYNC=1 %command%

You will also need to make sure you have all your necessary i386 libs and drivers installed for Steam and Proton including the video drivers.

I suspect you don't have the i386 libs and drivers installed.
x_wing Jun 1, 2019 @ 7:01pm 
Originally posted by Aoi Blue:
From https://www.protondb.com

Use the following launch parameters in your game advanced settings under Steam:
WINEDLLOVERRIDES="xaudio2_7=n,b" PROTON_NO_ESYNC=1 %command%

You will also need to make sure you have all your necessary i386 libs and drivers installed for Steam and Proton including the video drivers.

I suspect you don't have the i386 libs and drivers installed.

I think that F4 is a 64 bit game.

For the OP, I read that the game takes a while to start on first boot (maybe for shaders cache creation?). As steam detects it as running, did you give it some time before closing it?
osced86 Jun 2, 2019 @ 12:53am 
Originally posted by Aoi Blue:
From https://www.protondb.com

Use the following launch parameters in your game advanced settings under Steam:
WINEDLLOVERRIDES="xaudio2_7=n,b" PROTON_NO_ESYNC=1 %command%

You will also need to make sure you have all your necessary i386 libs and drivers installed for Steam and Proton including the video drivers.

I suspect you don't have the i386 libs and drivers installed.

It was those settings I used to get the above errors. As X_wing and Rogue says the game is 64 bits. So it might be that Proton uses 32-bit wine, not sure where you can check which wine they are using or changing it. It really looks like proton tries to start the game in 32 bit.

Originally posted by x_wing:
Originally posted by Aoi Blue:
From https://www.protondb.com

Use the following launch parameters in your game advanced settings under Steam:
WINEDLLOVERRIDES="xaudio2_7=n,b" PROTON_NO_ESYNC=1 %command%

You will also need to make sure you have all your necessary i386 libs and drivers installed for Steam and Proton including the video drivers.

I suspect you don't have the i386 libs and drivers installed.

I think that F4 is a 64 bit game.

For the OP, I read that the game takes a while to start on first boot (maybe for shaders cache creation?). As steam detects it as running, did you give it some time before closing it?

I waited a couple of minutes and nothing happened.
Last edited by osced86; Jun 2, 2019 @ 1:07am
x_wing Jun 2, 2019 @ 7:14am 
Originally posted by osced86:
Originally posted by Aoi Blue:
From https://www.protondb.com

Use the following launch parameters in your game advanced settings under Steam:
WINEDLLOVERRIDES="xaudio2_7=n,b" PROTON_NO_ESYNC=1 %command%

You will also need to make sure you have all your necessary i386 libs and drivers installed for Steam and Proton including the video drivers.

I suspect you don't have the i386 libs and drivers installed.

It was those settings I used to get the above errors. As X_wing and Rogue says the game is 64 bits. So it might be that Proton uses 32-bit wine, not sure where you can check which wine they are using or changing it. It really looks like proton tries to start the game in 32 bit.

You can check your wine prefix arch with "winecfg && %command%" as game startup option. When running the game, a wine config dialog will be shown. If in the dropdown list of windows versions you can see listed Windows 98, then you're in a 32 bits prefix.

Anyway, I think that proton always use a 32 bit prefix but that isn't a problem for 64 bit games (for instance, I have the PES 2019 Demo -- a 64 bit game -- and it works fine with the 32 bit Proton prefix).

Are you able to run any other game with Proton (one that uses DX 11)? I suspect that you didn't install vulkan libs...
osced86 Jun 2, 2019 @ 7:42am 
Originally posted by x_wing:
Originally posted by osced86:

It was those settings I used to get the above errors. As X_wing and Rogue says the game is 64 bits. So it might be that Proton uses 32-bit wine, not sure where you can check which wine they are using or changing it. It really looks like proton tries to start the game in 32 bit.

You can check your wine prefix arch with "winecfg && %command%" as game startup option. When running the game, a wine config dialog will be shown. If in the dropdown list of windows versions you can see listed Windows 98, then you're in a 32 bits prefix.

Anyway, I think that proton always use a 32 bit prefix but that isn't a problem for 64 bit games (for instance, I have the PES 2019 Demo -- a 64 bit game -- and it works fine with the 32 bit Proton prefix).

Are you able to run any other game with Proton (one that uses DX 11)? I suspect that you didn't install vulkan libs...

I tried the command and found windows 98 in the drop down menu, have looked around all the Vulkan libs I can think I've got them installed, but not the dev files and something called vulkan-tools and vulkan-utils. Do you think I need those?

The problem still seems to be that Fallout4 Launcher can't be started, due to bad 'exe' format which I've read is usually due to wrong running 32 bit in 64 bit or vice verse. However you say that it should not be a problem. It's quite confusing, it probably is some library that is missing. Only need to find it, my computer is very new so have not installed that much on it yet. I'm quite new at Linux gaming so are unfortunately not so knowledgeable.
osced86 Jun 2, 2019 @ 2:44pm 
Originally posted by Rogue:
I'm pretty sure the Nvidia drivers include Vulkan, but you may install "libvulkan1" which is the Vulkan loader library package in Ubuntu. Although, it's not listed on the Proton requirements page... so if it is needed, this page should be updated to reflect that:

https://github.com/ValveSoftware/Proton/wiki/Requirements#nvidia

Steam for Linux requires a 32-bit C library (glibc) and 32-bit OpenGL library (depends on your driver) from the host distro. If you don't have those, the Steam client itself would fail to launch. You seem to have no issues launching Steam, so you should be all set there.

The errors about "wrong ELF class" literally say "ignored" at the end of them, those are not really errors and you can safely ignore them. Steam includes both 64- and 32-bit versions of some libraries and only one version will load successfully. This "error" is displayed even when Steam (and the in-game overlay) is working perfectly.

Make sure you have Python 3 installed and available in your path as "python3" because that's the only other hard requirement for Proton (you probably already have it, but it doesn't hurt to check).

It's not really worth spending too much time trying to get games running with Proton. Test the game, if it runs, awesome, if it doesn't try a different version of Proton, and/or try some of the runtime config options[github.com], and then add your report to ProtonDB[www.protondb.com].

It's Valve's job to tweak Proton so that these games work OOTB. If you want to go the extra mile, you can use PROTON_LOG to create a useful debug log and upload that along with your comment to the relevant Github issue:

https://github.com/ValveSoftware/Proton/issues/308

Aside from that, try vanilla Wine with a front-end like Lutris instead and wait for Valve to update Proton, or wait for the game to be whitelisted:

https://lutris.net/games/fallout-4/

Thank you for your comments, maybe will try to use Lutris, but will try some more stuff. As most people appears to have succeed with starting the game it's likely something wrong on my end and that's what I'm looking for.
Aoi Blue Jun 2, 2019 @ 5:59pm 
Originally posted by osced86:

It was those settings I used to get the above errors. As X_wing and Rogue says the game is 64 bits. So it might be that Proton uses 32-bit wine, not sure where you can check which wine they are using or changing it. It really looks like proton tries to start the game in 32 bit.

No, the issue is that Proton is 64/32bit combination wine. Certain games won't run without the appropriate wine dependencies installed. It's sort of hit or miss too.

To be specific Proton launches a standard WOW64 setup for Win32 on it's Win64 setup no matter what game you are running. This requires some 32 bit Linux libraries.

I usually just install all the recommends and suggests for Wine Staging myself. you can get Wine Staging from winehq.org. Wine staging is also useful for running other Windows programs that aren't on Steam.

osced86 Jun 3, 2019 @ 9:18am 
Originally posted by Aoi Blue:
Originally posted by osced86:

It was those settings I used to get the above errors. As X_wing and Rogue says the game is 64 bits. So it might be that Proton uses 32-bit wine, not sure where you can check which wine they are using or changing it. It really looks like proton tries to start the game in 32 bit.

No, the issue is that Proton is 64/32bit combination wine. Certain games won't run without the appropriate wine dependencies installed. It's sort of hit or miss too.

To be specific Proton launches a standard WOW64 setup for Win32 on it's Win64 setup no matter what game you are running. This requires some 32 bit Linux libraries.

I usually just install all the recommends and suggests for Wine Staging myself. you can get Wine Staging from winehq.org. Wine staging is also useful for running other Windows programs that aren't on Steam.

Thank you, it make sense that something is missing will try that later, hopefully it will work with your suggestions.
osced86 Jun 6, 2019 @ 10:31am 
I've installed Wine staging and now it works, thank you all for your useful comments.
< >
Showing 1-11 of 11 comments
Per page: 1530 50

Date Posted: Jun 1, 2019 @ 1:25am
Posts: 11