-
-
Notifications
You must be signed in to change notification settings - Fork 442
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
Alternative Legendary Path not being recognized #781
Labels
bug:confirmed
Something isn't working.
Comments
Can you try this on the beta release? |
Confirmed the bug, I'll fix it on next release. |
flavioislima
added a commit
that referenced
this issue
Dec 21, 2021
7 tasks
Thank you very much! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
IMPORTANT! Do not erase this template!
Is this a game issue? If YES please use our Discord to get help.
Open here only issues with Heroic like: Heroic doesn't open, some button is out of place, Heroic closes unexpectedly, installs got interrupted, etc.
Try to get help on our Wiki first: https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/wiki/Troubleshooting
Describe the bug
I need to use a custom path for Legendary. I have set it on the Settings and the config file is showing it as expected:
But when I try to execute a game, it uses another Legendary path. See logs below.
Add Logs
Crash report is empty. The launch command is executing a legendary path that seems to be the default, that I want to avoid because it won't work on NixOS, that's why I'm using another path for Legendary.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Application will use alternative path to run game.
Screenshots
Desktop (please complete the following information):
Additional context
Although this is not on an OS that is officially supported, I think that as long as the application can use the alternative path for Legendary, it would be enough to solve the issue.
The text was updated successfully, but these errors were encountered: