-
Notifications
You must be signed in to change notification settings - Fork 54
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
FA Forever client is unable to successfully start game itself #177
Comments
The legacy setup only works for Wine, not Proton. Not new Proton versions at least, it may or may not work with an old Proton version. Please tell me what "being unable to use non-legacy wizard" means and I may be able to help you. |
I see, this env var got removed: ValveSoftware/Proton#7575 In the meanwhile, you can either use Proton 8, or manually put the following script where the setup script excepts it to be:
|
Thanks, manually setting up the script you gave for Proton 9.0 worked |
umu (https://github.com/Open-Wine-Components/umu-launcher) can be used now, but it has to be in user's PATH to work. I guess I'll get around to updating the setup script later. |
Issue is exactly as the title suggests.
Exact package used:
faf-client-bin
.I can confirm that I have run the setup script successfully, only noting that I was unable to use the non-legacy proton config wizard. I have also manually checked that every path provided by the setup script looks correct at a light glance.
Additionally, I can confirm that the game itself runs fine when launched through steam.
The only seemingly relevant logs are as follows (redacted for privacy). The game itself did not write any logs. (I have checked
~/.faforever/logs/game_*.log
.Additionally, experience suggests that the issue could have stemmed from running the game on a non-default steam library, but moving the game over from my HDD onto my boot drive, re running the setup script and trying again resulted in the exact same result.
I am at my wit's end here, I have no idea what's causing the issue and where to look further for any additional clues.
The text was updated successfully, but these errors were encountered: