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

"Sliders" setting UI element not working properly in SteamVR mode #280

Open
Azzurite opened this issue Jun 28, 2022 · 3 comments
Open

"Sliders" setting UI element not working properly in SteamVR mode #280

Azzurite opened this issue Jun 28, 2022 · 3 comments

Comments

@Azzurite
Copy link

Subnautica 1 (not below zero), when in SteamVR mode. Does not happen on the flatscreen version, only in SteamVR.

When going into the game options, straight to the "Mods" tab, all sliders will be set to the "middle" position, even if the backing setting properties have a different value. This happens with any mod that uses a "Slider" setting property. No matter what value you set the sliders to, these values will not be saved - only the default value.

If you first go to any of the standard game settings tabs like "General" and change any setting there, and only afterwards go to the "Mods" tab, then some sliders will have their correct positions according to their backing settings, some don't. If you then change these sliders, they are saved properly. So this only happens on SteamVR and if you go straight to the "Mods" tab, not in any other case.

Tested with Subnautica Dec-2021 68598; QMod 4.4.3 from Nexus, and these mods (all of which have sliders but none work in the above cases) Base Clocks, Day/Night Speed, Persistent Reapers

Here is a log where the sliders got reset:
qmodmanager_log-Subnautica.txt

These were the settings before:
config - before.json.txt
and these were the settings after:
config.json.txt

@Azzurite
Copy link
Author

I can do any debugging necessary, am a progammer myself.

Luckily if you don't go to the settings menu the configs work, so that's a decent workaround for now :D

@Metious
Copy link
Member

Metious commented Jun 28, 2022

@toebeann @MrPurple6411 Take a look at this when you guys can.

@Azzurite
Copy link
Author

Also I downgraded to 4.3.0 to test if it still happened there, which it did. The log I attached is from that version still, forgot to switch back. I can provide a new one with 4.4.3 but I don't think the logs are saying much in this instance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants