Our records show that you have outstanding author rewards points. Please confirm your latest payment information and redeem your points balance via the Author Reward Store.
Why does compatibility keep getting broken though. It's very frustrating.
Previously an Omen from 3 months ago would work just fine with earlier versions.
Now, omen from 1 day ago won't even work with recent versions. What gives?
Omen from 3 months ago was a mature product with months and months of development time behind it. Omen 1 day ago is a highly volatile project that is undergoing heavy development to work out bugs that have shown up in practical raid usage.
I can't use any of the dropdown menus in the config dialog, because is is cut off on the right (Perhaps only in the german version?). Can you please tell me, whats broken?
I am getting threat values far higher than another rogue in my group while doing similar damage. Comparing the values to the damage i have dealt and with the threat behavior pre 2.4 i think there is something pushing my shown threat higher than it should be. Sometimes i don't even pull aggro with 150% tank threat.
I have already tried resetting my settings by deleting everthing related to Omen in my WTF directory. I am always doing clean instals through the updater.
Antiarc-
The hunter issues seem to mostly be resolved, as far as pet threat goes...as long as you're in close range to the pet. I'm not sure what the range cutoff is, but I noticed if i'm at max range, the pet threat isn't reported correctly. Going to poke at it a bit this weekend and see what the functional range is. Looks like 20-25 yards is the maximum right now, but that's just guessing.
Again, thanks for your work on this mod.
-caet
Why is every new version incompatible with its previous version? This addon gets updated like every 5 minutes and whenever people log on with newer versions it screws it up for raids because we can't see them on our version and so we waste more time logging out, downloading the newer version, logging in to find out ours is now higher than theirs, then someone DC's 10 mins later and logs on with an even newer version that's incompatible with the rest of the raid!
Other than that it's a fine addon and I'm glad there's a way to get rid of all the excess stuff that came with the first new release at 2.4
Why is every new version incompatible with its previous version?
It hasn't been every new version. To the best of my knowledge (and I update daily) there have been two versions that broke compatibility since 2.4 went live, and both of those versions were incompatible because of bug fixes. In other words, they couldn't fix the bug and remain compatible.
I can't use any of the dropdown menus in the config dialog, because is is cut off on the right (Perhaps only in the german version?). Can you please tell me, whats broken?
The Blizzard menu isn't big enough. You can:
a) use /omen config to configure Omen, or
b) Install BetterBlizzOptions, an addon I threw together yesterday to let the Blizzard options dialog be movable and resizable.
I can't use any of the dropdown menus in the config dialog, because is is cut off on the right (Perhaps only in the german version?). Can you please tell me, whats broken?
The Blizzard menu isn't big enough. You can:
a) use /omen config to configure Omen, or
b) Install BetterBlizzOptions, an addon I threw together yesterday to let the Blizzard options dialog be movable and resizable.
I am getting threat values far higher than another rogue in my group while doing similar damage. Comparing the values to the damage i have dealt and with the threat behavior pre 2.4 i think there is something pushing my shown threat higher than it should be. Sometimes i don't even pull aggro with 150% tank threat.
I have already tried resetting my settings by deleting everthing related to Omen in my WTF directory. I am always doing clean instals through the updater.
This was a bug that could have shown up specifically for rogues after multiple enable/disables of the player module. It should be fixed now.
It hasn't been every new version. To the best of my knowledge (and I update daily) there have been two versions that broke compatibility since 2.4 went live, and both of those versions were incompatible because of bug fixes. In other words, they couldn't fix the bug and remain compatible.
This is correct. It's not really fair to say every commit breaks backwards compatibility - there were a few that did it, but they were done in a short timeframe and early on in the project's lifecycle to get them out of the way as soon as possible.
The alternative was to leave crippling bugs in that would have been bad for everyone.
Though this might be more of an Ace3 issue, I wanted to bring it to light.
When I go to the bar texture dropdown, the list appears but is too large to fit on my screen and am unable to shift the list down. I am using the basic Shared Media library. I want to select a specific texture that is below the cutoff line of my display. If you look in my left chatbox, you can see that I attempted to use the command line options to no avail. That particular command doesn't seem to be implemented.
EDIT: Make it clear that scroll wheel does not work. It is not an implemented event in Ace3.
Though this might be more of an Ace3 issue, I wanted to bring it to light.
When I go to the bar texture dropdown, the list appears but is too large to fit on my screen. I am using the basic Shared Media library. I want to select a specific texture that is below the cutoff line of my display. If you look in my left chatbox, you can see that I attempted to use the command line options to no avail. That particular command doesn't seem to be implemented.
Scroll wheel does not seem to work for me for scrolling the list of bars (I have the same issue with wanting to use one at the bottom of the list). Omen 1 using RockConfig would do it, but the new config just doesn't here, and it Omen 2 doesn't seem to show up in RockConfig... so I guess I'll be editing saved variables to get it set.
BugSack showed thousands of the "invalid order function for sorting" error last night. Don't know if it's related, but the top row (with the column titles) kept switching back and forth with the second row (which simply contained "<none>"). Everything threat-related seemed to be fine, though.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumOmen from 3 months ago was a mature product with months and months of development time behind it. Omen 1 day ago is a highly volatile project that is undergoing heavy development to work out bugs that have shown up in practical raid usage.
Please explain what each of new omen mods(target,AOE,healing) for?
Regards,
Christian Stadler
I have already tried resetting my settings by deleting everthing related to Omen in my WTF directory. I am always doing clean instals through the updater.
The hunter issues seem to mostly be resolved, as far as pet threat goes...as long as you're in close range to the pet. I'm not sure what the range cutoff is, but I noticed if i'm at max range, the pet threat isn't reported correctly. Going to poke at it a bit this weekend and see what the functional range is. Looks like 20-25 yards is the maximum right now, but that's just guessing.
Again, thanks for your work on this mod.
-caet
- Omen Dependency Downloads
- Ace3
- LibGUIDRegistry-0.1
- LibSharedMedia-3.0
- LibSink-2.0
- Threat2.0
Is this suppose to happen. I was under impression only version of Threat2.0 you want is inside the omen folder?
Other than that it's a fine addon and I'm glad there's a way to get rid of all the excess stuff that came with the first new release at 2.4
It hasn't been every new version. To the best of my knowledge (and I update daily) there have been two versions that broke compatibility since 2.4 went live, and both of those versions were incompatible because of bug fixes. In other words, they couldn't fix the bug and remain compatible.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe Blizzard menu isn't big enough. You can:
a) use /omen config to configure Omen, or
b) Install BetterBlizzOptions, an addon I threw together yesterday to let the Blizzard options dialog be movable and resizable.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe Blizzard menu isn't big enough. You can:
a) use /omen config to configure Omen, or
b) Install BetterBlizzOptions, an addon I threw together yesterday to let the Blizzard options dialog be movable and resizable.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThis was a bug that could have shown up specifically for rogues after multiple enable/disables of the player module. It should be fixed now.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThis is correct. It's not really fair to say every commit breaks backwards compatibility - there were a few that did it, but they were done in a short timeframe and early on in the project's lifecycle to get them out of the way as soon as possible.
The alternative was to leave crippling bugs in that would have been bad for everyone.
When I go to the bar texture dropdown, the list appears but is too large to fit on my screen and am unable to shift the list down. I am using the basic Shared Media library. I want to select a specific texture that is below the cutoff line of my display. If you look in my left chatbox, you can see that I attempted to use the command line options to no avail. That particular command doesn't seem to be implemented.
EDIT: Make it clear that scroll wheel does not work. It is not an implemented event in Ace3.
Scroll wheel?
Use the scroll wheel on your mouse.
I have the same issue in new Omen 2.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium