-
-
Notifications
You must be signed in to change notification settings - Fork 480
With "MANGOHUD=1", Heroic behaves like the option inside Heroic is set to 1 and uses its own config file #2922
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
Comments
I have this bug too. The reason is because of the code linked below. HeroicGamesLauncher/src/backend/launcher.ts Line 409 in 1020e7e
|
#2841 is the offending commit. globally set syslinking |
What exactly did you link from where to where? Cause just setting an explicit |
working on trying to resolve the XDG_CONFIG_HOME overrides, I fixed it with nile so far, legendary is waiting on a PR |
this should fix it for yall: #3137 |
TYVM 👍 |
In lieu of the fix being merged (much appreciated!), the exact symlink for MangoHUD is:
For vkBasalt, it would likely be:
This is because |
This should be fixed now in heroic 2.10.0 since we don't use the XDG_CONFIG_HOME env anymore |
Describe the bug
In the case where the user has "MANGOHUD=1" in /etc/environment or launch Heroic with "MANGOHUD=1 heroic", Heroic behaves like the option inside Heroic is set to 1 and uses its own config file. It's not an expected behavior.
In my case, I have "MANGOHUD=1" in /etc/environment to have Mangohud everywhere with my config file. If I run Heroic in this situation, when I launch a game Mangohud is here but not using my config file, it's a default config file instead.
This issue doesn't exist in Heroic 2.8.0.
Add logs
Steps to reproduce
Expected behavior
Heroic shouldn't bypass the user's config file for Mangohud when MANGOHUD=1
Screenshots
No response
Heroic Version
Latest Stable
System Information
Additional information
Only with games from the Epic Store, no issue with games from GOG.
The text was updated successfully, but these errors were encountered: