You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, MangoHUD seems to detect a game's name by its executable name. In the case of WINE/Proton running Unreal Engine games, it may be that the game EXE is creatively named Client-Win64-Shipping.exe. When MangoHUD creates log files, they are then named based on this value.
Feature Request
Is it possible for MangoHUD to provide a way to override the exe name, so that instead of the log files having an auto-detected name, one could provide an alternate name via environment variables?
Why is this important?
It isn't
what
This is purely a "creature comfort" / user experience optimization. It would also be practical when auto-uploading logs to the Flightless Network, as the upload would be properly identified.
The text was updated successfully, but these errors were encountered:
"Issue"
Right now, MangoHUD seems to detect a game's name by its executable name. In the case of WINE/Proton running Unreal Engine games, it may be that the game EXE is creatively named
Client-Win64-Shipping.exe
. When MangoHUD creates log files, they are then named based on this value.Feature Request
Is it possible for MangoHUD to provide a way to override the exe name, so that instead of the log files having an auto-detected name, one could provide an alternate name via environment variables?
Why is this important?
It isn't
what
This is purely a "creature comfort" / user experience optimization. It would also be practical when auto-uploading logs to the Flightless Network, as the upload would be properly identified.
The text was updated successfully, but these errors were encountered: