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

Computed save path wrong on linux #41

Closed
tastytea opened this issue May 22, 2020 · 4 comments
Closed

Computed save path wrong on linux #41

tastytea opened this issue May 22, 2020 · 4 comments

Comments

@tastytea
Copy link

The computed save path for “Untitled Goose Game” (Flour) is %APPDATA%/../locallow/House House/Untitled Goose Game/. I guess %APPDATA% should be translated to ${WINEPREFIX}/drive_c/users/${USER}/Application Data/?

@derrod
Copy link
Owner

derrod commented May 22, 2020

Yes, it's currently not done automatically since there's no way to know which wine prefix is used for that game (if you use more than one) unless it's set in the config. In the future third party integrations and changes to how legendary itself handles wine should make that easier.

Edit: also I believe there's some issues with some games not properly resolving %APPDATA% within wine.

@derrod
Copy link
Owner

derrod commented Jun 7, 2020

Now that I know a little more about how WINE handles things related to %APPDATA% I think I can move forward with some changes that should make this a little easier. For instance by keeping track of the last wine prefix used to launch a game, and searching that or the one specified in the config to see if any save game exists. Of course it'd still ask for confirmation, I also don't intend to make it work with the -y flag to avoid accidental misconfiguration.

@xcodian
Copy link

xcodian commented Oct 29, 2020

Any progress on this change?
This is still an issue on the current version.

@derrod
Copy link
Owner

derrod commented Dec 16, 2020

Keeping track of the last wine prefix used is something I might come back to later (and with --set-defaults you can already achieve that). For now having working resolution at all is enough for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants