Too good to be true?

[MadMilitia]

I don't even see my mouse leave my screen, even when I use ground-target AOE on all 5 windows. In exceedingly heavy combat, I might see my cursor flicker, but it's still instantaneous.

You can also use mock mouseover where you don't actually send your mouse to the other window. You simply set up a region where moving or clicking your mouse at X,Y sends a keypress only to the slave and the keypress triggers a hardcoded macro. That is what I use for dealing with procs.

This most likely has to do with the way your setup is configured.

I'm a former grid user, so it makes the most sense for me to click what I think needs healed quickly. Now I use blizzard's raid frames with mouseover macros to eliminate the need for additional addons.

I'm curious to your setup. When you heal party or raid how do you deal with healer targeting?

[Khatovar]

I use mouseover for healing and rez. Mock mouseover for decursing, procs, cooldowns, interrupts. This is my setup

http://genus-industri.us/wp/2011/11/...ipt-v2-part-2/

[Ualaa]

I don't notice any heal lag, with a Repeater Region over a Grid Frame.

I'm using Grid + Grid Custom Layouts.
So my team (any composition of my toons) appear in column one (five toons).
And the rest of the raid in columns two through eight.

No pets show up, could add that but didn't want to.

With Grid you need Clique to interpret the clicks.

The Repeater Region sends the mouse stuff to only my Paladin on the Pally/4x DK team.
But it sent it to 3x Shaman on the Pally/Warlock/3x Elemental Shaman team.
On the 5x Resto Druids, they all got the mouse stuff.
Set it how you like.

With a Repeater Region and an identical grid frame across all toons.
You can drive with any toon.
And heal as effectively, as with the main toon.
Or at least as effectively as you configure your Grid.
On the Pally, Grid gets me (Set Focus, Clear Focus, Quick Heal, Big Heal, Cleanse).
On the Druids, Grid gets me heals on Left, Alt Left, Ctrl Left, Shift Left, Right, Alt Right, Ctrl Right, Shift Right clicks, and Scroll Up and Scroll Down; 10 binds instead of 5.

[Ughmahedhurtz]

If you've not seen it, or maybe it's just my hardware not being up to snuff, there is a good half a second when you move your cursor over a broadcast region that it takes to appear on the slave window.

Tell us about your setup. It sounds like you've got something funky going on. I had my healer in Rift set up with a click region (did not process anything until I actually clicked on something) and I never noticed any lag at all. It was effectively exactly like driving from the healer.

[edit] Correction: due to ISBoxer's awesomeness, it was actually faster than driving from the healer, now that I think about it.

[MadMilitia]

Tell us about your setup. It sounds like you've got something funky going on. I had my healer in Rift set up with a click region (did not process anything until I actually clicked on something) and I never noticed any lag at all. It was effectively exactly like driving from the healer.

[edit] Correction: due to ISBoxer's awesomeness, it was actually faster than driving from the healer, now that I think about it.

Q9650 core 2 Quad
WD Caviar Black 1TB
8GB Nvidia Ram
EVGA 780i
2x GTX nvidia video cards (device manager is showing 460 but they are not 460s. Generic driver I suspect). First card runs the display interface, second handles physics (for other games obv).
Razer death adder left handed edition
Logitech G510
Win 7

Standard AV running during the game play.


The latency between broadcasts is very prominent in that second. Even in a 3s game.

[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.

[Ualaa]

http://isboxer.com/forum/viewtopic.p...b49f593580e7c0

Although you can share the profile here or there.
Or in both places.

But that's how to share an IS Boxer profile.

[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

[Ughmahedhurtz]

I'm betting this is not CPU or memory but a leak in either a driver or some software you have installed, or possibly a bad keymap config buried in all those mapped keys you have(!). I highly doubt it's ISBoxer itself as I have yet to see anyone complain about ISBoxer having issues after long play sessions. For that matter, I can't remember any of the broadcasting software having reported issues with memory leaks, crashes or corruption once they were out of beta.

[edit] I do recall some folks having issues where a keypress in a high-pop/high-stress environment that triggered certain spells would be tough on certain video cards but yours doesn't seem to fit with my vague recollection of that problem.

[MadMilitia]

I'm betting this is not CPU or memory but a leak in either a driver or some software you have installed, or possibly a bad keymap config buried in all those mapped keys you have(!). I highly doubt it's ISBoxer itself as I have yet to see anyone complain about ISBoxer having issues after long play sessions. For that matter, I can't remember any of the broadcasting software having reported issues with memory leaks, crashes or corruption once they were out of beta.

[edit] I do recall some folks having issues where a keypress in a high-pop/high-stress environment that triggered certain spells would be tough on certain video cards but yours doesn't seem to fit with my vague recollection of that problem.

Well,

To summarize it when I stand in front of a portal or some other highly active graphical feature my setup slows to a crawl in single digit numbers when 5 boxing.

I don't see how that could be normal. Maybe my hardware is slightly overheating due to being on fan cooling. Thinking of switching to water cooled soon but don't want to water cool a setup I'm going to replace anyways.