Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The First Descendant (2074920) #7873

Open
2 tasks done
nimbold opened this issue Jul 4, 2024 · 15 comments
Open
2 tasks done

The First Descendant (2074920) #7873

nimbold opened this issue Jul 4, 2024 · 15 comments
Labels
Game compatibility - Unofficial Games not expected to work without issues XAudio2 Uses the XAudio2 subsystem

Comments

@nimbold
Copy link

nimbold commented Jul 4, 2024

Compatibility Report

  • Name of the game with compatibility issues: The First Descendant
  • Steam AppID of the game: 2074920

System Information

I confirm:

  • that I haven't found an existing compatibility report for this game.
  • that I have checked whether there are updates for my system available.

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
@kisak-valve kisak-valve added the Game compatibility - Unofficial Games not expected to work without issues label Jul 4, 2024
@kisak-valve kisak-valve changed the title The First Descendant only uses iGPU instead of D-GPU The First Descendant (2074920) Jul 4, 2024
@kisak-valve kisak-valve added the XAudio2 Uses the XAudio2 subsystem label Jul 4, 2024
@nimbold
Copy link
Author

nimbold commented Jul 5, 2024

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
Copy link

froz3n commented Jul 7, 2024

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
Copy link
Member

The First Descendant: After 1.0.2 patch refuses to launch

Issue transferred from #7889.
@maxsupermanhd posted on 2024-07-11T23:03:55:

Compatibility Report

  • Name of the game with compatibility issues: The First Descendant
  • Steam AppID of the game: 2074920

System Information

  • GPU: NVIDIA GeForce RTX 4060
  • Video driver version: nvidia-open 555.58.02
  • Kernel version: Linux 6.9.8-arch1-1
  • Link to full system information report: Gist
  • Proton version: 7, 8, 9, Experimental (others not tested)

I confirm:

  • that I haven't found an existing compatibility report for this game.
  • that I have checked whether there are updates for my system available.

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
Copy link

maxsupermanhd commented Jul 11, 2024

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

@maxsupermanhd
Copy link

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
Copy link

Working fine for me here on GE-Proton 9.9.

@maxsupermanhd
Copy link

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

@froz3n
Copy link

froz3n commented Jul 14, 2024

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

@maxsupermanhd
Copy link

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
Copy link

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
Copy link

froz3n commented Jul 17, 2024

@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
Copy link

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
Copy link

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
Copy link

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
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Game compatibility - Unofficial Games not expected to work without issues XAudio2 Uses the XAudio2 subsystem
Projects
None yet
Development

No branches or pull requests

5 participants