Exiting vehicles kill my Hotkeys...
This may have been addressed. Everytime I leave a vehicle ie. Drake, Siege Engin and enter combat my action bar with all my hotkeys does not work. Infact upon pressing 1, 2 the pet bar buttons indicate. Typing /rl fixes the issue, but you really can't do that in the middle of Ulduar. Flame Levithain waits for no one. :D
Thanks |
Hmm, not noticed that myself. Although I haven't tried since the latest update so I will do tonight.
Before the last 2 updates however I could do the icecrown quests without reloading the UI. I could hop on the harpoon guns and use them. Hop on a dragon and burn some buildings and then carry on using my action buttons as normal for the other dailies there. |
Let me know what you find out Xrystal.
LechonKawali -- what other mods do you have installed? |
Sure, but it just occurred to me that most of the time I use the mouse to click on the action buttons but I'll try both ways as I know in the past I have used the bound keys before with no problems. I just can't remember if that ever happened after being on a vehicle of some sort.
|
Here is the list as of last night when I logged.
FuBar-compat-1.2: disabled Atlas_Entrances: disabled Atlas_FlightPaths: disabled Auc-Advanced: enabled Auc-Filter-Basic: enabled Auc-Stat-Classic: enabled Auc-ScanData: enabled Auc-Stat-Histogram: enabled Auc-Stat-Purchased: enabled Auc-Stat-iLevel: enabled Auc-Stat-Simple: enabled Auc-Stat-StdDev: enabled BeanCounter: disabled FB_TrackingFrame: enabled FB_OutfitDisplayFrame: enabled FishingBuddy: enabled FB_MergeDatabase: enabled nUI_ThinBlack: disabled AtlasLootFu: enabled AtlasLoot_WrathoftheLichKing: enabled AtlasLoot_WorldEvents: enabled AtlasLoot_OriginalWoW: enabled AtlasLoot_Crafting: enabled AtlasLoot_BurningCrusade: enabled AtlasLoot: enabled Atlas_OutdoorRaids: enabled Atlas_DungeonLocs: enabled Atlas_Battlegrounds: disabled Atlas: enabled FuBar_BattlegroundFu: disabled FuBar_FishingBuddyFu: enabled FuBar_SpeedFu: enabled FuBar: enabled FuBar_MoneyFu: enabled FuBar_MailFu: enabled FuBar_LocationFu: enabled FuBar_ExperienceFu: disabled FuBar_ClockFu: enabled Atlas_Transportation: disabled ChatMOD: enabled PassLoot: disabled Stubby: enabled ArkInventory: enabled Postal: enabled nUI: enabled Outfitter: enabled !Swatter: disabled nUI_Transparent_Console: enabled MobInfo3: disabled FuTextures: enabled GrinderCore2: disabled FactionGrinder2: disabled Enchantrix: enabled Enchantrix-Barker: enabled EnhTooltip: enabled EMLib: disabled RareFinder: disabled FuBar_PetInfoFu: disabled QuestHelper: disabled SlideBar: disabled FuBar_VoiceFu: disabled Bejeweled: disabled FB_InfoBar: disabled FuBar_DurabilityFu: enabled FuBar_PerformanceFu: enabled FuBar_QuestsFu: disabled Informant: enabled ItemPriceTooltip: enabled Looter: disabled MobInfo2: enabled nUI_AuraButtons: enabled Omen: enabled PricePer: enabled RatingBuster: enabled Recount: enabled sct: enabled sct_options: enabled sctd: enabled sctd_options: enabled FB_Titan: disabled DBM-Core: enabled DBM-GUI: enabled DBM-Battlegrounds: enabled DBM-ChamberOfAspects: enabled DBM-EyeOfEternity: enabled DBM-Naxx: enabled DBM-Party-WotLK: enabled DBM-Ulduar: enabled Rebuilt: enabled Gatherer: enabled Gatherer_HUD: enabled Peggle: disabled |
Okay had my mage do her Icecrown dailies with the latest Dev version after todays patch so here goes ..
1. Used keys to attack a few mobs for the stabbing quest. 2. Jumped on a dragon and used keys to breathe fire on buildings for that quest. 3. Left vehicle and proceeded to use keys to attack a few more mobs for stabbing quest. 4. Hopped on a harpoon and used keys to shoot dragons and their riders down. 5. Left vehicle and finished off stabbing quest with more key bashing. Didn't see any problems during that time. |
At first glance I don't see anything in your mod list that jumps out at me as a problem for the keybindings. I did notices that you have both MobInfo2 and MobInfo3 installed and kinda wondering what that's about.
My recommendation would be to do a clean install of nUI and for testing purposes, run some vehicle oriented quests/instances with only nUI enabled and see if you still have a key binding issue or not. I strongly suspect you won't if you do the clean install. Instructions are here... http://www.wowinterface.com/forums/s...ad.php?t=21716 |
Well alas that did not fix my bug. I did remove mobinfo2 and 3. Now I am playing a DK w/ perma ghoul. I have not yet had the chance to test without my ghoul away vice out. Gonna try a few more times in WG and Ulduar. :confused:
|
Hmm maybe its a death knight specific problem .. or .. erm .. anything with a permanent pet. Pity my warlock isn't 80 yet to test with her.
|
Well I tested it with all, none, and just nUI turned on. The results are that with no mods loaded no issues, with just the core+ loaded hotkeys fail (keybinds not on the hotbar are not affected). I have also tested this with ghoul in and out, the ghoul has no effect. :confused:
|
very strange .. and did you check that your bindings were cleared .. did I read they were now stored online somewhere ?
I did a vehicle quest with my warlock as well today and had no problems. Using 1 to 5 on my warlock bar and 1 to 3 on my pet bar worked fine after using a vehicle in Dragonblight. So at a loss as to why you are having problems. Although I don't change the default bindings so whether thats the initial step to this going wrong is the next thing to find out. |
Quote:
|
Ah thats what I thought. So, if keybindings were changed then clearing out your wtf files won't change them. You would have to manually change them.
|
You got it. One thing I noticed when I first started using nUI was even though my keybindings had been set prior, nUI did not recognize them. So for example, the default action bar, 1 to = did not show as bound. If I moused over them, the tooltip would only show how to bind them.
This did conflict with vehicles, or so I found out on my Hunter. Without the numbers being shown on the main action bar, just solo grinding, everything worked fine. But, I did the Wyrmrest daily at the temple, and found out real quick they weren't working. I had to manually rebind them so that nUI would show they were bound, after that I have had no issues. TL : DR Version: Manually rebind all the buttons you want how you want them and see if that fixes it. |
Hmm, then that is strange. I have never once bound my main action buttons and I don't recall binding any others either. But, I am not getting any problems and I get that key binding info popup like you mentioned. Go figure.
|
Yeah... I'm completely miffed by this one.
nUI reads the key bindings on all of your Bliz action bars when you log in and assigns those keys to nUI's action bars. It does *nothing* else with key binding until you exit *unless* you change the key bindings manually using either the ctrl-alt-right-click or the interface key binding menu. The main action bar always (to the best of my knowledge) uses the same key bindings regardless of which page you are one (1-6) or the special pages (7-10) used for vehicles, stances, forms, possession, etc... that's the whole point of the main action bar. So why the key binding would change just because the bar page changed from page 1 to the vehicle/possess page is a complete mystery to me. |
2 Attachment(s)
In my case at least, nUI didn't see that they were bound, even though they were. So my guess is just a glitch somehow. It was easy enough to rebind them from nUI so that I was able to see all hot key assignments on the buttons themselves. I'll see if I can dig up an old screen shot from before I rebound them.
***EDIT*** Screenshot's uploaded. The first is from before I rebound the keys, the 2nd is obviously after :) |
All times are GMT -6. The time now is 10:00 PM. |
vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI