Since the patch has hit, my max foreground fps toggle becomes unchecked. At first I thought it was because of an addon, but this also happens when I turn them all off.
7 Likes
Can confirm that Iām also experiencing this issue. Iāve tried running console commands and launching the game with a command line argument with no luck.
hey there, iām having the same issue after the patch. this has never happened before. keep me posted if you find a solution. itās annoying having to go in every time i log to check it off againā¦
Can confirm this happens as well.
This is also happening to me. I have to reapply it every time I launch the game.
Yes sir, can confirm as well.
Not a huge issue, but i like having my game to be locked at 62 to keep my gpu at 60c and the frametimes stable.
1 Like
so who do we contact to have this issue fixed?
There was a change made by Blizzard in the most recent patch to allow addons to write cache data to the Config.wtf
The problem is that if an addon writes more than 1103 characters to the config, it starts to affect the formatting of SET variables, such that they start overwriting cvars.
A good example is Details Damage Meter, for me it causes the SET useMaxFPS ā1ā to be removed after relaunching the game which means that the in-game fps cap is removed and the frame rate goes into the 400s which causes the fans to ramp.
TLDR: try disabling addons, re-enable Max foreground fps, restart the game and it should now stay correctly.
This doesnāt fix the issue for me. Iāve disabled all Addons and the max FPS still doesnāt āstickā. I exit the game so it āsavesā I turn it back on and my addons on and my FPS is back at uncapped. This is something blizzard needs to solve.
I run -very- minimal addons, at a time 5-6. (WA, DBM, Omni CC, Threatplates , RC lootcouncil and MRT)- all of which are required for my raiding at the time of posting this.
I shouldnāt have to ārememberā to cap my FSP every time I log into the game.
1 Like
I was having the same problem, the max FPS setting wouldnāt stick in the Wow video settings, causing my video card to overheat and my fans to spin up to high volume levels. I did find a work around, there is a setting in the nVidia configuration utility to set the max FPS. It should be noted that this will set it for all applications, not just WoW.
To change the setting in the nVidia control panel, click on the ^ on the lower right hand side of the the windows desktop toolbar, then click on the green nVidia logo. Once inside the control panel, find the āManage 3d Settingsā option on the left side of the screen, locate the āMax Frame Rateā option on the right hand side, then set it to the desired level (I set mine to 30). The setting can be changed by using the slide bar or typing it in manually.
Good luck!
2 Likes
This will indeed correct that issue, however it is only masking the effect. The underlying issue is an addon writing over the in-game fps limiter that the game sets in the WoW config.wtf file.
And when add-ons are required to play, itās not fixing the issue.
1 Like
This needs fixing immediately. Same addons as before, nothing changed but the patch
I am also experiencing this issue.
Yea
i can confirm as well
This is also happening to me
Itās the same issue thatās causing Gamma to reset for some people, as well as Ambient Sound Volume or any other setting. To quote myself:
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.
1 Like