[11:50:19] [string "UIErrorsFrame:Clear"]:1: function arguments expected near '<eof>'
[C]: ?
[C]: in function `RunScript'
Interface\FrameXML\ChatFrame.lua:1879: in function `?'
Interface\FrameXML\ChatFrame.lua:3505: in function <Interface\FrameXML\ChatFrame.lua:3458>
[C]: in function `ChatEdit_ParseText'
Interface\FrameXML\ChatFrame.lua:3176: in function `ChatEdit_SendText'
Interface\FrameXML\ChatFrame.lua:2274: in function <Interface\FrameXML\ChatFrame.lua:2267>
[C]: in function `UseAction'
Interface\FrameXML\SecureTemplates.lua:277: in function `handler'
Interface\FrameXML\SecureTemplates.lua:487: in function <Interface\FrameXML\SecureTemplates.lua:445>
I have Prat3.0 r366 and Omen3 v3.0.8-2-g32a9369.
I mentioned Omen because after installing the missing dependency - LibSink, that's when the error above showed up and it just keeps going everytime there are chats showing up.
That's my problem, I don't know which one, is it a conflict between Prat3 and Omen3? Or is it with LibSink?? Or something else altogether?
1) Equipment Manager - anything else other than CrossDresser and Equipsetupdater that will put Blizzard's implementation close to ClosetGnome? (since CG was the one I used prior to EquipMan of Blizzard's)
2) Blizzard's QuestLog - I can't seem to find any quest related addons that builds on top of Blizzard's QuestLog implementation. I used to use nQuestLog but as I read today, it won't be maintained anymore. Anyone who have suggestions for an addon that builds on top of Blizzard's?? (For example, extending the number of quests tracked, auto collapse and expands, questminion background color, etc.)
Thanks!!
I decided once 3.2 comes, I'm going to switch to the default implementation of Blizzard; and secondly switch to addons that builds on top of Blizzard's implementation.
(PS. By any chance, will ClosetGnome be changed to be an addon on top of Blizzard's? Similar to how GroupCalendar is today?)
(PS2. Blizzard, LOL. You should just hire these great AddOn developers, it is obvious anyway to whom you got your recent new features :p Or at least include them in the credits "Inspiration:")
Blizzard default UI adds quest objective info in mob tooltips. I can't remember how it is enabled or disabled (or even if it could be disabled).
Oh! So that's what it is. I haven't noticed when they added that feature (or maybe the previous tooltip addon I was using was blocking the default mob tooltip or something).
Definitely looks like some kind of mount addons debug messages
Assuming not too many people are hooking AddMessage, and the message is being added to the DEFAULT_CHAT_FRAME, then the attached mod will print out the sent message followed by what sent it (which will be a couple of lines long).
When the spam gets shown again can you please take a screenshot of the output, the text will be in blue.
Hope I explained this well enough.
Cool thanks!
I edited it to check chatframe #3, since that's where the texts are showing.
[b]When I close Cartographer I get this:[/b]
Interface\AddOns\Test\test.lua:23: in function <Interface\AddOns\Test\test.lua:22>
[C]: in function `AddMessage'
Interface\AddOns\Prat-3.0\modules\Timestamps.lua:524: in function <Interface\AddOns\Prat-3.0\modules\Timestamps.lua:520>
(tail call): ?
Interface\AddOns\Prat-3.0\addon\addon.lua:623: in function <Interface\AddOns\Prat-3.0\addon\addon.lua:616>
(tail call): ?
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:521: in function `Debug'
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4917: in function `CheckBuffs'
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4693: in function `GrabBattlegroundGivers'
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4506: in function <...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4493>
[C]: ?
Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:298: in function `TriggerEvent'
...
[C]: in function `Show'
Interface\AddOns\MobMap\Astrolabe.lua:957: in function `AllWorldMapsHidden'
Interface\AddOns\MobMap\AstrolabeMapMonitor.lua:168: in function `Update'
Interface\AddOns\MobMap\AstrolabeMapMonitor.lua:99: in function <Interface\AddOns\MobMap\AstrolabeMapMonitor.lua:97>
[C]: ?
[C]: in function `Hide'
Interface\FrameXML\UIParent.lua:1908: in function `HideUIPanel'
Interface\FrameXML\UIParent.lua:1881: in function <Interface\FrameXML\UIParent.lua:1879>
[C]: in function `ToggleFrame'
[string "TOGGLEWORLDMAP"]:1: in function <[string "TOGGLEWORLDMAP"]:1>
Interface\AddOns\Test\test.lua:23: in function <Interface\AddOns\Test\test.lua:22>
[C]: in function `AddMessage'
Interface\AddOns\Prat-3.0\modules\Timestamps.lua:524: in function <Interface\AddOns\Prat-3.0\modules\Timestamps.lua:520>
(tail call): ?
Interface\AddOns\Prat-3.0\addon\addon.lua:623: in function <Interface\AddOns\Prat-3.0\addon\addon.lua:616>
(tail call): ?
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:521: in function `Debug'
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4917: in function `CheckBuffs'
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4693: in function `GrabBattlegroundGivers'
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4506: in function <...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4493>
[C]: ?
Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:298: in function `TriggerEvent'
...
[C]: in function `Show'
Interface\AddOns\MobMap\Astrolabe.lua:957: in function `AllWorldMapsHidden'
Interface\AddOns\MobMap\AstrolabeMapMonitor.lua:168: in function `Update'
Interface\AddOns\MobMap\AstrolabeMapMonitor.lua:99: in function <Interface\AddOns\MobMap\AstrolabeMapMonitor.lua:97>
[C]: ?
[C]: in function `Hide'
Interface\FrameXML\UIParent.lua:1908: in function `HideUIPanel'
Interface\FrameXML\UIParent.lua:1881: in function <Interface\FrameXML\UIParent.lua:1879>
[C]: in function `ToggleFrame'
[string "TOGGLEWORLDMAP"]:1: in function <[string "TOGGLEWORLDMAP"]:1>
[b]When I zone-in to another zone, I get this:[/b]
Interface\AddOns\Test\test.lua:23: in function <Interface\AddOns\Test\test.lua:22>
[C]: in function `AddMessage'
Interface\AddOns\Prat-3.0\modules\Timestamps.lua:524: in function <Interface\AddOns\Prat-3.0\modules\Timestamps.lua:520>
(tail call): ?
Interface\AddOns\Prat-3.0\addon\addon.lua:623: in function <Interface\AddOns\Prat-3.0\addon\addon.lua:616>
(tail call): ?
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:521: in function `Debug'
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4917: in function `CheckBuffs'
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4693: in function <...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4689>
[C]: ?
Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:298: in function `TriggerEvent'
Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:372: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:345>
Interface\AddOns\Test\test.lua:23: in function <Interface\AddOns\Test\test.lua:22>
[C]: in function `AddMessage'
Interface\AddOns\Prat-3.0\modules\Timestamps.lua:524: in function <Interface\AddOns\Prat-3.0\modules\Timestamps.lua:520>
(tail call): ?
Interface\AddOns\Prat-3.0\addon\addon.lua:623: in function <Interface\AddOns\Prat-3.0\addon\addon.lua:616>
(tail call): ?
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:521: in function `Debug'
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4917: in function `CheckBuffs'
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4693: in function <...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4689>
[C]: ?
Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:298: in function `TriggerEvent'
Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:372: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:345>
I saw two addons from those two reports:
DailiesQuestTracker[/b]
AceEvent-2.0[/b]
I assumed it wasn't AceEvent-2.0 since it's part of the core if I'm not mistaken?? I turned off DQT = problem fixed.
Did I understand it correctly? If I did, then I'll file a report to DQT.
Additional info:
I have the MobMap settings related to quests already turned-off.
Checked Cartographer and CowTip - both a no.
Checked nQuestLog, not it either.
I also turned-off the Blizzard settings
Of the initial guessing, I can't think of any addon that has anything to do with quests. I hope I can avoid the bloody testing method :p Isolation (one addon at a time).
Your chat addon is Prat, but I bet you already know that. I noticed you don't have all the subfolders of Prat, enabled or not. Not sure what is causing the text dump, but it wouldn't hurt to make sure you have the newest version of your addons. If you use the Curse Client, I suggest clicking Manage Games, and setting the pulldown menu to Beta, applying to all addons, the seeing what needs updating.
Hmm, my CurseClient is setup to 'Alpha'. ^_^
Will try to do another round of tests and detection a few hours later.
EDIT:
Removed Prat comment... what I was thinking was Perl not Prat :p
I'm not sure if it's Cartographer 2, but everytime I close my World Map, the information shown in the screenshot shows up. But if I visit the settings of Carto2, I can't find anything pertaining to those texts.
I can't control it either, it isn't in WoW's chat window/menu option. For some reason, it chose to push those texts on my custom chat window and not on WoW's default (General/Combat Text).
I have quested to 80 with BT4. I have experienced no gameplay issues that are linked to BT4.
For http://www.wowhead.com/?quest=12953 you have to hit the roof of the buildings to get credit. This isn't a BT4 issue, but one of blizz quest design requiring one to hit a specific part of the building (not just any piece of it).
I did http://www.wowhead.com/?quest=13086 just today and it worked fine with BT4. If the dwagon is out of mana you need to devour someone else your buttons are unresponsive. Again, that's quest design and not an action bar issue.
But maybe I misunderstand what people report as problems for these quests.
Yep, you did misunderstand, as far as people having these issues are concerned, we read the quests, we read the vehicle skills, and we know how to do the quests. :p
As I have detailed in my reports, I tested it both with BT4 and without BT4. I call this issue "Vehicle Command-Lag", since that's where I ended up.
So to summarize:
1) Tested with BT4 and without BT4
2) Tested without any addons
3) Experienced the Vehicle Command-Lag on all setups (#1 and #2 above)
The "Vehicle Command-Lag" only occurs on, well, vehicles. All other game functions works fine. You can attack normally (if you are not on a vehicle), chat, walk, loot, interact with other quest objects, etc. But once you get on the vehicle, if you are unlucky, you get the VCL issue.
There seems to be some workaround which I forgot to mention.
a) Re-log
b) If it still doesn't work, go out of the zone then re-log
c) If it still doesn't work, do #2, but shut-down your client for 20 minutes
d) If all else fails, disable all your addons and hope the VCL doesn't kick-in
e) If it still fails, just get back to it later or try getting on a totally different vehicle to let the client and the server fix themselves.
All-in-all, I think this is out of BT4. If it happens without BT4 and without AddOns, then it is a Blizzard bug. Which explains why other BT4 users did not experience this issue. We were the unlucky ones :p
So cool, now to hope that Blizzard can duplicate this issue so they can start tracing what is causing the problem. IMO, the VCL seems to be random, however, there seems to be a list of vehicles where this occurs.
Other people are having problems, but I am not sure if they have Bartender4, so I did a test again.
Without Bartender4, it fires normally.
I also did button spamming and I noticed that there are 1 to 2 extra arrows showing up - graphics, with the "real" arrow among them.
The fake arrows will disappear half-way through.
With Bartender4, it now fires normally.
The difference, there are twice extra arrows this time, so 3 to 4 fake arrows graphics showing up on the screen if you are spamming the button.
From what I can tell, it seems to be on Blizzard's end, unless it was being caused by other addons. The vehicle commands seems to be getting some command-lag with or without BT4. However, everything else is fine, no lag at all (ie if not on a vehicle).
Anyway, I may be wrong. I haven't turned-in the quest yet in case you need me to test it.
Other people are having problems, but I am not sure if they have Bartender4, so I did a test again.
Without Bartender4, it fires normally.
I also did button spamming and I noticed that there are 1 to 2 extra arrows showing up - graphics, with the "real" arrow among them.
The fake arrows will disappear half-way through.
With Bartender4, it now fires normally.
The difference, there are twice extra arrows this time, so 3 to 4 fake arrows graphics showing up on the screen if you are spamming the button.
From what I can tell, it seems to be on Blizzard's end, unless it was being caused by other addons. The vehicle commands seems to be getting some command-lag with or without BT4. However, everything else is fine, no lag at all (ie if not on a vehicle).
Anyway, I may be wrong. I haven't turned-in the quest yet in case you need me to test it.
Ok i pushed another Alpha just now (4.2.0-3) which contains some changes to how the buttons work. Please try it and tell me if you still get the errors.
I'll try that. Going to ding to 77, then I'll enter Wintergrasp. I reverted back to the BT4 version where I first encountered it and see if I'll experience it in Wintergrasp vehicles.
If I do, then I'll switch to the latest Alpha and test.
Btw, yesterday, I tried it with the Dragon vehicle in Dragonblight (using the old version) but I didn't encounter problems (I'm not sure if it has to do with it 'flying' :p ).
Will reply as soon as I tested it in Wintergrasp, old and the latest Alpha. (I really need to find a vehicle where I'll encounter it again... )
I'm in Wintergrasp now, and while I can get the possess bar up (works out of the box), the catapult abilities are broken. I can click on the buttons, press the hotkeys for the buttons, and nothing works. Curiously though - if I try /cast Plague Barrel it doesn't work either. I'm really not sure what that says though.
[Edit: I disabled Carbonite after hearing that some other people were having no luck with their QuestHelper and now it's working. So I'm thinking it was a conflict on their end. For everyone else having this problem disable Carbonite/QuestHelper and then try it.]
I haven't tried Wintergrasp yet, but FYI, in my case and probably other people, it has nothing to do with Carbonite or QuestHelper because I do not use either of those.
((Off-topic: And secondly, Carbonite is not compatible with QuestHelper, so you will really get errors. I just read what these two addons are :p ))
-----------
Anyway, update on my testing.
Sadly, I can not use the vehicle found at Borean Tundra. No, it isn't a Meat Wagon, rather it is a Tank.
I reverted back to the old BT4 version for this testing. Once I find another vehicle where I get the same buttons-not-kicking-in, I will switch to the latest version and back, to possibly identify what could be the culprit.
As i said, i am level 80 and i did every damn quest in the expansion, and i never encountered any problem. So unless you tell me how to reproduce it, or i cannot fix it.
I'll try to explain it as clearly as possible.
Horde side, there is a quest where we have to ride a Meat Wagon (or something) in Borean Tundra. We have to rescue Horde NPCs by using Ability #4. Then we also have to kill the a lot of undead minions.
Without BT4 the vehicle controls are:
Aiming: Up
Aiming: Down
Ability #1
Ability #2
Ability #3
Ability #4
On the eight "skill" button (IIRC) is the Leave Button.
Now on my end, this is my BT4 setup for Bar#1 which is also my Possess Bar.
1) BT4 Bar#1 Keybinding from left to right: ` 1 2 3 4 5 6 7 8 9 0 -
2) Pressing Shift, Alt, CTRL shows up pages 10, 9, 8
3) My Possess Bar
Checklist - special note: This is only up to Borean Tundra (after doing Howling Fjord)
a) My Possess Bar/Bar #1 is in full bar mode, thus, it shows 12 Buttons, including the Leave Button - Check; Working as Intended
b) My BT4 Keybinding reflects correctly as the same Keybinding when not using BT4 - ie Blizzard's default "main bar" also shows ` 1 2 3 4 5 6 7 8 9 0 - is this intentional? Whatever keybinding I set to my BT4 Bar#1 reflects as the keybinding of Blizzard's "main bar".
c) Testing out other "vehicle" and possess bars - works fine. Example, riding the Mammoth.
d) However, when I ride the Meat vehicle thing, and I press the keys for Ability #1 to #4 it does not work as intended.
Example, if I want to rescue the horde NPC using Ability #4, it just won't activate.
Or if I want to drop mines which is Ability #2 IIRC, it won't activate.
However, when I disable BT4, it all works as intended. Pressing Ability #1, #2, #3, and #4 works alright.
If BT4 is enabled, the only vehicle skill-command that works for me for that particular vehicle, is the Leave button. All the other abilities seems to be messed up.
Now, here's where it becomes confusing, with BT4 enabled:
If I repeatedly press, for example, Ability #4 (to rescue the Horde NPC), as-in literally press it rapidly for like 20secs to 40secs, there is a small chance of it getting "through", and the Horde NPC will be rescued so to speak.
That is as much info that can be given on the front-end. In my case, I did nothing special to arrive to the problem. I simply ride the vehicle and do the quest as instructed, that's all there is to it.
I got the new BT4 yesterday (my local time), but I haven't got the chance to test it. I am not sure if I can ride the vehicle where it bugged for me. Let's hope that I can so I can test it again. Which I am going to test after this post :p
It is sad however, that it can not be traced becase everything seems to work fine on your end, which is understandable. There is no way to fix a bug if we do not understand it ;)
Ok, time to test the new BT4. I really hope I can ride that vehicle again. Coz so far, I haven't encountered any problems, I am in Dragonblight now. Or maybe, I will install the previous BT4 and find another vehicle where I will encounter the bug-ger.
Edit: to clarify; when I possess something, the bar changes correctly, but hitting the abilities does nothing. SOMETIMES it works, but very rarely. I've notices this on all of the possess quests so far.
That exactly what is happening. If you control a Vehicle, it recreates the Vehicle-Possess bar. However, the Vehicle Bar and BT4 seems not to be communicating correctly.
When I disabled BT4, I figured that the culprit is the fact that the Vehicle Bar contains other controls. Siege Tanks for example have 2 other controls, if I have BT4 and I start pressing keys, BT4 and WoW-Client seems to mix up the controls, then everything will stop working.
Now, personally, I only noticed this problem with Possess-Bars that have "other" controls. The rest seems to be working as intended.
As to the "missing exit/leave" button, I do not know. I never encountered that.
^_^
PS.
I haven't tried it yet with SotA, but more likely than not, it will be the same, since we have or can ride Vehicles there. Maybe I'll try it tonight ^_^
0
0
I have Prat3.0 r366 and Omen3 v3.0.8-2-g32a9369.
I mentioned Omen because after installing the missing dependency - LibSink, that's when the error above showed up and it just keeps going everytime there are chats showing up.
That's my problem, I don't know which one, is it a conflict between Prat3 and Omen3? Or is it with LibSink?? Or something else altogether?
Thanks thanks.
0
2) Blizzard's QuestLog - I can't seem to find any quest related addons that builds on top of Blizzard's QuestLog implementation. I used to use nQuestLog but as I read today, it won't be maintained anymore. Anyone who have suggestions for an addon that builds on top of Blizzard's?? (For example, extending the number of quests tracked, auto collapse and expands, questminion background color, etc.)
Thanks!!
I decided once 3.2 comes, I'm going to switch to the default implementation of Blizzard; and secondly switch to addons that builds on top of Blizzard's implementation.
(PS. By any chance, will ClosetGnome be changed to be an addon on top of Blizzard's? Similar to how GroupCalendar is today?)
(PS2. Blizzard, LOL. You should just hire these great AddOn developers, it is obvious anyway to whom you got your recent new features :p Or at least include them in the credits "Inspiration:")
0
Oh! So that's what it is. I haven't noticed when they added that feature (or maybe the previous tooltip addon I was using was blocking the default mob tooltip or something).
Tnx tnx. I guess I have to live with it.
0
Cool thanks!
I edited it to check chatframe #3, since that's where the texts are showing.
[b]When I close Cartographer I get this:[/b]
[C]: in function `AddMessage'
Interface\AddOns\Prat-3.0\modules\Timestamps.lua:524: in function <Interface\AddOns\Prat-3.0\modules\Timestamps.lua:520>
(tail call): ?
Interface\AddOns\Prat-3.0\addon\addon.lua:623: in function <Interface\AddOns\Prat-3.0\addon\addon.lua:616>
(tail call): ?
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:521: in function `Debug'
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4917: in function `CheckBuffs'
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4693: in function `GrabBattlegroundGivers'
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4506: in function <...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4493>
[C]: ?
Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:298: in function `TriggerEvent'
...
[C]: in function `Show'
Interface\AddOns\MobMap\Astrolabe.lua:957: in function `AllWorldMapsHidden'
Interface\AddOns\MobMap\AstrolabeMapMonitor.lua:168: in function `Update'
Interface\AddOns\MobMap\AstrolabeMapMonitor.lua:99: in function <Interface\AddOns\MobMap\AstrolabeMapMonitor.lua:97>
[C]: ?
[C]: in function `Hide'
Interface\FrameXML\UIParent.lua:1908: in function `HideUIPanel'
Interface\FrameXML\UIParent.lua:1881: in function <Interface\FrameXML\UIParent.lua:1879>
[C]: in function `ToggleFrame'
[string "TOGGLEWORLDMAP"]:1: in function <[string "TOGGLEWORLDMAP"]:1>
Interface\AddOns\Test\test.lua:23: in function <Interface\AddOns\Test\test.lua:22>
[C]: in function `AddMessage'
Interface\AddOns\Prat-3.0\modules\Timestamps.lua:524: in function <Interface\AddOns\Prat-3.0\modules\Timestamps.lua:520>
(tail call): ?
Interface\AddOns\Prat-3.0\addon\addon.lua:623: in function <Interface\AddOns\Prat-3.0\addon\addon.lua:616>
(tail call): ?
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:521: in function `Debug'
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4917: in function `CheckBuffs'
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4693: in function `GrabBattlegroundGivers'
...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4506: in function <...e\AddOns\DailiesQuestTracker\DailiesQuestTracker.lua:4493>
[C]: ?
Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:298: in function `TriggerEvent'
...
[C]: in function `Show'
Interface\AddOns\MobMap\Astrolabe.lua:957: in function `AllWorldMapsHidden'
Interface\AddOns\MobMap\AstrolabeMapMonitor.lua:168: in function `Update'
Interface\AddOns\MobMap\AstrolabeMapMonitor.lua:99: in function <Interface\AddOns\MobMap\AstrolabeMapMonitor.lua:97>
[C]: ?
[C]: in function `Hide'
Interface\FrameXML\UIParent.lua:1908: in function `HideUIPanel'
Interface\FrameXML\UIParent.lua:1881: in function <Interface\FrameXML\UIParent.lua:1879>
[C]: in function `ToggleFrame'
[string "TOGGLEWORLDMAP"]:1: in function <[string "TOGGLEWORLDMAP"]:1>
[b]When I zone-in to another zone, I get this:[/b]
I saw two addons from those two reports:
I assumed it wasn't AceEvent-2.0 since it's part of the core if I'm not mistaken?? I turned off DQT = problem fixed.
Did I understand it correctly? If I did, then I'll file a report to DQT.
Thanks for the help ^_^
0
The Blue Circle is my question as to what addon it is.
The Red Circle is nQuestLog, I'm cool with it.
Asking here in case someone encountered this already, or maybe someone will figure it out faster than me.
Thanks in advance!!
My AddOns:
Additional info:
I have the MobMap settings related to quests already turned-off.
Checked Cartographer and CowTip - both a no.
Checked nQuestLog, not it either.
I also turned-off the Blizzard settings
Of the initial guessing, I can't think of any addon that has anything to do with quests. I hope I can avoid the bloody testing method :p Isolation (one addon at a time).
Again, tnx tnx.
0
Hmm, my CurseClient is setup to 'Alpha'. ^_^
Will try to do another round of tests and detection a few hours later.
EDIT:
Removed Prat comment... what I was thinking was Perl not Prat :p
0
I can't control it either, it isn't in WoW's chat window/menu option. For some reason, it chose to push those texts on my custom chat window and not on WoW's default (General/Combat Text).
Here are my list of addons:
Thanks thanks.
0
Yep, you did misunderstand, as far as people having these issues are concerned, we read the quests, we read the vehicle skills, and we know how to do the quests. :p
As I have detailed in my reports, I tested it both with BT4 and without BT4. I call this issue "Vehicle Command-Lag", since that's where I ended up.
So to summarize:
1) Tested with BT4 and without BT4
2) Tested without any addons
3) Experienced the Vehicle Command-Lag on all setups (#1 and #2 above)
The "Vehicle Command-Lag" only occurs on, well, vehicles. All other game functions works fine. You can attack normally (if you are not on a vehicle), chat, walk, loot, interact with other quest objects, etc. But once you get on the vehicle, if you are unlucky, you get the VCL issue.
There seems to be some workaround which I forgot to mention.
a) Re-log
b) If it still doesn't work, go out of the zone then re-log
c) If it still doesn't work, do #2, but shut-down your client for 20 minutes
d) If all else fails, disable all your addons and hope the VCL doesn't kick-in
e) If it still fails, just get back to it later or try getting on a totally different vehicle to let the client and the server fix themselves.
All-in-all, I think this is out of BT4. If it happens without BT4 and without AddOns, then it is a Blizzard bug. Which explains why other BT4 users did not experience this issue. We were the unlucky ones :p
So cool, now to hope that Blizzard can duplicate this issue so they can start tracing what is causing the problem. IMO, the VCL seems to be random, however, there seems to be a list of vehicles where this occurs.
^_^
0
Just an update, I experienced it again for this quest: http://www.wowhead.com/?quest=13086 "The Last Line Of Defense".
Same thing, other people reported the same problem. However, for my experience, it works w/o BT4, but doesn't work with BT4.
This should be on Blizzard's part, their Vehicle Bars.
0
I encountered the problem again last night (8 hours ago), this time for this quest: Valkyrion Must Burn, in Storm Peaks.
I have to spam the button, leave, then ride again, then spam, to get some random "successful" fire command.
But, I found something. Check the comments from: http://www.wowhead.com/?quest=12953
Other people are having problems, but I am not sure if they have Bartender4, so I did a test again.
Without Bartender4, it fires normally.
I also did button spamming and I noticed that there are 1 to 2 extra arrows showing up - graphics, with the "real" arrow among them.
The fake arrows will disappear half-way through.
With Bartender4, it now fires normally.
The difference, there are twice extra arrows this time, so 3 to 4 fake arrows graphics showing up on the screen if you are spamming the button.
From what I can tell, it seems to be on Blizzard's end, unless it was being caused by other addons. The vehicle commands seems to be getting some command-lag with or without BT4. However, everything else is fine, no lag at all (ie if not on a vehicle).
Anyway, I may be wrong. I haven't turned-in the quest yet in case you need me to test it.
I'm using version:
4.2.1-1-g80667ee
0
I'll try that. Going to ding to 77, then I'll enter Wintergrasp. I reverted back to the BT4 version where I first encountered it and see if I'll experience it in Wintergrasp vehicles.
If I do, then I'll switch to the latest Alpha and test.
Btw, yesterday, I tried it with the Dragon vehicle in Dragonblight (using the old version) but I didn't encounter problems (I'm not sure if it has to do with it 'flying' :p ).
Will reply as soon as I tested it in Wintergrasp, old and the latest Alpha. (I really need to find a vehicle where I'll encounter it again... )
thanks. Logging to WoW......
0
I haven't tried Wintergrasp yet, but FYI, in my case and probably other people, it has nothing to do with Carbonite or QuestHelper because I do not use either of those.
((Off-topic: And secondly, Carbonite is not compatible with QuestHelper, so you will really get errors. I just read what these two addons are :p ))
-----------
Anyway, update on my testing.
Sadly, I can not use the vehicle found at Borean Tundra. No, it isn't a Meat Wagon, rather it is a Tank.
I reverted back to the old BT4 version for this testing. Once I find another vehicle where I get the same buttons-not-kicking-in, I will switch to the latest version and back, to possibly identify what could be the culprit.
^_^
0
I'll try to explain it as clearly as possible.
Horde side, there is a quest where we have to ride a Meat Wagon (or something) in Borean Tundra. We have to rescue Horde NPCs by using Ability #4. Then we also have to kill the a lot of undead minions.
Without BT4 the vehicle controls are:
Aiming: Up
Aiming: Down
Ability #1
Ability #2
Ability #3
Ability #4
On the eight "skill" button (IIRC) is the Leave Button.
Now on my end, this is my BT4 setup for Bar#1 which is also my Possess Bar.
1) BT4 Bar#1 Keybinding from left to right: ` 1 2 3 4 5 6 7 8 9 0 -
2) Pressing Shift, Alt, CTRL shows up pages 10, 9, 8
3) My Possess Bar
Checklist - special note: This is only up to Borean Tundra (after doing Howling Fjord)
a) My Possess Bar/Bar #1 is in full bar mode, thus, it shows 12 Buttons, including the Leave Button - Check; Working as Intended
b) My BT4 Keybinding reflects correctly as the same Keybinding when not using BT4 - ie Blizzard's default "main bar" also shows ` 1 2 3 4 5 6 7 8 9 0 - is this intentional? Whatever keybinding I set to my BT4 Bar#1 reflects as the keybinding of Blizzard's "main bar".
c) Testing out other "vehicle" and possess bars - works fine. Example, riding the Mammoth.
d) However, when I ride the Meat vehicle thing, and I press the keys for Ability #1 to #4 it does not work as intended.
Example, if I want to rescue the horde NPC using Ability #4, it just won't activate.
Or if I want to drop mines which is Ability #2 IIRC, it won't activate.
However, when I disable BT4, it all works as intended. Pressing Ability #1, #2, #3, and #4 works alright.
If BT4 is enabled, the only vehicle skill-command that works for me for that particular vehicle, is the Leave button. All the other abilities seems to be messed up.
Now, here's where it becomes confusing, with BT4 enabled:
If I repeatedly press, for example, Ability #4 (to rescue the Horde NPC), as-in literally press it rapidly for like 20secs to 40secs, there is a small chance of it getting "through", and the Horde NPC will be rescued so to speak.
That is as much info that can be given on the front-end. In my case, I did nothing special to arrive to the problem. I simply ride the vehicle and do the quest as instructed, that's all there is to it.
I got the new BT4 yesterday (my local time), but I haven't got the chance to test it. I am not sure if I can ride the vehicle where it bugged for me. Let's hope that I can so I can test it again. Which I am going to test after this post :p
It is sad however, that it can not be traced becase everything seems to work fine on your end, which is understandable. There is no way to fix a bug if we do not understand it ;)
Ok, time to test the new BT4. I really hope I can ride that vehicle again. Coz so far, I haven't encountered any problems, I am in Dragonblight now. Or maybe, I will install the previous BT4 and find another vehicle where I will encounter the bug-ger.
So, be right back.
0
Yes, that is true, however, I believe he reported about it not just because of the Flying Machine quest but because of the other Vehicles-Possess bar.
I for one can confirm his report. In fact, the quote below explains it more clearly.
That exactly what is happening. If you control a Vehicle, it recreates the Vehicle-Possess bar. However, the Vehicle Bar and BT4 seems not to be communicating correctly.
When I disabled BT4, I figured that the culprit is the fact that the Vehicle Bar contains other controls. Siege Tanks for example have 2 other controls, if I have BT4 and I start pressing keys, BT4 and WoW-Client seems to mix up the controls, then everything will stop working.
Now, personally, I only noticed this problem with Possess-Bars that have "other" controls. The rest seems to be working as intended.
As to the "missing exit/leave" button, I do not know. I never encountered that.
^_^
PS.
I haven't tried it yet with SotA, but more likely than not, it will be the same, since we have or can ride Vehicles there. Maybe I'll try it tonight ^_^