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

Set -res in cmdline_fso.cfg #123

Closed

Conversation

niffiwan
Copy link
Member

@niffiwan niffiwan commented Nov 5, 2015

This worksaround recently reported issues with users being unable to
write to the Windows registry, even when running as an administrator.
Setting -res should be foolproof, although it leaves other settings out
like audio.

Also, this could be considered a massive hack, and it's my first time digging into wxlauncher. Please let me know if there's a better way...

This worksaround recently reported issues with users being unable to
write to the Windows registry, even when running as an administrator.
Setting -res should be foolproof, although it leaves other settings out
like audio.
@niffiwan
Copy link
Member Author

niffiwan commented Nov 6, 2015

Hmm... maybe this is better fixed by solving #113?

@IssMneur
Copy link
Member

IssMneur commented Nov 6, 2015

Yeah #113 would help but the recent issue of not being able to set the screen resolution was because of a bug in wxLanucher 0.10.0 where we were writing to the incorrect key. This was fixed in 0.10.1.

This patch does not address the other, less obvious, settings that are stored in the registry like joystick selection, which as far as I know is not something that can be set on the command line.

See https://github.com/scp-fs2open/wxLauncher/wiki/FS2-Open-Launcher-Communication for more seeing that only the registry configures. To be fair, some of which are not that important.

@MageKing17
Copy link
Member

More annoying is that once we move to a configuration file on all platforms, this would just be yet more commandline clutter that should be removed.

@niffiwan
Copy link
Member Author

niffiwan commented Nov 7, 2015

yeah - given that the original issue seems like it should have been resolved with an upgrade to 0.10.1 I'm going to close this one.

@niffiwan niffiwan closed this Nov 7, 2015
@niffiwan niffiwan deleted the feature/res_via_custom_flag branch November 7, 2015 01:28
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

Successfully merging this pull request may close these issues.

3 participants