I am not getting any errors, but I'm having a serious problem with DBM that I figured is relevant to post here. While ideally I would like to actuallky solve the issue, maybe someone can at least use the information to figure out if this is a bug with the addon and not myself.

DBM is not working for me, at all. Everything is set up and enabled in the settings and all the test bars, warnings and sounds work in test mode. But as soon as I get into raid combat, I get absolutely nothing at all. The module doesn't even load on its down when I zone in; I have to force it to load when I zone in and after I've run back after a wipe. Forcing it to load, however, does not make the warnings and timer bars work. The only thing that did work was my range check, although I had to manually turn it on and manually set it to the appropriate distance each fight.

Worse yet, DBM is repressing the raid warnings from the raid leader's boss mod so I can't even rely on that like I used to when I'd experience combat log locks in the past. (I couldn't find a setting to turn that off, if there is such an option)

It's like it's not syncing with my game or combat log, but my combat log is not file locked. My combat log is recording and other addons dependent on it (like recount) work fine. Additionally, restarting the client had no impact.

I tried logging in and out, restarting, reinstalling the addon (deleting the orignal first), even disabling my other addons to see if any were conflicting with it. I also tried disabling all the other DBM modules but Icecrown on the addons menu on the character screen. And yes, I saw the message about the error with older versions of classic and BC turning off the module, but that didn't fix this either (and also my issue isn't just the module not loading automatically). Nothing I tried made it work.

I ended up having to disable DBM entirely just so I could at least see the /rw from someone else. Last night I was just a sub though; tonight I will be the raid leader of my 25man and won't even be able to do that.

FWIW, I am using the latest [release] version straight from this site and not from a third party site. I'm playing on Windows client patched for 4.0.1.

Just for the record, after three days of mine not working, it spontaneously began working one evening. I had made no changes to anything.

I'm still not sure whether it's on WoW's end with patch bugs or DBM (sorry there is no errors generating to share) but whatever it is, it's clearly situational. I am pretty confident that it isn't another addon messing it up because I still had the issue even after disabling everything else, nor do I think the combat log was the issue (and even if I had been, client restarts usually fix that) because my other addons that use the log were working and it looked fine visually. If it occurs again, though, I will let you know as well as any other changes I may have made to my setup to influence it.

I realise all this information is too ambiguous for you to know where to look for bugs and I appologise for that.

(english client)

edit: while we're on the topic though, is there a way to disable the muting of the raid leader's raid warnings for the times when an individual's boss mod is unworking? I found the setting to block or allow whispers but nothing to do with the general warnings. This would be very helpful for the times when DBM didn't work, to at least be able to watch the RL's warnings when my timers were unavailable. Or, as a RL myself, to turn on the ability to broadcast to the raid and not have to worry about their copy of the addon blocking the messages.

Quoted from ""Omega""

yeah it's in spam/filter options.

disable "filter warnings from other boss mods"

Much appreciated.

Quoted

not much to debug,if combat log unfiltered is working then mod should be working. unless it's not loaded but you say that it's loading fine when you zone in. and showing loaded in the gui right?

What exactly do you mean by loaded? In my case, the module was not loading on its own when I zoned in, and although I could force load it, it still was not working. But the addon itself seemed to be working for all other appearances (I could bring up the gui and access the config in my interface options, and I could run all the test settings okay), it just seemed to not be recognising that I was in a raid or syncing with what was actually occuring in-game. Basically it was acting as if I was combat log locked, even though I wasn't and my log was unfiltered and working in other regards.

Quoted

any of you warlocks by chance?

The particular class I was playing when I was having troubles was a shaman. However, worked fine this weekend on my rogue.