Skip to content

Texture Quality presets write broken flags to ClientAppSettings.json and reset in-game settings #6517

Description

@latexfromchanged

I have...

  • I have read the instructions, and I didn't find a solution in any of the links above.
  • I am using the latest version of Bloxstrap.

Bloxstrap Version

v2.11.3

What problem did you encounter?

Hello! I would like to report an issue regarding the "Texture Quality" feature in Bloxstrap.

Bloxstrap forces internal flags into the file inside the Modifications folder. Because of this, Roblox is unable to read or save any local user configurations properly upon relaunch. Every single setting (camera sensitivity, Shift Lock Switch, volume, and graphic bars) completely resets back to zero/default on every launch.

Furthermore, when reopening Bloxstrap Settings, the UI visually bugs out and resets the Texture Quality dropdown menu back to "Automatic", hiding the fact that it locked the file with a hardcoded zero value.

If you open the configuration file, it looks exactly like this:

Visual proof of the bug inside ClientAppSettings.json:

{
  "DFFlagTextureQualityOverrideEnabled": "True",
  "DFIntTextureQualityOverride": 0
}

This specific hardcoded zero-value forces the Roblox engine to lock down the rendering profile, which completely prevents the client from syncing and saving user configurations upon exit.

P.S.
Because of all these changes and blocks from the new Roblox client updates, custom graphic settings are completely dead now. Rest in peace, custom graphics 🥀

How do you reproduce the problem?

  1. Open Bloxstrap Settings ➔ Engine Settings.
  2. Change "Texture Quality" to any manual level (for example, Minimum / level 0) and click Save.
  3. Launch Roblox and try to change camera sensitivity, Shift Lock, or graphic sliders inside the in-game menu (Esc ➔ Settings).
  4. Leave the game properly and relaunch it.

Bloxstrap Log

N/A

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions