-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Comments
I found the workaround fix thanks to a Nobara linux discord user. |
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/ |
The First Descendant: After 1.0.2 patch refuses to launch Issue transferred from #7889. Compatibility Report
System Information
I confirm:
SymptomsIt 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. ReproductionStart the game |
Log with the crash: steam-2074920.log (log with infinite loop in message above) |
In console_log.txt in some cases a line
appears upon crash, no idea how to fix/approach it really... |
Working fine for me here on GE-Proton 9.9. |
Just installed GE-Proton 9.10, same results, I think it is something to do with the game, not Proton |
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... |
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? |
@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. |
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" |
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? |
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... |
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 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 |
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
The text was updated successfully, but these errors were encountered: