WowAce

What steps will reproduce the problem?
1. Sign in on a rogue
2. Attack something with a combo point producing attack
3. Observe
4. Go to setting, under target, and click blizzard combo points twice (uncheck it and recheck it)
5. Repeat 1-3

What is the expected output? What do you see instead?
Expect to see combo points over the target's portrait, but see nothing until steps 4-5, then they are there.

What version of the product are you using?
3.6.15

Do you have an error log of what happened?
No log

Please provide any additional information below.

Is this still happens with 3.6.20 Beta 2 ??

But I guess I needed to find some time to test this with my brother's 85 rogue...

@PlayerLin: Go

I'm quite sure that I saw this already a few times

@Asixandur: Go

See a few times but still cannot finding a way to fix it?

@PlayerLin: Go

I saw it on Curse, not myself

@Asixandur: Go

......I know but better try with myself to confirm.

OK, tested with my brother's 85 rogue with 3.6.20 Beta 2(damn, I forgot updates my copy to Beta 3)......

And it works perfectly when I login... I guess it may some other reasons cause the problem...

So, we'll wait for more infos from th3silly0n3

Updated to the beta from the release version 3.6.15 - same thing is happening. I have screenshots to illustrate, but not sure where I'd need to put them to show this.

I turned on display lua errors, and I don't get any error. I did have the option for "Display Combo Point Bar" turn on, as well. I turned that off and I see no combo points at all until I go into the x-perl options, check and then uncheck the "Blizzard's Combo Points," then try again. Then I see the five circles with their combo points above the portrait as should be the case from the start.

I can try totally removing then putting back a fresh copy of x-perl, but other than that, I just have no idea what could be the issue here. It's like it's not recognizing the setting initially.

__

Edit: So I logged my level 54 rogue in on my second account...same exact settings on this copy of WoW...and it works fine. So something at level 90?

I can't think of anything else to test. Still no lua errors, just not sure.

I did some further testing after totally removing and reinstalling x-perl with 3.6.20 beta 3.

Apparently I don't need to even change anything in my settings, all I have to do is open the x-perl configuration and then close it, and it restores the combo point bubbles to their proper place.

Also, I did get a lua error when I opened x-perl's configuration while in combat, but I suspect that's expected.

In combat, I can click twice on the xperl chocolatebar broker button, and open the options, and close them - the combo points don't come back if I do that - but they DO come back during combat if I click on and off of the blizzard combo points option under target.

Outside of combat, all I have to do is open and close the configuration itself.

I can't think of anything else I can try to do to help out with more information.

It's really strange, I think is due to broken config. It isn't a bug also because you say that it works on your second account's rogue

Do changing configurations in combat will get in-combat lockdown taints easily... so that's normal because I guess it missed checking that since beginning. :p

And yes, if in-combat lockdown taints happens, the option does not works and no effects until you exit from combat.

Not recommend doing that in-combat, some code for locking some options on X-Perl Option UI in combat isn't working as it intended so it still have high chances to get taints.

If you think your configuration file has problems? Just go WTF directory and finding and killing it, but it will reset all setting to default ones... :p

I actually deleted all files and folders related to x-perl, and tried again, and it still does it on my 90 rogue. The second account actually uses the exact same configuration as my main account, because I copied the files over.

A fresh install of x-perl after all files have been deleted does the same thing. Although I'm unsure if I'm getting a 100% total reset - does the new default xperl have the player, target, and focus frames across the bottom? I don't know why, but when I removed everything, and reinstalled, and deleted all x-perl related config lua files from inside my wtf folder, I see this as the configuration. Is there a file I might be missing somewhere?

Tried again, still no luck. On my 90 it does this, but on lower level it doesn't. New default config, deleted everything, still does it. I can't really understand why.

I don't think the default is in on bottom of your screen, it should be on upside of screen, like the Blizzard's default unitframe UI.

It still weird, do you try only using X-Perl(means only X-Perl loaded)?

I removed xperl, and lost all of my unit frames. I then removed ALL addons, and figured out that VuhDo is causing that loss. Turned everything on except VuhDo and now X-Perl works fine.

Sorry for the confusion, but apparently my VuhDo config is either ruined or I have a setting messed up in it.

Anyway, if anyone else has the problem, VuhDo is a likely culprit.

_

edit: VuhDo was set to hide all my default frames, not sure how it got set that way, or if it came that way, but that was my problem. I set it to show them all and now x-perl's combo point functions work fine.