Dark Souls 3 stuck on "Launching"
Dark Souls 3 stuck on "Launching"
I just downloaded Dark Souls 3, when I hit "Play", it just stuck on "Launching" forever.
Register DarkSoulsIII.exe as none Steam game and force compatibility mode, it somehow still goes back to launch through official app page and gets stuck again.
Searched online, 2 guys on reddit described the same issue, with Pop!_OS 22.04 LTS and Mint 20.02, while I'm on Fedora 37 KDE.
Weirdest thing, when I hit "Verify Integrity of Game Files", it also gets stuck. It doesn't start nor fail, just infinitely checking something.
Strangely, browsing ProtonDB, I've seen no one had a similar issue. Even someone with exact same Distro had no problem whatsoever.
I don't know what to do now, so I'm asking for help, or just ideas for troubleshooting.
===============================
System info
Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.4.4-100.fc37.x86_64 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X570 GAMING X
================================
wine DarkSoulsIII.exe outputs:
002c:fixme:winediag:LdrInitializeThunk wine-staging 8.12 is a testing version containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org.
0088:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0088:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0088:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0088:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0078:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
0078:fixme:xrandr:xrandr10_get_current_mode Non- primary adapters are unsupported.
0078:fixme:xrandr:xrandr10_get_current_mode Non- primary adapters are unsupported.
0078:fixme:xrandr:xrandr10_get_current_mode Non- primary adapters are unsupported.
0078:fixme:xrandr:xrandr10_get_current_mode Non- primary adapters are unsupported.
0078:fixme:xrandr:xrandr10_get_current_mode Non- primary adapters are unsupported.
0078:fixme:xrandr:xrandr10_get_current_mode Non- primary adapters are unsupported.
0034:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
002c:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
0024:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
0110:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
[user@fedora Game]$ 0088:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled
type 00000005
0088:fixme:xinput:pdo_pnp IRP_MN_QUERY_ID type 5, not implemented!
0088:fixme:xinput:pdo_pnp IRP_MN_QUERY_ID type 5, not implemented!
0088:fixme:xinput:pdo_pnp IRP_MN_QUERY_ID type 5, not implemented!
0088:fixme:xinput:pdo_pnp IRP_MN_QUERY_ID type 5, not implemented!
I ran into this with Boltgun (and Remnant earlier in the week). Other symptoms were Steam not actually closing unless I
kill -9d it.From debugging, clearing my download cache got me to the point where it "launched" but nothing happened. Whereas Remnant launched normally. And steam closed normally the first time and then grabbed a crap ton of (presumably) shaders and redistributables. And now I am back to the previous symptoms.
So I assume something is funky with the current version of steam that is corrupting the download cache and I am not going to care until at least the next steam client update.
2okay, guess I'll wait
1Try Steam stable vs beta perhaps?
1Just popping back in to say I "fixed" it. Did a bunch of debug logging, figured out it was hanging in failing to install a prereq on the proton side, and confirmed that was another thing that was fixed by clearing download cache. Then thought through what would make that fail.
Turned off "Background processing of shaders" in downloads, full shutdown of steam, start up. Then cleared my download cache, killed all processes again, and logged back in.
So far no issues with any games. My working theory is it may have been a specific proton version corrupting the redistributables that was updated last week or that this is related to preprocessing of shaders not shutting down gracefully.
1
Do you have mangohud on our globally enabled?
1Try manually selecting the latest version of Proton in the game's compatibility settings, currently 8.0-3. That fixed the issue for me.
1Tried every version down to 6.3-8, no version changes anything.
1