It's an exact replica of the lag issues CTRA had when patch 2.0 first came out, but was fixed with release 2.001 of CTRA, iirc.
It's probably not sRaidFrames but something else conflicting with it. What other addons are you using?
No, if you look around page 52, I explain the very same situation. I've tried to run sraidframes by itself, and I had this issue. I was less obvious, but the more mods you have, the more it accentuates the problem.
What I suspect is it may be related to the range check. I may be wrong, but I've noticed that when using another raidframe system (I've tried simpleraid, grid, sraidframes) all of them froze at the very same moments (when players zone in/out, log in and out, join/leave the raid, die).
It's an exact replica of the lag issues CTRA had when patch 2.0 first came out, but was fixed with release 2.001 of CTRA, iirc.
It's probably not sRaidFrames but something else conflicting with it. What other addons are you using?
Hmm I'm at work so I can't get an exact list, but off the top of my head:
Titan Bar
CTMod (some of it)
Deadly Boss Mods
Druid Bar
KTM
pDebuffFilter
Trinket Menu
Item Rack
oRA2
OmniCC
Mass Auction
Some Ace mod that disables/hides UI error messages
I think that's just about everything. I don't use the entire CTMod suite, as I had issues with a lot of it, so mainly that is for unit frames, map coordinates and the mailbox features.
Range does seem a likely suspect, but as I said I had the same issue with CTRA when 2.0 first came out, and I can't remember that having any range component to it. And again, the CT people fixed it shortly after it was reported as a known issue (probably the last bit of work that was done on that mod).
I can try messing with my mods tonight to see if I can find one that is conflicting with sRF.
As I said, I tried it with 0 mod on (only sraidframes), but was still getting the issue. You'll probably notice that the freeze is less important, but still noticeable.
As I said, I tried it with 0 mod on (only sraidframes), but was still getting the issue. You'll probably notice that the freeze is less important, but still noticeable.
All I can say is that I run a LOT of mods. I've used sRaidFrames since before BC came out, and can't remember ever having the freezing issues.
If it freezes up for you when only sRaidFrames is enabled, I would definately think you have something else wrong, not something wrong with sRaidFrames.
Did you move your AddOns and WTF Folders out of the WoW directory and then only put sRaidFrames into a new, empty AddOn folder? (essentially creating a pure vanilla WoW install). If you didn't test it this way, try it...
I'll play around with it, see if I can point to anything that might help.
I would make a backup of your WTF/Interface folders (just move them to your desktop or something). Then stick just sRaidFrames into a new Interface\AddOns\ folder and run it solo. If you don't see freezing issues with it then, you know that sRaidFrames isn't the problem.
Move your Interface&WTF folders back and WoW will act like you never changed anything. If sRaidFrames works fine alone, I would start with finding any sRaidFrame files in the WTF folder and deleting them...making it start from defaults again. If that fixes it, woot...if not, it's definately another mod not playing nice.
Of the mods you listed...
I currently Use:
KTM (well not anymore, but it didn't cause any issues)
Trinket Menu
Item Rack
oRA2
OmniCC
I do not use:
Titan Bar
CTMod (some of it)
Deadly Boss Mods
Druid Bar
pDebuffFilter
Mass Auction
I would tend to suspect something with pDebuffFilter or some part of CTMod, just because they potentially encompass similar functions that sRaidFrames uses.
TitanBar could possibly have a module that is also pulling raid info?
I wouldn't suspect Druid Bar, DBM or Mass Auction to have any involvement...but anything is possible.
Maybe that will give you something to start with. FWIW I Raid with both a Druid and a Hunter and have not had any issues with sRaidFrames, I run quite a few mods, and still no issues. Hopefully you can figure out whats interfering and get it working.
I'll play around with it, see if I can point to anything that might help.
I would make a backup of your WTF/Interface folders (just move them to your desktop or something). Then stick just sRaidFrames into a new Interface\AddOns\ folder and run it solo. If you don't see freezing issues with it then, you know that sRaidFrames isn't the problem.
Move your Interface&WTF folders back and WoW will act like you never changed anything. If sRaidFrames works fine alone, I would start with finding any sRaidFrame files in the WTF folder and deleting them...making it start from defaults again. If that fixes it, woot...if not, it's definately another mod not playing nice.
Of the mods you listed...
I currently Use:
KTM (well not anymore, but it didn't cause any issues)
Trinket Menu
Item Rack
oRA2
OmniCC
I do not use:
Titan Bar
CTMod (some of it)
Deadly Boss Mods
Druid Bar
pDebuffFilter
Mass Auction
I would tend to suspect something with pDebuffFilter or some part of CTMod, just because they potentially encompass similar functions that sRaidFrames uses.
TitanBar could possibly have a module that is also pulling raid info?
I wouldn't suspect Druid Bar, DBM or Mass Auction to have any involvement...but anything is possible.
Maybe that will give you something to start with. FWIW I Raid with both a Druid and a Hunter and have not had any issues with sRaidFrames, I run quite a few mods, and still no issues. Hopefully you can figure out whats interfering and get it working.
Thanks for the tips! Just to make sure I understand, you suggest I take the WTF and Interface folders out of my WoW directory and then just start up WoW, which will then create new, fresh versions of these folders? I can then put just sRF into the Interface/Addons folder and sort of build my UI from scratch with that as the starting point?
Thanks for the tips! Just to make sure I understand, you suggest I take the WTF and Interface folders out of my WoW directory and then just start up WoW, which will then create new, fresh versions of these folders? I can then put just sRF into the Interface/Addons folder and sort of build my UI from scratch with that as the starting point?
Sorry for the long delay in response.
Yup, WoW stores almost all of the configuration data in your WTF folder. And actually, if you save the config.wtf that is in the base WTF folder, you won't have to reset your sound/video settings.
If sRF works fine by itself, then you know its another addon causing the problem. Then all you can really do is start adding them in one by one and seeing what happens. Its not a fast process, but it will work.
Are you referring to the range issues, or the lag problem I'm experiencing?
Any ideas on the lag problems I'm having? =)
It's an exact replica of the lag issues CTRA had when patch 2.0 first came out, but was fixed with release 2.001 of CTRA, iirc.
It's probably not sRaidFrames but something else conflicting with it. What other addons are you using?
No, if you look around page 52, I explain the very same situation. I've tried to run sraidframes by itself, and I had this issue. I was less obvious, but the more mods you have, the more it accentuates the problem.
What I suspect is it may be related to the range check. I may be wrong, but I've noticed that when using another raidframe system (I've tried simpleraid, grid, sraidframes) all of them froze at the very same moments (when players zone in/out, log in and out, join/leave the raid, die).
Hmm I'm at work so I can't get an exact list, but off the top of my head:
Titan Bar
CTMod (some of it)
Deadly Boss Mods
Druid Bar
KTM
pDebuffFilter
Trinket Menu
Item Rack
oRA2
OmniCC
Mass Auction
Some Ace mod that disables/hides UI error messages
I think that's just about everything. I don't use the entire CTMod suite, as I had issues with a lot of it, so mainly that is for unit frames, map coordinates and the mailbox features.
Range does seem a likely suspect, but as I said I had the same issue with CTRA when 2.0 first came out, and I can't remember that having any range component to it. And again, the CT people fixed it shortly after it was reported as a known issue (probably the last bit of work that was done on that mod).
I can try messing with my mods tonight to see if I can find one that is conflicting with sRF.
So I'm SOL? =(
I'll play around with it, see if I can point to anything that might help.
Thanks a bunch Saroz. Just updated my version and will raid this weekend.
All I can say is that I run a LOT of mods. I've used sRaidFrames since before BC came out, and can't remember ever having the freezing issues.
If it freezes up for you when only sRaidFrames is enabled, I would definately think you have something else wrong, not something wrong with sRaidFrames.
Did you move your AddOns and WTF Folders out of the WoW directory and then only put sRaidFrames into a new, empty AddOn folder? (essentially creating a pure vanilla WoW install). If you didn't test it this way, try it...
I would make a backup of your WTF/Interface folders (just move them to your desktop or something). Then stick just sRaidFrames into a new Interface\AddOns\ folder and run it solo. If you don't see freezing issues with it then, you know that sRaidFrames isn't the problem.
Move your Interface&WTF folders back and WoW will act like you never changed anything. If sRaidFrames works fine alone, I would start with finding any sRaidFrame files in the WTF folder and deleting them...making it start from defaults again. If that fixes it, woot...if not, it's definately another mod not playing nice.
Of the mods you listed...
I currently Use:
KTM (well not anymore, but it didn't cause any issues)
Trinket Menu
Item Rack
oRA2
OmniCC
I do not use:
Titan Bar
CTMod (some of it)
Deadly Boss Mods
Druid Bar
pDebuffFilter
Mass Auction
I would tend to suspect something with pDebuffFilter or some part of CTMod, just because they potentially encompass similar functions that sRaidFrames uses.
TitanBar could possibly have a module that is also pulling raid info?
I wouldn't suspect Druid Bar, DBM or Mass Auction to have any involvement...but anything is possible.
Maybe that will give you something to start with. FWIW I Raid with both a Druid and a Hunter and have not had any issues with sRaidFrames, I run quite a few mods, and still no issues. Hopefully you can figure out whats interfering and get it working.
Thanks for the tips! Just to make sure I understand, you suggest I take the WTF and Interface folders out of my WoW directory and then just start up WoW, which will then create new, fresh versions of these folders? I can then put just sRF into the Interface/Addons folder and sort of build my UI from scratch with that as the starting point?
and if you want to revert to your current one, just delete the new folders and move the old ones in... done
Sorry for the long delay in response.
Yup, WoW stores almost all of the configuration data in your WTF folder. And actually, if you save the config.wtf that is in the base WTF folder, you won't have to reset your sound/video settings.
If sRF works fine by itself, then you know its another addon causing the problem. Then all you can really do is start adding them in one by one and seeing what happens. Its not a fast process, but it will work.
Just to confirm: Raided 10man and 25man over the weekend and range check is indeed functional again in current SRF versions. Thumbs up.