Naranjar, what you stated is basically correct. Release sites get release versions. SVN gets atomic commits which are often unstable. If your guild wants to be sure everyone's version is compatible with each other, use the release versions posted on Curse and WoWI.
This is not ok. People use wowaceupdater to update all wowace2 mods. Developers should use other tools or at least make the updater pull stable branches. Don't commit broken software. If I have to go to curse to get working verions of Omen it would be easier to delete it and use ktm instead so that way I can use the updater for other addons.
This is not ok. People use wowaceupdater to update all wowace2 mods. Developers should use other tools or at least make the updater pull stable branches. Don't commit broken software. If I have to go to curse to get working verions of Omen it would be easier to delete it and use ktm instead so that way I can use the updater for other addons.
I can't believe people are still going on about this. My guild was severely annoyed as well and actually had everyone disable Omen for a night in Hyjal, but it's been weeks now since Omen/Threat broke backwards compatibility.
I do agree that truly unstable/broken stuff doesn't belong on the SVN trunk, but I haven't seen a version of Omen/Threat that qualifies as broken or unstable - just incompatible with other versions.
Forget the naysayers ... Omen2 is a grand addon in my opinion.
I have run into a problem, I have had to switch to a computer that uses Vista. Omen worked for a week but seems to have disappeared.
It shows to be installed, I can check it in the addon list, etc. It just doesn't appear anywhere. I've tried using /omen config, etc. to bring it up but nothing has happened. Any suggestions?
the new omen is working fine for me. i use it in single target mode only though. no problems in KZ and ZA... just the occasional raider with a severly outdated version of omen of one that isn't working. They don't show up on the threat list.
Ah well... all just update 30 min before raid and you're good to go.
Forget the naysayers ... Omen2 is a grand addon in my opinion.
I have run into a problem, I have had to switch to a computer that uses Vista. Omen worked for a week but seems to have disappeared.
It shows to be installed, I can check it in the addon list, etc. It just doesn't appear anywhere. I've tried using /omen config, etc. to bring it up but nothing has happened. Any suggestions?
Thanks
maybe the monitor setting is much lower than on the first computer, and Omen needs something to make sure it's not positions off the edge of the screen? I've seen other mods end up off screen when I go from my Tower !920x1200 to my laptop 1440x900 (moving the mods and saved data over) Some mods are smart and know their relation ship to the screen edge, some are not. I haven't played on my laptop in months, so I don't know if Omen is or not.
I can't believe people are still going on about this.
Me neither. I'm perfectly happy pulling the latest version from WAU (or SVN, for that matter). And I know that it's OK for people to be running slightly different versions of Threat and except for that one bug a few weeks ago, it will work alright. But I'm a software engineer who understands this stuff. All I'm saying is that there's a lot of superstition about software and a lot of people feel it's essential to have everyone on the same version. Which is causing a bit of grief.
I enjoyed Antiarc's interview and was all prepared to point to it for evidence that Omen was stable and we didn't have to stress about versions anymore. But unfortunately he said
The absolute best way to get things running smoothly is to make sure you have the whole raid group running the same revision, the more recent the better.
Which while true, will only encourage folks to drive themselves crazy with updates more often.
I think the best solution is to have occasional stable releases. But as folks point out above, we all love to use WAU to update. Another solution would be to have the Omen versioncheck not check the actual revision ID of Threat, but instead some "compatibility" version number that's only manually incremented on backward-incompatible changes. But that causes other trouble.
Another solution would be to have the Threat-2.0 versioncheck not check the actual revision ID of Threat, but instead some "compatibility" version number that's only manually incremented on backward-incompatible changes. But that causes other trouble.
Threat-2.0 already does both such checks since the last incompatibility update amount a month ago. On logging in, it sends out a query, stating its version number and last compatible version number. Everyone that receives this will then know the version of this person and whether he is compatible or not. Then a reply is sent back to the person telling him his version and last compatible version number.
Based on all this information, Threat-2.0 then knows who is incompatible, and you can easily see this by doing a version check in the config menus.
I have run into a problem, I have had to switch to a computer that uses Vista. Omen worked for a week but seems to have disappeared.
It shows to be installed, I can check it in the addon list, etc. It just doesn't appear anywhere. I've tried using /omen config, etc. to bring it up but nothing has happened. Any suggestions?
I don't use Vista, but judging by the billions of posts describing issues just like yours, I'd advise moving WoW outside of the Program Files directory. If you're willing to do a bit more research, you can leave WoW in the Program Files directory if you set the correct permissions on it, and/or disable Vista's UAC; as I don't use Vista, I know nothing more specific about UAC or what might be appropriate permissions. If you don't know anything either, you're probably better off just moving WoW outside of Program Files.
after finally finding out how AOE Mode works (this is really user unfriendly designed, hard to understand what the numbers mean without any explanation)
The "layout" is like this in AOE Mode:
'Name' 'Aggro in k' 'Number'
Most people don't understand AOE Mode, and here is why:
1. Name is clear.
2. 'Aggro in K' - ok, thats my own Aggro. But wtf i can't compare it to the tank! how much aggro has the tank! heeeelp
3. 'number' - <insert random number here>? no - turns out it's actually a % number, relative to the tank
once u know what the fields mean, its easy to understand. but to get to this point...
so here is my suggestion:
2. 'Aggro in K' - change it to difference vs Tank! (Tankaggro minus own aggro = displayed number)
if you are above tank, make the bar red, if you are below tank, color it green
3. 'number' adding a %-sign would probably really help people ;D
I'm still having problems changing the appearance.The frames overlap and I can't get the drag on the lower right corner of the frames to open it. Is this a Skinner problem or Omen?
My guild has noticed what appears to be an issue with Omen:
On the Nalorakk fight in ZA, we have a both our Pally and Warrior tanks swapping aggro on Nalorakk for each phase. They taut off each other each time he changes forms. However, the taunt doesn't seem to be registering properly with Omen, as the Pally (who tanks the bear form) never jumps up to the Warrior's threat within Omen, even after the taunt succeeds.
It's not a huge deal, as the raid knows to simply stay below the warrior for the entire fight and they should be good, but it does seem to be a bug.
I don't use Vista, but judging by the billions of posts describing issues just like yours, I'd advise moving WoW outside of the Program Files directory. If you're willing to do a bit more research, you can leave WoW in the Program Files directory if you set the correct permissions on it, and/or disable Vista's UAC; as I don't use Vista, I know nothing more specific about UAC or what might be appropriate permissions. If you don't know anything either, you're probably better off just moving WoW outside of Program Files.
Hmmm hadn't thought of permissions issues... you could look at files that do work and make the permissions match those?
1. what does (F) mean on a bar?
2. What does the purple color mean?
3. what does the "miss direct" symbol on a bar mean? seems to go with purple color?
That feature has not been implemented in Omen2 yet. Be patient, Antiarc has said it will be coming.
May I bump this "issue" ? Yesterday got crushed by Gruul because I didn't see myselft going over the OT.
If I had pull out the OT's bar just in the middle of my screen, it would have been much easier ^^
Healer Mode grow up does not work right. It's jumpy, sometimes it grows up but brings the bottom bar with it while trying to print bars where it things the bar area is, etc.
Bumping as well - Pull out aggro bars are a defining feature of Omen.
I miss this feature, please accept our humble bribery of gnome tears to put this feature on the front burner. :)
Quote from Choumarin »
May I bump this "issue" ? Yesterday got crushed by Gruul because I didn't see myselft going over the OT.
If I had pull out the OT's bar just in the middle of my screen, it would have been much easier ^^
This is not ok. People use wowaceupdater to update all wowace2 mods. Developers should use other tools or at least make the updater pull stable branches. Don't commit broken software. If I have to go to curse to get working verions of Omen it would be easier to delete it and use ktm instead so that way I can use the updater for other addons.
I can't believe people are still going on about this. My guild was severely annoyed as well and actually had everyone disable Omen for a night in Hyjal, but it's been weeks now since Omen/Threat broke backwards compatibility.
I do agree that truly unstable/broken stuff doesn't belong on the SVN trunk, but I haven't seen a version of Omen/Threat that qualifies as broken or unstable - just incompatible with other versions.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI have run into a problem, I have had to switch to a computer that uses Vista. Omen worked for a week but seems to have disappeared.
It shows to be installed, I can check it in the addon list, etc. It just doesn't appear anywhere. I've tried using /omen config, etc. to bring it up but nothing has happened. Any suggestions?
Thanks
Ah well... all just update 30 min before raid and you're good to go.
Omen rocks :)
maybe the monitor setting is much lower than on the first computer, and Omen needs something to make sure it's not positions off the edge of the screen? I've seen other mods end up off screen when I go from my Tower !920x1200 to my laptop 1440x900 (moving the mods and saved data over) Some mods are smart and know their relation ship to the screen edge, some are not. I haven't played on my laptop in months, so I don't know if Omen is or not.
Me neither. I'm perfectly happy pulling the latest version from WAU (or SVN, for that matter). And I know that it's OK for people to be running slightly different versions of Threat and except for that one bug a few weeks ago, it will work alright. But I'm a software engineer who understands this stuff. All I'm saying is that there's a lot of superstition about software and a lot of people feel it's essential to have everyone on the same version. Which is causing a bit of grief.
I enjoyed Antiarc's interview and was all prepared to point to it for evidence that Omen was stable and we didn't have to stress about versions anymore. But unfortunately he said
Which while true, will only encourage folks to drive themselves crazy with updates more often.
I think the best solution is to have occasional stable releases. But as folks point out above, we all love to use WAU to update. Another solution would be to have the Omen versioncheck not check the actual revision ID of Threat, but instead some "compatibility" version number that's only manually incremented on backward-incompatible changes. But that causes other trouble.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThreat-2.0 already does both such checks since the last incompatibility update amount a month ago. On logging in, it sends out a query, stating its version number and last compatible version number. Everyone that receives this will then know the version of this person and whether he is compatible or not. Then a reply is sent back to the person telling him his version and last compatible version number.
Based on all this information, Threat-2.0 then knows who is incompatible, and you can easily see this by doing a version check in the config menus.
I don't use Vista, but judging by the billions of posts describing issues just like yours, I'd advise moving WoW outside of the Program Files directory. If you're willing to do a bit more research, you can leave WoW in the Program Files directory if you set the correct permissions on it, and/or disable Vista's UAC; as I don't use Vista, I know nothing more specific about UAC or what might be appropriate permissions. If you don't know anything either, you're probably better off just moving WoW outside of Program Files.
after finally finding out how AOE Mode works (this is really user unfriendly designed, hard to understand what the numbers mean without any explanation)
The "layout" is like this in AOE Mode:
'Name' 'Aggro in k' 'Number'
Most people don't understand AOE Mode, and here is why:
1. Name is clear.
2. 'Aggro in K' - ok, thats my own Aggro. But wtf i can't compare it to the tank! how much aggro has the tank! heeeelp
3. 'number' - <insert random number here>? no - turns out it's actually a % number, relative to the tank
once u know what the fields mean, its easy to understand. but to get to this point...
so here is my suggestion:
2. 'Aggro in K' - change it to difference vs Tank! (Tankaggro minus own aggro = displayed number)
if you are above tank, make the bar red, if you are below tank, color it green
3. 'number' adding a %-sign would probably really help people ;D
maybe u could add such things to the option menu?
thanks in advance
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumOn the Nalorakk fight in ZA, we have a both our Pally and Warrior tanks swapping aggro on Nalorakk for each phase. They taut off each other each time he changes forms. However, the taunt doesn't seem to be registering properly with Omen, as the Pally (who tanks the bear form) never jumps up to the Warrior's threat within Omen, even after the taunt succeeds.
It's not a huge deal, as the raid knows to simply stay below the warrior for the entire fight and they should be good, but it does seem to be a bug.
Hmmm hadn't thought of permissions issues... you could look at files that do work and make the permissions match those?
1. what does (F) mean on a bar?
2. What does the purple color mean?
3. what does the "miss direct" symbol on a bar mean? seems to go with purple color?
I'm guessing it's your current Focus
ahh good catch. it very well could be
May I bump this "issue" ? Yesterday got crushed by Gruul because I didn't see myselft going over the OT.
If I had pull out the OT's bar just in the middle of my screen, it would have been much easier ^^
Healer Mode grow up does not work right. It's jumpy, sometimes it grows up but brings the bottom bar with it while trying to print bars where it things the bar area is, etc.
I miss this feature, please accept our humble bribery of gnome tears to put this feature on the front burner. :)