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

Add GAMEMODE_CONFIG environment variable to specifiy gamemode.ini location #491

Open
CyberCois opened this issue Aug 14, 2024 · 1 comment

Comments

@CyberCois
Copy link

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I find it difficult to make per game configurations. Ex. gamemode.ini with a custom script for 4:3 stretched resolution for CS2, but a different custom script for other games. This would also help with organization of config files.

Describe the solution you'd like
A clear and concise description of what you want to happen.
GAMEMODE_CONFIG environment variable should take precedence over all other config file locations. The would allow for steam launch options such as: GAMEMODE_CONFIG=~/.config/gamemode/gamemode-callofduty.ini gamemoderun %command%

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Trying to find $PWD and put the config file in that location for steam games.

Additional context
Add any other context or screenshots about the feature request here.

@mdiluz
Copy link
Contributor

mdiluz commented Aug 14, 2024

Unfortunately this doesn't quite work in the current logic, even if code were implemented to pass the config over the dbus connection to the daemon - in particular because gamemode is itself a "global" on or off mode, I don't think there'd be a way to selectively activate certain settings like that.

Unless the code has changed since I wrote it! Perhaps it could be possible now in some form.

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

2 participants