Too good to be true?

[Ughmahedhurtz]

Forgive me for not being more clear. I meant your ISBoxer, HotKeyNet, etc. setup. As in, how do you have your keys bound, what macros are you using, how does your broadcasting software control your alts, etc.

[MadMilitia]

Forgive me for not being more clear. I meant your ISBoxer, HotKeyNet, etc. setup. As in, how do you have your keys bound, what macros are you using, how does your broadcasting software control your alts, etc.

I see.

I usually stick to 1-9, -, = to be clear. I only use isboxer unless I'm grid/cliqing from the tank or dps perspective.

The macros are all standard cast with mouse mods. Meaning, clique is told to cast healing wave on left click, GHW on right click.

I put the repeat region over the grid/clique setup then make sure it is broadcasting to my healer. This all works as expected for the most part.

As soon as I hit the wall (thinking this is cpu related), the whole thing starts experiencing noticeable latency.

I've ditched one video card to see if that was the issue. I've tried testing memory and also checking the hard drive for failures or hard swaps.

I don't do anything out of the normal wizard setup and the repeater region that is documented clearly. The only distinction might be the wow macros I use in the client itself which are standard mod macros like:

#showtooltip
/castsequence reset=6 riptide, healing wave, healing wave

Or

#showtooltip
/cast [mod:rshift]Totemic Recall;Call of the Spirits


Pretty basic stuff. If I had to pick a culprit it would definitely be the Q9650, which just hits the wall hard on 5s and seems to hit the wall during intense 3s.


Ualaa,

http://www.privatepaste.com/b62534a937