Slow HDD Mode keeps turning off

[Despair]

I already checked and other video settings do save, only the 'Slow HDD Mode' option keeps turning off when I quit the game and open. Any solutions?

[Etragorn]

Try running it as an administrator. Sometimes settings being saved has to do with the settings file being written to.

[Ironwu]

Well:

MINIMUM:
Requires a 64-bit processor and operating system
OS: Windows 10 64-bit
Processor: Intel I5 4690 / AMD FX 8350
Memory: 8 GB RAM
Graphics: Nvidia GTX 970 / RX 480 (4GB+ of VRAM)
DirectX: Version 11
Storage: 150 GB available space
Additional Notes: SSD required

Should have taken that seriously. SSD are very cheap now and don't need a huge one if all you want is a single game on it.

[talemore]

don't turn off the program. keep it in the background

[DragonMaster]

You can get a 1 TB SSD drive for around $50 or so I don't know what the problem is with up grading to one. I've got a 2 SSD drive for my games and don't have any issues with it at all.

[Angel]

back when I was using it it always turned off when I closed and re opened the game too, this seems like 'normal' behavior for it

[Ironwu]

Originally posted by Denky:

I already checked and other video settings do save, only the 'Slow HDD Mode' option keeps turning off when I quit the game and open. Any solutions?

Well the other thing you could do is go into Power Management and tell it to Never spin down the drive. But if you are running on batteries, that may be a problem.

[pyrrho]

Go here: C:\Users\<yourUserName>\AppData\Local\Larian Studios\Baldur's Gate 3
Edit this file: graphicSettings.lsx
Add a new XML node:

<node id="ConfigEntry">
<attribute id="MapKey" type="FixedString" value="SlowHDDMode"/>
<attribute id="Type" type="int32" value="0"/>
<attribute id="Value" type="int32" value="1"/>
</node>

Save file, load game.
It should stick now.

[Despair]

Originally posted by pyrrho:

Go here: C:\Users\<yourUserName>\AppData\Local\Larian Studios\Baldur's Gate 3
Edit this file: graphicSettings.lsx
Add a new XML node:

<node id="ConfigEntry">
<attribute id="MapKey" type="FixedString" value="SlowHDDMode"/>
<attribute id="Type" type="int32" value="0"/>
<attribute id="Value" type="int32" value="1"/>
</node>

Save file, load game.
It should stick now.

This worked. Thank you.

[Etragorn]

Originally posted by Denky:

Originally posted by pyrrho:

Go here: C:\Users\<yourUserName>\AppData\Local\Larian Studios\Baldur's Gate 3
Edit this file: graphicSettings.lsx
Add a new XML node:

<node id="ConfigEntry">
<attribute id="MapKey" type="FixedString" value="SlowHDDMode"/>
<attribute id="Type" type="int32" value="0"/>
<attribute id="Value" type="int32" value="1"/>
</node>

Save file, load game.
It should stick now.

This worked. Thank you.

Obviously, thought, it's a bug since you shouldn't have to manually edit a settings file to make a setting stick.

[pyrrho]

Obviously, though, since it is a bug I reported it using the Larian Bug Report page. I doubt Larian wants users to have to edit settings files either so hopefully it is included in one of the upcoming hot-fixes (which are prolific so far). Some may say that needing hot-fixes is a sign that a game is poorly designed, or irreparably flawed but I disagree with that notion and think that a healthy player base that really exposes some edge cases (or even simple oversights) that weren't caught in QA/Testing is a good thing -- especially considering that many of those reported bugs have been/attempted to be fixed.

[アンジェル]

Originally posted by pyrrho:

Obviously, though, since it is a bug I reported it using the Larian Bug Report page. I doubt Larian wants users to have to edit settings files either so hopefully it is included in one of the upcoming hot-fixes (which are prolific so far). Some may say that needing hot-fixes is a sign that a game is poorly designed, or irreparably flawed but I disagree with that notion and think that a healthy player base that really exposes some edge cases (or even simple oversights) that weren't caught in QA/Testing is a good thing -- especially considering that many of those reported bugs have been/attempted to be fixed.

^
This should be marked as answer in addition