This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.
What steps will reproduce the problem?1. Latest Decursive and wait for a while in raid.2.3.
What is the expected output? What do you see instead?Wow-client crashes.
What version of the product are you using?WoW 2.4.3, Latest Decursive found on CurseForge
Do you have an error log of what happened?No.. The client crashes totally
Please provide any additional information below.
How do you know it's decursive ? What is the type of crash you experience (for example error 132 etc...)?
"wait for a while in raid"
What means "for a while"? 5 minutes? 30 minutes?
What do you mean by "wait"? - you do nothing, you're in a raid group. - you are in battle etc...
What do you mean by "Latest Decursive found on CurseForge"? provide me the version as displayed in the about box of Decursive and the release date.
Thanks
I do get an error message which states that is it Decursive(I'm sorry but the WoW-client totaly freeze so i cant copy the message). I have not experiensed any problems after i removed Decursive.
For a while is more about 30minutes. I have gotten the problem both out of combat and in combat. It was "2.3_Beta_2-1-g702d8a1" I tried if i remember correctly.
I'll install it again and try and write down the error message.
Date: 2008-10-12 19:28:32 ID: 2 Error occured in: Global Count: 1 Message: ..\AddOns\Decursive\Dcr_DebuffsFrame.lua line 470: stack overflow Debug: Ace2\AceEvent-2.0\AceEvent-2.0.lua:369: Ace2\AceEvent-2.0\AceEvent-2.0.lua:345
Ok the massage indicates that this happens when Decursive scans the raid group.
Are you using the priority and/or the skip list? How many characters were in your raid group?
We were 25ppl in the raidgroup when it happened.
I have a prio-list but now that you mention it, it didnt seemed to work. I always was on the first position but the ppl on priolist should have been listed first. There wasnt a raid today so I havent been able to do more testing. I hope you can have some ideas where the problems comes from anyway. If you want me to try something I can try it tomorrow during raid.
Note that since the version 2.3 beta, the internal priority and skip list format has changed, the first time you install 2.3, the priority and skip list are cleared.
So did you re-configure your priority list since you installed this beta?
- Are you using names in the list or group/class? - How many players are in the priority list?
Something you can try is to not use the priority list at all and see if it still crashes ; use the 'C' button on the list interface to clear it (or just remove every one)
Thank you
Please, try : 2.3 beta 3
I didnt reconfigure the prio list after installing the beta. And that would answer why I never saw the previously prioritized members first. I had approx 8 members in the prio list before.
I will try the new beta 3 and make sure the prio list is cleared tonight.
I tried Beta 3 yesterday. Wasnt a "hard" raid, we only did vashj but I didnt get the same problem as before. Maybe I was lucky or you solved the problem.
Thanks.
Can you confirm me the problem is fixed?
I did Felmyst and Twins yesterday with full raid. The problem did not appear so I would consider this problem fixed.
To post a comment, please login or register a new account.