-
Notifications
You must be signed in to change notification settings - Fork 16
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
Bazzite/(Immutable?) Launcher won't work due to path issues #202
Comments
Go into files |
I've done it, didn't work. I mention that at the start of the post. Everything but the "global" install is pointing towards /var/home/... because I installed the game to the SD card, game really doesn't require an SSD. That's why I ended up opening this issue :p Edit: here's my config.json in case anyone may see something I missed:
|
This worked for me on bazzite-deck too |
Are you sure that's issues with the f drive/partition kftX you set the game path to? |
Yeah, nope. Issue happens both if that's the path (SD card) or if I set it to be inside of Unless the issue is that my path has spaces on it, which seems to be the only difference. Lemme try renaming to HSR and I'll edit. |
Issue fixed by reinstalling and manually changing the global path to where I wanted it to be (SD card in this case). I guess I should've done that to begin with, but felt that having the app itself on the SSD might help in some way. Apparently it did not. |
Recently installed Bazzite on my Steam Deck and was trying to get Honkers installed on it.
Initial set-up was complicated since it was looking/trying to use folders it could not write to, but this was solved with config tweaks suggested in this issue #72.
Despite a successful set-up of the launcher, upon opening it I was immediately greeted with errors related to pathing issues. Pressing the "repair files" option on the settings however did download the game, however the launcher is unable detect anything or start the game. Classic mode is also unavailable. Log below (I cleared the logfile beforehand to remove as much unnecessary info as possible).
The text was updated successfully, but these errors were encountered: