• 0

    posted a message on Omen2
    No settings are being saved still for windows background color and border color. Someone mentioned swapping to an alt, load skin or profile and swap back. That only worked because they had previous saved variables that worked on another toon. Please delete all saved variables from all your toons and look into this. This seems to only effect colors of default window, title window, module window, and bar window. Again changing one of them effects all of them at once. However no setting is being saved for any of them. It just reverts back to default values. options.lua it looks like. Background textures, border textures and text do however save individually.

    Oh i might add that all of the Show When... settings seem to work great. Gonna be some happy mages, locks and hunters. Autocollapse also. :)

    BTW i didn't notice a problem with hunter threat. If it was broke it seems fine now. Didn't test range of feign death over 25 yards though.

    It's getting there Antiarc and Nevcairiel and the others helping. Much appreciated.
    Posted in: Raid AddOns
  • 0

    posted a message on Omen2
    Also background color and border color changing any 1 thing ie just title color effects everything ie title color, module color and bar color. Also it does not save at all now. You'r stuck with default if you swap toons or log out then back to the same toon. Saving the skin doesn't do anything either. You may need to delete old saved variables to notice this. I'm not sure as i usually delete old saved variables while a mod is still being worked on. version 68050
    Posted in: Raid AddOns
  • 0

    posted a message on Omen2
    Shouldn't there be a releasebar for always show self like the title bar has? Or is that what's causing the above error? Something to look into.
    Posted in: Raid AddOns
  • 0

    posted a message on Omen2
    Antiarc replace line 292 in SingleTarget.lua with this correction please.

    name = OL["Color"],

    with

    name = L["Color"],

    This will make your personal bar color selection actually show the correct color and transparency in the configuration gui. I know i know not a huge fix. But i'm doing my part. That's 2 for me now. :)
    Posted in: Raid AddOns
  • 0

    posted a message on Omen2
    Doesn't remove itself from my map. Do you use a map mod of any kind? If so list which one. Also there are option for fubar. Are they selected?
    Posted in: Raid AddOns
  • 0

    posted a message on Omen2
    I get an error in FrameXML log too many OMEN Headers or whatever. Existing omen Bindings file looks like this.

    <Bindings>
    <Binding name="OMENTOGGLE" description="Toggle the Omen window" header="OMEN">
    Omen:Toggle()
    </Binding>
    <Binding name="OMENNEXTMODULE" description="Show the next Omen module" header="OMEN">
    Omen:CycleModule(1)
    </Binding>
    <Binding name="OMENPREVMODULE" description="Show the previous Omen module" header="OMEN">
    Omen:CycleModule(-1)
    </Binding>
    </Bindings>

    The correct way should look like this?

    <Bindings>
    <Binding name="OMENTOGGLE" description="Toggle the Omen window" header="OMEN">
    Omen:Toggle()
    </Binding>
    <Binding name="OMENNEXTMODULE" description="Show the next Omen module">
    Omen:CycleModule(1)
    </Binding>
    <Binding name="OMENPREVMODULE" description="Show the previous Omen module">
    Omen:CycleModule(-1)
    </Binding>
    </Bindings>

    Not a programmer here. But the 3 instances of header="OMEN" isn't correct. All but the 1st header need to be removed. Not sure if this is the correct way to do it. But if not it's damn close and i don't get errors now. Toggles between modules fine also.
    Posted in: Raid AddOns
  • 0

    posted a message on Threat-2.0 / Omen2 - request for PTR testers
    Quote from Antiarc »

    It should be significantly more efficient due to the deprecation of the ParserLib requirement. Omen2 itself is a complete ground-up rewrite, so I'll be taking the opportunity to optimize where possible.

    There is a certain flat rate of overhead that is going to exist with threat meters; there's a lot to handle. However, if Omen is impacting peoples' framerates that badly, something is significantly off. Do you have any benchmarks or other information I could take a gander at?

    I have no benchmarks except fraps. Since we desperately wanted to use Omen and still do we tried disabling all mods. We made sure running proccesses were at a minimum. Tried new video drivers also. The only common thing was people with older systems with older cpus were suffering the single digit framerate. Like me using a P4 3.2extreme edition cpu and an ATI X1900pro agp video card. Normal framerate is between 28-300 and in 25 man raids can drop to as low as 28fps in some areas. With Omen 6-8fps was about average framerate on those bosses where i'd get 28fps. With the peole using older systems a 16-18fps hit was the most common. People with newer systems would suffer only a 6-8fps hit. But the newer systems were running higher average framerates so they'd never drop down to single digit framerates. So i could only up with the conclusion that either Threat1.0 was too cpu intensive or Omen1.0 was somehow slowing it down.

    I'm not posting this to make Threat or Omen look bad. I'm posting this info in hopes that you all can figure out what's wrong or make them both more efficient. My raiders want to use threat and Omen desperatley and i do too. We will try Threat2.0 and Omen2.0 in a raid in hopes that it's improved. Good to know about the deprecation of the ParserLib requirement. Hopefully and i'm crossing my fingers here that that helps a lot and resolves the issue. Looking forward to trying Threat and Omen again.
    Posted in: Raid AddOns
  • 0

    posted a message on ag_UnitFrames Status (What's going on?)
    BTW absolutely love the raid layout and most especially love party targets. Show's me who's on the wrong mob and who's not following assist when i'm tanking. Perhaps i can save a few more deaths now. This is what a mod should do. Make you a better player and not just look good. This mod does both well.
    Posted in: Unit Frames
  • 0

    posted a message on ag_UnitFrames Status (What's going on?)
    Are you even using the ace 3 version? I'd guess no as you got [config] is not a valid option. Get tortoisesvn from http://tortoisesvn.net/ and get get the aguf ace3 version goto http://svn.wowace.com/wowace/branches/ag_UnitFrames/Ace3/

    select player or tot or tott, etc etc,
    Frame attributes tab
    Style/border/width/height/scale
    under that is has this
    ----BAR height modifier----
    cast/mana/health selectable
    0.1-3 variable for each

    Posted in: Unit Frames
  • 0

    posted a message on Threat-2.0 / Omen2 - request for PTR testers
    Antiarc is some of the code for threat2.0 and or OMEN2.0 updated to be more cpu friendly ie more efficient? I'd love to use OMEN2.0 but if this isn't the case some of our raiders will be dropping to single digit framerates and we won't be able to use OMEN2.0 which is our current situation with OMEN1.0. Please tell me it's an improved more efficient version.
    Posted in: Raid AddOns
  • 0

    posted a message on PitBull 2.0
    I finally gave up on Pitbull. Main gripe was party rames not refreshing so having to constantly type /reloadui during raids. Also the mod keeps getting more and more bloated. A few other problems too. I'd probably have stayed with it if some of the old problems were fixed. But i've been ignored and i'm rather annoyed at that also. Rather things worked that was already in the mod instead of adding more stuff to screw it up even more. The mod looks damn sweet. But it's usefulness it metiocre at best. Sorry CKknight but you really need to fix some issues here.
    Posted in: Unit Frames
  • 0

    posted a message on ag_UnitFrames Status (What's going on?)
    There's an option to change bar heights already built in, unless you're talking about somethig else.

    I must say i'm loving this mod. I finally got off my lazy arse and got a svn client and grabbed this mod. I was getting so frustrated with Pitbull not refreshing party frames and raid/target icons being incorrect and numerous other problems i had to try something else. I'm a minimalist and Pitbull is like the opposite of minimalist. SO damn bloated it drives me nutz.

    I only have 1 suggestion. Er is there any way to disable my target from what looks like fading. Guess it's supposed to indicate that i'm in combat or i have aggro on this mob or something. I like the colors i have now. I'm not a fan of this fading on my target or whatever it is. It just doesn't look right. Might even call it highlighting although i have highlighting turned off. Other than that everything else seems perfect.

    Having a mouseover frame wouldn't be a bad idea if it has an enable disable button like the other frames. I know it seems like it can be a waste. But lots of us warriors do use it for multi mob tankig along with our mouseover devastate macros. Makes it easier to do this with a mouseover frame. But if you don't want to include it that's fine by me. I'd rather this mod stayed more simple than bloated. So i can live without it.

    Great mod and much thanks dude.
    Posted in: Unit Frames
  • 0

    posted a message on Omen - Bug Reports and Suggestions
    I must first congradualte the people that made Omen. I think it's laid out well. Visuals and TPS were working as they should for our raid. The multi mob tracking ability were nice. But it was a trial for our raid. We were hoping it was the new patch that was causing our fps loss. Well tonight we went back to KTM and our fps went back up. I don't know if it's Omen using too much cpu and if it's too much bandwidth being used or what. But atm we can't use Omen as is. I say this in hopes that you will look at your code and possibly optimise it some more so it'll be viable for us to use again. Carry on your excellent work. :)
    Posted in: Raid AddOns
  • 0

    posted a message on X-Perl 2.3.8a Double MT list
    It isn't an X perl problem. It happens when you run ora or pitbull or as far as i know just about any addon that has an MT and Assist boxes. The problem is the Blizzard pullout tabs. Far as i know no addons address this issue. Unlike some i'll actually attempt to solve the problem. The problem lies in the user at some time in a raid pulled out the blizzard tabs and now it's saved. Some people tried theese steps.

    wow/interface/addons/Blizzard_RaidUI delete this folder. Personally this didn't work for me.

    wow/wtf/account/accountname/savedvariables this is the folder that has lots of .lua saved files. Look for Blizzard_RaidUI.lua and change it to look like this. Line 1 is blank btw so make sure you use a carriage return. Also hit a Carriage return for line 6 as line 7 is also blank. This should save the blizzard raid frames to not being pulled out. This worked best for me.


    RAID_PULLOUT_POSITIONS = {
    }
    RAID_SINGLE_POSITIONS = {
    }

    With notepad 2 showing line numbers it looks like this.

    Line 1
    Line 2 RAID_PULLOUT_POSITIONS = {
    Line 3 }
    Line 4 RAID_SINGLE_POSITIONS = {
    Line 5 }
    Line 6

    Now also look for other areas that also have the position saved. Such as wow/wtf/accountname/server/toonname/savedvariables. Look for and in all folders in the wtf folder for your savedvariable settings that has that blizzard_raidui.lua saved variable and change them all to as i've shown. You could also try creating a L1 toon and copy it's blizzard_Raidui.lua saved variable. As it should look like my example above. Then use that to copy past over all the other blizzar_raidui.lua saved variable files you have. For me this in a total of 11 files i replaced.

    Some people have also tried deleting the blizzard_raid addon and all the blizzard_raidui savedvariables. Doing both didn't work correctly for me. I suggest just changing the saved variables.

    Now your next problem may be having ora and xperl both showing mt frames. Have ora mt frames set to ZERO to only show xperl mt frames. Or vice versa. ALso ct raid i think does this too. I hope ct raid mt frames doesn't use the blizzard pull out frames or you'd have to start all over. Pretty sure they don't. A caution though. Never ever pull out a blizzard raid frame or you're back to square one.

    I think that since you want to use the ct raid MT list you may continue to have this problem. I'd suggest putting ora mt list to zero and not using the ct raid mt list and just use xperls mt list. That's the easier fix imo and may not require the changing of the saved variables. Hmm nope that still requires changing the saved variables. Play with all the settings. Trust me you can and will figure it out.

    A fix to all this would be for all theese addons to have a setting to change the Blizzard_RaidUI.lua saved variables. I don't know of any that currently do this. It would be a nice option is pitbull and ora and xperl had this option to save the blizzard raid settings. But alas nobody has it coded in yet. Seems like a real simple fix too. But they'd all have to have that fix or at least all the mods you use.

    Also just try changing ora to showing zero MTs and zero assists and that may keep the x peral mt frames from showing up possibly. It's worth a try anyways.
    Posted in: Unit Frames
  • 0

    posted a message on Omen - Bug Reports and Suggestions
    Well i've gone thru a lot of addons and updated them. Running bugsack and only get 2 erros now. Omen errors when i change tps update freq because it resets threat and threat has a nil value. Don't know why you'd want to reset threat when you're only changing the update freq. But i don't think that should hurt anything. Only other error i get is a random Pitbull error maybe once a day. That's it no other errors and my framexml log looks fairly clean along with bugsack. I'll try some new video settings too. My comp may be old but i always got good framerate before. ATI 1950XT shouldn't drop me to 8fps. BTW i post in other forums besides here where i use thier addons with error reports or my observations or both to try and figure this fps issue out. I don't just point my finger at 1 addon. The other addon modders at least gave constructive feedback and looked at thier stuff and did find problems and have fixed thier problems. Maybe not completely. But at least they're trying. I don't see any comment at all here saying "We're looking into it and updating our code". Reminds me of Blizzard.
    Posted in: Raid AddOns
  • To post a comment, please or register a new account.