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

Bug: SC2 Graphical settings aren't saving; Settings aren't inherited from the install #3531

Open
Slimurgical opened this issue Jun 14, 2024 · 1 comment
Labels
is: bug/fix Issues that are reporting bugs or pull requests that are fixing bugs.

Comments

@Slimurgical
Copy link

What happened?

When starting a mission, the game does not inherit settings values from Variables.txt in the Starcraft 2 documents folder, and it does not retain any changes to the Window state. You can change it however is wanted and it will revert to windowstate=1 aka Fullscreen (Windowed). This requires any player who requires Windowed mode to have to change the state upon beginning a mission. Other settings are saved, namely Hotkey profiles, but graphical setting changes are not.
Note: If this is intended functionality (don't know why it would be) I would at the least like to know what file Archipelago pulls config details from with Starcraft 2.

What were the expected results?

When the game is started, it retains any and all values set in Variables.txt as well as changing them when changes are made, even if Archipelago is creating its own config file for the SC2 game window, the expected result is to not have it reset the window mode everytime the window opens, to instead have it save to whichever file Archipelago is pulling config details from. The expected result is that thep layer doesn't need to manually set it to windowed each time no matter the ease of the method one uses for it.

Software

While playing

@ScipioWright ScipioWright added the is: bug/fix Issues that are reporting bugs or pull requests that are fixing bugs. label Jul 31, 2024
@neocerber
Copy link
Contributor

@Ziktofel could you look into that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is: bug/fix Issues that are reporting bugs or pull requests that are fixing bugs.
Projects
None yet
Development

No branches or pull requests

3 participants