While you're here, please consider supporting GamingOnLinux on:
Reward Tiers:
Patreon. Plain Donations:
PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers:
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- US operating system age verification bill "Parents Decide Act" gets published
- Mozilla announced "Thunderbolt", their open-source and self-hostable AI client
- PlayStation 3 emulator RPCS3 can now auto-configure games for you
- Gaming on Linux with an older GPU levels up with DXVK-Sarek v1.12 bringing major new features
- SDL (Simple DirectMedia Layer) ban AI / LLM code contributions
- > See more over 30 days here
- Steam achievement conundrum
- GustyGhost - Testing the VRAM valve patch
- Avehicle7887 - Away all of next week
- Liam Dawe - New Desktop Screenshot Thread
- tmtvl - Shop Crush - Psychological Horror Thrift Sim with Literal Illusio…
- hollowlimb - See more posts
How to setup OpenMW for modern Morrowind on Linux / SteamOS and Steam Deck
How to install Hollow Knight: Silksong mods on Linux, SteamOS and Steam Deck
Linux Distribution: Pop! OS 21.04
Desktop Environment: GNOME
Graphics Card: NVIDIA Geforce GT 635M
GPU Driver Version: 390
Have you checked for system updates?: Yes
If this is to do with Steam, please add your system read-out from Steam -> Help -> System Information (please put that into Pastebin/Gist as linked above!): https://pastebin.com/dVyM1e0V
If this is not Steam, you can still give us a system readout using inxi with "inxi -SbCGxx" in terminal (please put that into Pastebin/Gist as linked above!): n/a
You can note your issue below here
I'm trying to run AoE2 DE on my old Asus A75VJ with various Proton versions (including the latest GE version). Unfortunately, it either crashes on launch or shows the game logo and the Xbox signin prompt and crashes right after.
Based on my own googling, I'm afraid that the nvidia-driver 390 is simply too old, but any of the 4xx driver versions seems to be incompatible with my GPU as commands like `nvidia-settings` or `nvidia-smi` result in errors and I can not switch my system to the NVIDIA graphics mode.
According to ProtonDB however, the game has Gold status and many users with Pop! OS and NVIDIA GPUs report almost flawless experiences. Does anyone here know what might be my problem and how to fix it?
Note any particular steps to reproduce it below here
PS: Ignoring my NVIDIA GPU and running the game on my Intel integrated graphics doesn't work either.
Last edited by Itagane on 25 Aug 2021 at 7:10 pm UTC
Also, lately Proton likes to run everything (or most things) through Vulkan (neglecting OpenGL) which your video cards and drivers might not support. If the previous question doesn't help, you should look into forcing Proton to use OpenGL.
Last edited by tuxintuxedo on 26 Aug 2021 at 3:39 pm UTC
2. You might also try asking for help in the [Proton issues thread](https://github.com/ValveSoftware/Proton/issues/2995) for the game if you haven't already done so.
Use the Set Launch Options setting in the game's Properties dialog in the Steam client. Set the variable, followed by %command%. In your case, try "PROTON_USE_WINED3D=1 %command%" to use the OpenGL-based wined3d renderer instead of the Vulkan-based DXVK renderer.
That's almost straight from the Proton README linked above.
HTH,
PROTON_LOG=1 %command% PROTON_USE_WINED3D=1 %command%, I got a slightly longer log and updated the pastebin entry from my previous reply.Last edited by Itagane on 26 Aug 2021 at 6:28 pm UTC
PROTON_LOG=1 PROTON_USE_WINED3D=1 %command%The Proton log should be looong. The last log I grabbed from a game crashing on start was 44 000 lines...
======================Proton: 1629748146 proton-6.3-6c
SteamGameId: 813780
Command: ['/home/itagane/.steam/debian-installation/steamapps/common/AoE2DE/AoE2DE_s.exe']
Options: {'forcelgadd', 'wined3d'}
depot: 0.20210723.18
pressure-vessel: 0.20210722.0
scripts: v0.20210722.0-0-gb142f90
soldier: 0.20210719.0 soldier 0.20210719.0
User settings WINEDEBUG: +timestamp,+pid,+tid,+seh,+debugstr,+loaddll,+mscoree
======================
Best advice I can give is to ask for help in the [GitHub bug report mentioned previously](https://github.com/ValveSoftware/Proton/issues/2995). The problem with the logs is a separate issue, but my gut feeling for the problem with the game is that your GPUs are most likely simply too old.