Too good to be true?

[Khatovar]

I put up with the setup because quite honestly, broadcast healing is horrible. I found it to be truly unreliable even on a very good piece of hardware.

I broadcast heal and have for years and it works beautifully. My broadcast healing is as reliable in multiboxing as it was soloboxing a healer, and I don't now, nor have I ever used a healing mod like Grid or Clique. All it is is HotKeyNet and mouseover regions. I know the same things can be done with ISBoxer via VideoFX or Clickbars.

Driving from the healer is always an option, but there's many, many users who run the healer as a slave with no issues.

[MadMilitia]

I broadcast heal and have for years and it works beautifully. My broadcast healing is as reliable in multiboxing as it was soloboxing a healer, and I don't now, nor have I ever used a healing mod like Grid or Clique. All it is is HotKeyNet and mouseover regions. I know the same things can be done with ISBoxer via VideoFX or Clickbars.

Driving from the healer is always an option, but there's many, many users who run the healer as a slave with no issues.

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.

To me, that half a second is life or death in an intense PvP or PvE encounter. Sending what you thought was a heal that went into that abyss of a half second can be a wipe easily.

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

[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