search

ValveSoftware / Proton

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

The First Descendant (2074920) #7873

Open nimbold opened 3 months ago

nimbold commented 3 months ago

Compatibility Report

System Information

I confirm:

steam-2074920.log

Symptoms

The game always runs on iGPU instead of Dedicated GPU. I tried multiple launch commands, but I didn't have any luck. I tried these: __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia %command% and prime-run %command%

Reproduction

  1. Open Steam and run the game
  2. Try with no launch command or launch commands mentioned above
  3. The game runs on iGPU no matter the launch command and therefor the perfromance is ugly
nimbold commented 3 months ago

I found the workaround fix thanks to a Nobara linux discord user. We can fix this by vulkan icd loader method. I just added this in launch command and it works now: DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce GTX 1650" VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json %command%

froz3n commented 3 months ago

Just want to report that deleting prefix then starting the game can cause black screen and the game won't start. Seems the game failed to create user config file and can't start.

I crashed and got blackscreen. Nuking prefix and verifying files didn't help. The thing that fixed my black screen problem is this : https://steamcommunity.com/app/2074920/discussions/0/4408543731839110883/

kisak-valve commented 2 months ago

The First Descendant: After 1.0.2 patch refuses to launch

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7889. @maxsupermanhd posted on 2024-07-11T23:03:55:

Compatibility Report

System Information

I confirm:

steam-2074920.log

Symptoms

It does not launch.

Right after opening the window (0 frames drawn) it either closes immediately or hangs in infinite loop consuming 2 cores of the CPU.

Reproduction

Start the game

maxsupermanhd commented 2 months ago

Log with the crash: steam-2074920.log (log with infinite loop in message above)

maxsupermanhd commented 2 months ago

In console_log.txt in some cases a line

naries/Win64/M1-Win64-Shipping.exe: ../../src/xcb_io.c:626: _XAllocID: Assertion `ret != inval_id' failed.

appears upon crash, no idea how to fix/approach it really...

alligatorshoes commented 2 months ago

Working fine for me here on GE-Proton 9.9.

maxsupermanhd commented 2 months ago

Just installed GE-Proton 9.10, same results, I think it is something to do with the game, not Proton

froz3n commented 2 months ago

Shot in the dark, but @maxsupermanhd have you tried creating config file like in the link on my post ?

maxsupermanhd commented 2 months ago

Shot in the dark, but @maxsupermanhd have you tried creating config file like in the link on my post ?

Yes, it did nothing, let alone it crates one by itself and still goes into infinite loop or crashes in xcb_io.c.

Also tried running in Bottles but not much success, identical results...

maxsupermanhd commented 2 months ago

Is there a way to intercept crash report data or gather some logs that would explain what exactly game is trying to do and where it is failing?

froz3n commented 2 months ago

@maxsupermanhd Does PROTON_LOG=1 do nothing ?

Also seems on Linux there's a disconnection problem (code NE:1000). Someone here said it's an EAC error but I don't know how to test the fix on fedora.

maxsupermanhd commented 2 months ago

Does PROTON_LOG=1 do nothing ?

Well not nothing, it generates a log with nothing interesting inside. The actual crash message is not being logged in it, it is instead found in console_log.txt file, see my comment above. Just re-tested it and it is absolutely identical despite having couple of updates. I wonder if my system has too new libraries/drives... Might try to run it on my ubuntu laptop for giggles since I believe there are people for who it "just works"

maxsupermanhd commented 2 months ago

Indeed, after steam transferred the game via my fast local network to my very slow laptop that can barely count as a thin client for streaming games, it started up perfectly, although with expected rock bottom unplayable performance. I had doubts it will even have enough vram.

So are there any other people on current Arch here with the game running?

maxsupermanhd commented 2 months ago

Ok, even more troubleshooting from my side, I side-rolled Fedora Workstation 40 and it launched there just fine. Current Arch borked? Tomorrow will maybe try rolling back whole system to pre-patch date and see what happens...

maxsupermanhd commented 2 months ago

Ok so stars lined up real cool, I imagine TFD decided to grab my AMD igpu for upscaling or something (I have one in my ryzen cpu) but it is disabled on bios level so it was just falling over, after adding DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce RTX 4060" I presume it decided not to do that anymore and launched just fine... Case closed.

P.S. when tested on Fedora performance was literal seconds per frame so I bet it somehow succeeded in what it tried to do and utilized cpu/igpu to upscale somehow

tomByrer commented 1 month ago

I had First Descendant working for a few hours, worked good aside from a few disconnects. But then it stopped working, even after a simple reinstall.

patlefort commented 2 weeks ago

I am able to run it on my laptop (Dell G5 15 SE), but it won't on my desktop (threadripper 1950x and radeon 6900xt). Both are running Arch Linux. The game will show the initial load screen and then just exit. I tried proton experimental and GE proton. Log shows no obvious problem or crash: steam-2074920.log