Log in

View Full Version : [ISBoxer] repeater stops working for some slaves



jeepdriver
08-27-2011, 06:20 PM
Ive noticed that after a while playing, that my 4 and 5 slave slot will not show the arrow when I turn on the repeater, yet when I switch to those slots, and hit repeater it will show on all 5 slots, is there a way to fix this or is this a new bug?

Lax
08-28-2011, 09:45 AM
It sounds like the Repeater Target might be changed to something you aren't expecting, in that window. The only way this SHOULD happen is through a Repeater Target Action. There are other ways it changes, but they SHOULD be temporary -- Send Next Click, Repeater Regions, Video FX with repeater built in, etc.

You can force the Repeater Target back to normal if you like. In your Activate Repeat mapped key under Control, in Step 1 where it turns ON repeater, add a Repeater Target Action. Set the Target box to Window:Current, New Repeater Target to Window:All w/o Current, and don't check the "block" box.

Any Export to Inner Space will also reset it to its original state.

Apps
08-29-2011, 09:40 AM
Ive noticed that after a while playing, that my 4 and 5 slave slot will not show the arrow when I turn on the repeater, yet when I switch to those slots, and hit repeater it will show on all 5 slots, is there a way to fix this or is this a new bug?


Happened to me when I made a new group, and an ISB patch happened at the same time.

5th slave, didnt repeat, yet when I would client window swap to number 5, it was there.

Heres how I fixed it.
1. remove the existing region, and make a new one.
2. before you do the sync to all windows, save it as "Auto". (default)
3. close the interface window.

It should work when you start up. Sometimes, a window doesnt get updated when the patches go through. I dunno why. It should be operating off the same lavish/ISB program. But Ive only ever seen it happen once.

jeepdriver
09-04-2011, 04:52 AM
Sorry for getting back to this so late, but its not a region or anything that messing up. What happens is when I click on the Mouse repeater icon (the 3 boxes with A on them) Some windows will have the little finger cursor show up and some will not. :) This only happens about an hour or so into play.....maybe Isboxer is tellin me to get off my ass and do something else for awhile ? :)

Heres something new, I swapped out my druid for another shaman, put her into the team etc...now the only window with the finger cursor is that window (window 4) and Window 4 is the only window that will NOT repeat what I type! LOL

jeepdriver
09-05-2011, 10:06 AM
Got with Lax on this, fixed it right up :)

HomoDoctus
09-05-2011, 11:50 AM
mind sharing the solution? I've been having this problem the past week with some teams. Typically i notice it at login and just cycle through my windows with repeater on, but it will stop broadcasting an hour or so into play. might be a moot point though, doing a new comp build end of week if the parts arrive.

jeepdriver
09-05-2011, 04:16 PM
Youre gonna have to get with lax on it, I cant remember everything we had to do. :/

HomoDoctus
09-06-2011, 01:37 AM
no worries, doing a new build and fresh install of everything anyways, so i imagine it will fix itself.

jeepdriver
09-18-2011, 09:33 PM
well hell...it started doing it again, WTF lol

HomoDoctus
09-19-2011, 02:26 AM
that's annoying eh? After building my new rig everything is fine, with the exception of the log in screen. I still have to activate repeater and then shuffle through the screens a few times to get the mouse to show up on all of them. I'm sure Lax will get you sorted out again :)

best of luck, and try to document the steps this time (in case it happens again).

Apps
09-19-2011, 09:06 AM
ya know, if you log in too fast... that "sometimes", and I do mean rarely, when you click the button to broadcast mouse in all windows, will it not work for one or two.

What I do in those VERY RARE cases, is to
1. turn off the repeater.
2. do the window click swap for each window. I.e. If I am on window 1 of 5 total, I will click on 2, then 3, then 4, then 5, then back to 1.

After that the repeater works as intended. Again, this is VERY RARE, and to be blunt, I havent seen this hiccup / glitch since the last update.