Gamma setting is reset each logout since 10.0.7

Support Bug Report
23

Same here, since 10.0.7 it keeps resetting

24

Same problem with Radeon RX 6600 on a Mac. My workaround is to increase the brightness instead of the gamma. The brightness setting does stick after log out.

25

Adding my voice to the crowd. It just started with 10.0.7 for me also, always resetting to 1 from my 1.3 setting.

26

I found this and tried it, is working so far.

  1. Log in and correct your settings
  2. Type the following command into the in game chat box: /console synchronizeSettings 1
  3. Press Enter
  4. Log out of the character using the ESC command and choosing Log out

(This worked for the day, but stopped working once I shut the computer down.)

1 Like
27

this did nothing, you are just logging out, issue happens when you exit the game. Tried /console synchronizeSettings 1…enter esc exit game …came back gamma was reset to 1

28

Same issue here! 8 days without a fix?

1 Like
29

same here with a rtx 2060 super only on 1 of my accounts though. when logging into the other it functions normally

30

This is a combination of addons and a change made to the Blizzard UI system with 10.0.0.7. Details! in particular is known to cause it (via the LibOpenRaid library) but others could well be doing the same.

You can find more details about it here: https://github.com/Tercioo/Details-Damage-Meter/issues/479

The short is that addons can now write their own CVARs to the main config file (config.wtf), but it isn’t gracefully handling extremely long values. This in turn results in some lines being invalidated, causing the client to use default settings for those variables when next you reload.

3 Likes
31

Asterchades is probably right.
I just noticed that if I set my gamma at the login screen, without loggin on a character, then exit the game, the gamma stays where I set it.
If i log on a character and exit the game the gamma reverts back to where I don’t want it.
That seem to me to indicate an addon issue. At some point I will go thru my addons to figure out which one(s) is/are to blame. But I am just too dang lazy to do it today.

edit. It is Details Damage meter as indicated in the above post.
Tercioo is usually great at fixing things like this. I hope he reads that post.

32

I don’t use Details, so there’s more than one culprit.

33

I installed the newest Alpha version of Details and that fixed the issue for me! It sounds like there could be other addons causing this, but this seems to be the culprit in my case. Thanks for posting about that.

1 Like
34

Per the link I provided, any addon which creates a new CVAR (“RegisterCVar” and “SetCVar” codes in the LUA) is potentially doing it. Not all of them, though - it requires a particularly long value to be assigned, potentially over 1,104 characters. Details! just happens to be the most likely as it’s known to use such lengthy variables. From my own addons I know that ThreatPlates also uses it but seems to be better behaved.

For Windows users you can check for that command in all of your addons by opening a command prompt or terminal in your Warcraft directory and typing the following:
findstr /s /i /c:RegisterCVar * .*

Note that unfortunately due to a limit of the WoW forums I’ve had to insert a space after the first asterisk, otherwise it will only acknowledge the dot. If you’re copy/pasting that command it won’t work unless you remove that space

Other operating systems will require commands I’m unfamiliar with to search.

35

This fixed the ambient issue resetting to 60% everytime i log in.
I’ll check if the NPC dialogues are working in dungeons.

Nope, can’t hear npc dialogus.