Could post this on the beta forums but I see similar stuff in here.
Have a razer Tartarus and it works everywhere except in beta client.
I can’t bind or use SHIFT/CTRL etc, it’s like it is not recognised in beta
Normal keyboard works (It sits next to the Tartarus)
All other keys on the Tartarus work
Works on retail all day long
Works on other apps
Tried deleting WTF folder etc
I can even type totally fine in game, e.g. I can use the key bound to shift to type in the chatbox in WoW with uppercase and it works there.
It’s bound using steermouse
Haven’t ever done that terminal fix I see here because it’s scary looking and was a retail fix. But I could try it if people think it would work on beta.
Only and exclusively in beta client have I seen a problem.
So baffled by this. (It’s still me, replying on another toon)
I tried the terminal command meme thing that gets posted around, defaults write com.blizzard.worldofwarcraft disable-expose-fix -bool YES
No change and I never needed this on retail.
The fact I can type in uppercase with the shift modifier in the chat window, but once I click off back to character control, SHIFT+Q etc isn’t recognised, seems strange to me.
All my other apps work. I don’t want to spend too much time on it in case it’s something the actual devs need to fix with beta client.
14inch 2021 Macbook Pro M1 Max Sonoma 14.5
Should I post this on beta forums?
EDIT: Dude in another thread said his Tartarus is having the the exact same issue.
EDIT2:
I have found a work around and it’s weird.
If I bind a modifier with something else on the Tartarus it will work as a key.
So for example.
Key bound to SHIFT doesn’t work, this is the problem.
Key bound to SHIFT+K does work, it will push both SHIFT and K.
Weird right?
K is an empty keybind for me, so if I push this key bound to SHIFT+K and also a key bound to Q
I get SHIFT+K+Q in put into the game
Same as just SHIFT+Q, since K doesn’t do anything in game. So if you are having this problem rebind your SHIFT key to a SHIFT+empty keybind for the moment.
Same issues here lol. Crazy stuff, will try your workaround as sad as it has to be
I will be more specific, it doesn’t seem like any of these modifiers will work for me the one I need is CMD, and it won’t work unless I bind it with something else. But since I use it as a modifier I need it to work as it does in retail, just as that without anything else so I can have the most benefit.
Also for some reason shift-mouswheeldown binds to shift-mousewheelup and only in the MAC, not in other areas or in retail. Weird for sure lol.
I’m not sure if it’s still in more recent versions of the WoW client, but there was at some point a “Disable OS shortcuts” option in WoW’s preferences settings. If it’s still present, it might be possible you have this enabled in TWW but not on retail.
Also, the usual tidbit about adding WoW to the various whitelists for the Security and Privacy prefpane sections applies as it is separate from the classic and retail clients, so check there as well. But given you can macro just fine on the Tartarus but not use the OS modifier keys, the first part above seems the more likely culprit.
The issues are still persisting with the recent updates and the TWW option is not the cause as the setting is the same on both instances of the client.
Never had to do the second paragraph above on my Mac on retail though I do use karabiner and steermouse; but that shouldn’t be impacting the binds upon entry into the beta client any differently than the retail one.
Also, this isn’t a Tartarus issue but it seems like anything being remapped to something outside of the norm as I am using a g600 with an extra gshift button to map ALT/CMD. (Though, I have tested the button with SHIFT, etc and it does the same issue.)
The other thing that is broken from retail - beta is for whatever reason shift-mousewheeldown is also mapping to shift-mousewheelup no matter what I do. The other modiers work fine including the “real” shift-mousewheelup.
Hopefully they pay attention to the bug reports and forums as this is a bit of a pain
I actually consider this a minor issue in some ways since Tartarus isn’t directly supported on Mac but its such an odd bug and I thought it might affect other accessories too. Plus I like my Tartarus. Thank you.
For me it’s a big part of the game since I modify the gshift to OPT/ALT so it eliminates a good chunk of binds along with shift-mouswheeldown not working. Hope it gets rectified.
the bug actually affected many more things than just this. this just happened to be related to several more pressing bugs such as not being able to use shift mouse wheel down or not being able to interact with the game AT ALL due to command key getting stuck. Fixing all of those issues were down to one root cause with modifier keys
Is yours fixed yet I am on 11.0.0.552588 and do not see it fixed or any difference in the modifier issue? I have had a few small updates but no changes.
Tested the new build that just went up and no changes, shift-mousewheeldown no functioning still as well as no update to my gshift (Logi g600) assigned to OPT/ALT still just producing as if no modifier was pressed.
Yeah that build doesn’t seem to have fixes yet. Often times the public build is a week behind from internal. So even when he says “hopefully next build” sometimes it’s not til the one after next.
Seems like this build has fixed the OPT key not being recognized in game as ALT when combined with other keys so now can bind all of those with my GSHIFT button assigned to it
Unfortunately “shift mousewheeldown” seems to still be recognized as shift-mousewheelup. Hope that one gets fixed soon too.
my tab and space bar doesn’t work now, or let me key bind. either with my MacBook Pro 2’s keyboard or apple’s Magic Keyboard, just out of the blue yesterday. I’ve went through the UI reset process, per some older posts and nothing fixed it. I have to key bind my jump to another key, which is difficult to get used to.
