-
Notifications
You must be signed in to change notification settings - Fork 1.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
3d Aim Trainer (1600530) #5033
Comments
@Frequential Does the newly released Proton 6.3-6 fix the launch failure? There was a fix included specifically for this crash :) |
Hi there @alasky17, I've tried the 6.3.6 version and the Experimental once again, to no avail. |
@Frequential Thank you for retesting :) Could you upload a new log of the crash with 6.3-6 just in case something changed with the crash under the hood? |
@alasky17 It's been a while, but the game still doesn't work, even though it's supposedly been fixed. The first time after installation and download (including Proton), the game outputs an error similar to the one above, after closing the game and reopening it, though, it shows no error but no windows are created and nothing happens. To close the game, I have to kill steam via the system monitor or alt+4 and “exit now”. (Not always, for some reason) I left the game running for a while and recorded the logs. This is happening in flatpak and the rpm version of steam, I've found no way around this. Edit: I just checked the files, and nothing has been written to them, I just tried to run the game a couple more times, logs aren't being recorded, It just doesn't do anything. |
The UV_pipe_open thing seems to be a electron-logging thing where node or whatever tries to pass stdout to a stream opener when in linux it's a file and blows up. If you pull apart the app.asar file, set electron logging to file, then recompile, you can get past the electron logging issue. I have no idea why, it looks like a modern version of electron, electron logging, etc etc. Maybe its an ancient version of node or something bundled in the app. HOWEVER, once you get past the electron logging issue, you also get a black screen that immediately crashes to desktop. The next issue you'll run into is this guy: Proton Experimental: steam-1600530.log Real nasty stuff! It's certainly been weird debugging windows issues, I hope this is helpful to someone else. |
It works! Out of the blue it works great. Thank you for fixing this, whoever it was who fixed things! |
@lutzseverino Could you please retest again with Proton 8.0? It sounds like it could be working now 🤞 |
I just installed the game on Mint 21, I was only able to get it working using Proton Experimental, on which it runs perfectly. With proton 8 and below, it does not even open. Note: The current latest stable that I can see is Proton 8.0-2 |
Compatibility Report
System Information
I confirm:
Symptoms
The game fails to launch and reports a JavaScript error in a popup.
Reproduction
Install the game and launch.
Log files
steam-1600530 (p6.3-5).log
steam-1600530 (pexp).log
The text was updated successfully, but these errors were encountered: