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

Games using proton_tkg_9.21.r1.g32abf9fc get stuck on 'launching' in steam #1316

Open
StelardActek opened this issue Nov 14, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@StelardActek
Copy link

I've been building proton-tkg myself in order to test out NTsync. I was able to build a working version of 9.20, however when I try the same process now the proton-tkg.sh script builds 9.21 and that version gets stuck at the 'Launching' stage in Steam. As best I can tell, the game itself doesn't actually start at all.

After waiting a few minutes to check, I would run pgrep -a wine to see what is running, and I would get something like the below:

1533368 /home/stelardactek/.local/share/Steam/compatibilitytools.d/proton_tkg_9.21.r1.g32abf9fc/files/bin/wine64 start.exe /b C:\Program Files (x86)\Steam\Steam.exe /home/stelardacte
k/.local/share/Steam/legacycompat/iscriptevaluator.exe legacycompat\evaluatorscript_2139460.vdf
1533406 C:\windows\system32\wineboot.exe --init
1533411 C:\windows\system32\winedevice.exe
1533421 C:\windows\system32\winedevice.exe

Out of curiosity I ran the command /home/stelardactek/.local/share/Steam/compatibilitytools.d/proton_tkg_9.21.r1.g32abf9fc/files/bin/wine64 start.exe /b "C:\Program Files (x86)\Steam\Steam.exe /home/stelardactek/.local/share/Steam/legacycompat/iscriptevaluator.exe" legacycompat\evaluatorscript_2139460.vdf and got the following output:

wine: using fast synchronization.
002c:fixme:winediag:loader_init Wine TkG (staging) 9.21 is a testing version containing experimental patches.
002c:fixme:winediag:loader_init Please don't report bugs about it on winehq.org and use https://github.com/Frogging-Family/wine-tkg-git/issues instead.
0058:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\win32k.sys"
0058:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\drivers\\dxgkrnl.sys"
0058:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\drivers\\dxgmms1.sys"
007c:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\win32k.sys"
007c:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\drivers\\dxgkrnl.sys"
007c:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\drivers\\dxgmms1.sys"
0080:fixme:wineusb:query_id Unhandled ID query type 0x5.
003c:err:service:process_send_command receiving command result timed out
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"winebus" failed to start: 1053

Running the same command against 9.20 gets a similar output except without these lines:

003c:err:service:process_send_command receiving command result timed out
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"winebus" failed to start: 1053

And the command actually returns to the command prompt with a ShellExecuteEx failed: Path not found., I presume because I'm not in the correct directory for the relative path legacycompat\evaluatorscript_2139460.vdf

Hopefully this is all relevant and useful information. Sorry if it isn't.

@Tk-Glitch Tk-Glitch added the bug Something isn't working label Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants