I'm missing an entire options section?

I have no Options->Gameplay->Controls section. Does anyone else have this problem?

I’ve deleted all addons, deleted WTF/Interface folders, scanned and repaired my game. I also completely reinstalled the game. No luck on any of that.

I also submitted a help ticket, but the wait time is 28 days.

So you’re not showing it at all where it loads into? When you click Options, it automatically brings you to this screen. But you’re not seeing it?

1 Like

Missing that, yeah. I can’t post a picture unfortunately since my trust level isn’t at 3.

https:// i.imgur[dot]com/eYzT0WT.png

o.O Alrighty, yeah. It’s definitely not there. (posting screenshot for anyone else tripping in here.)

The first thing I would suggest trying is a UI reset? I know you said you disabled add-ons, but it’s a bit more than that.

5 Likes

You mentioned the WTF and Interface folders, but did you also delete your Cache folder during the UI reset?

I’d try the default UI by following the directions in the link Leilleath provided, then we can go from there.

5 Likes

I have deleted that folder, yeah. Reinstalled the entire game actually. No luck :frowning:

I know that sometimes it takes a couple to a few UI resets for it to finally take. This really does sound like a classic display issue, I would give the UI reset a couple more tries. As well as resetting the computer after each one.

2 Likes

I just /reloaded ~10 times, no luck either. I’ve restarted my machine multiple times over the weeks that I’ve been dealing with it, unfortunately

One of my rules of thumb when dealing with WoW is to run every thing as Windows Administrator, including file Renames/Deletes.

Seemed to clear up a lot of file-based issues so I made it a standard practice.

2 Likes

I just ran wow.exe as an administrator, but no luck.

@Vrakthris, I’ve followed the “Resetting the WoW User Interface” multiple times, no luck either :frowning:

Maybe run the scan and repair tool?

1 Like

Might be a good idea if you haven’t tried it yet. I am not seeing any other reports and I haven’t been able to reproduce it myself. :frowning:

2 Likes

Just to be clear, you renamed or deleted the three folders as instructed, then completely restarted your computer, the launcher, and then the client…without moving the old files back, right?

And then on a completely fresh, default UI, you’re still not seeing the menu option?

2 Likes

Just an extra bit since no one has mentioned it… make sure you don’t have any addon managers running that might auto-launch at Windows start and auto-update WoW addons, thereby re-installing the corruption.

Most of these addon managers like to default to just that: auto-start at boot and auto-update everything. If you use one and never changed options, it’s likely doing just this.

If this is the case, either change their options so that they don’t auto-launch or auto-update, or temporarily uninstall the manager.

Good luck!

3 Likes

Thanks for the bump guys. I wasn’t able to post an update until someone else posted after me. I ended up figuring out the issue on my own. I’ll run through the steps in case it might be of help to anyone else.

Given the stubbornness of the error, I figured it had to be an account-level issue. It was my suspicion that if the account level settings for the Control section were invalid, it might just error silently and hide the section altogether.

I found some error logs in my WoW/Errors folder that confirm this:

[C]: in function 'error'
Interface/SharedXML/Settings/Blizzard_Setting.lua: in function 'SetValueInternal'
...
<ErrorDescription> Script exception: Interface/SharedXML/Settings/Blizzard_Setting.lua:221: SetValue 'Mouse Look Speed' requires 'number' type, not 'nil' type.
Locals: (*temporary) = "SetValue 'Mouse Look Speed' requires 'number' type, not 'nil' type."

Seems like the latest update involved some changes to the settings, and whatever Mouse Look Speed value I had saved in storage was invalid. If a CS tech / engineer is reading this, it’s probably due to the fact that I set my mouse sensitivity with /console commands prior to the DF update.

The solution was to reset all my CVARs using the following command
/console cvar_default
This command should probably be suggested in the troubleshooting articles, since I didn’t see it there.

After a relog, the freshly reset cvar is successfully parsed and with no errors, the control section appears.

10 Likes

The Support Forum Agents in this forum are primarily information desk support mostly for billing and issues with accounts. They have no contact with Devs and Devs do not come here for feedback and suggestions.

I would suggest posting this info in the QA forum so QA can test the problem, and your solution, and then pass along the results to the Devs.
The Support article updates would then come from the Dev team.

P.S. Nice bit of trouble shooting. :slight_smile:

6 Likes

Check advanced troubleshooting on the article you were linked

It specifies to use that console command as its the next step if a basic reset doesnt fix the problem.

3 Likes