nUI 6 Talent Bug
 

The picture says it :D

Damn Oomkins, they get all the good specs.... like Resto, lol :P

Were they resto when you first inspected them, or they first joined the group, and then respec'd or were they already Boomkin when they joined the group?

Trying to figure out if the spec was right initially and missed switching to their second spec or if it was something else.

Thats what I am not sure of. When does the talent inspect happen ? We were grouped for a while before we went in the instance but he wasn't nearby. He is a boomkin/resto though so he may have switched over before we ported to the instance. I can double check with him and see if he remembers. An 11 year old may not quite remember rofl. He's the son of one of our old timers rofl.

No worries either way... just keep and eye on it.

The inspect is done as soon as possible and cached. It *should* detect when the respec happens, however, if the unit is out of range when that happens, it's possible it could be missed.

Ah, that is probably what happened as he was in Ironforge and I was in Dalaran.

No other way of forcing an inspect ? In case of these anomalies ? Like, targetting or will an inspect itself force a fresh talent inspect update ?

An inspect itself should do the trick.

The talent spec switching thing is an issue. I still don't have a good answer for that other than to reinspect, but that's expensive and with the throttling of inspects now in place, could be broken pretty easily.

Ah gotcha. Maybe, keep a record of the last inspect done and to whom and if someone is hovered over the inspect info is marked as being out of date or something to give people the option to inspect if they need to ? Just an idea. Not touched inspecting so have no clue what is possible or not there.

The inspection system is... challenging. It's a poll response client-server thing and, if I may be so bold, way less than elegant and not designed to be used the way the mods are now using it. The addition of dual spec has made that even more interesting. I've been lobbying for a better API but hold little hope it will ever happen.

I'm likely going to add detection of when a unit goes out of range and just invalidate their talent spec data when that happens. It'll mean doing far more inspections than should have to be done, but it will at least better ensure reliable data.

For now I think I'm just going to be content that it seems to be far more stable in nUI6 than it was in nUI5.

I see this bug too and I see it on more than on moonkins.

Attachment 4586

Attachment 4587

The Picture say's everything, but maybe I should translate.

On the first picture you see a friend of mine playing a mage. The Talentspec says that the she is skilled as tank.

On the second one you see a shaman I never seen before. The talentspec says he has a holy talent skill.

So What I think is, that nUI mix the talentspec's of the players of an raid, because the priest under the shaman was skilled as Holy. The Warrior with name Crarbag on the screen is skilled as tank and the Paladin on the first place in the group too.

What I watched several times with nUI5 and 6 is that if click right on a char and want to look on the talents, mostly they are changing after a second or so, to a shaman talent tree, equally which char I want to see. Only shamans I can look without many Problems.

I'll tanke a look deeper if there is an addon conflict, but with nUI6 this problem is going back really hard. with nUI5 it works most of the times, with nUI6 never.

At least one of my addons (GearScore, I think) reports when a player was last inspected. I imagine that's no more than informatory, but it seems pretty clear that other addon authors have seen it, and nobody, so far, has figured out a fix or work around.

I suspect that with no addons enabled, you won't see the problem, because only the default blizz interface is inspecting players. I don't know if it will happen with just one addon (that inspects players) enabled, though it seems likely. It seems pretty much guaranteed to happen with more than one.

I have had this happen as well, however, I don't think it is somehting being jumbled in raid, or at least not the only thing happening.

As on many occasions in 5 mans I see a talent spec listed on the wrong class, but it is for a class not in the group. For example, Prot warrior, Assassination Rogue, Tree Druid, Hunter, Lock. And the Warrior showed Shadow for spec, when there was no priest to have gotten mixed with. I have errors like this many time, I never thought much of it (more just got a small laugh) but when I inspect them I can see talents correctly, so it isnt caching someone elses spec, but the pic in my 5man window still shows the same incorrect info.

If you are referring to nUI5, this is a known problem which is what I am trying to fix in nUI6. If you are seeing things like "shadow warriors" in nUI6 I need to know that, if the problem you're having is in nUI5 then I already know about that.

Prot warrior => Shadow (priest) because those two trees are, for their respective classes, in the same place (ie, last) in the list of trees. Or so it seems to me, anyway.:cool:

Forgot to check, my bad.
As for your Shadow Warrior comment, gave me fond flashbacks to an old Windows 95 FPS game, Shadow Warrior "Haha! You no mess with Lo Wang...." Hilarious game, the asian Duke Nukem. Anyway, back to topic.....

Hmm, that might be it alright.

I'll have to pay close attention but so far in nUI 6 the only problem I have seen is refreshing the info after a spec change out of your range.

Yeah -- the same tree wouldn't be the cause as the "name" of the tree is retrieved at the same time as the points in the tree... so a "shadow warrior" was the result of a failed read of a shadow priest and not just because they have the same tree.

The next update to nUI6 will, I hope, solve the problem of people going out of range and respecing.