Issues with EQ2 and PIP switching - Clients stop responding

Machine info:
Vista x64 w/SP1
Intel Quad Core @ 2.7ghz
4gb ram
ATI Radeon 4860 or something like that
Running dual monitors, left @ 1280x1024 and right @ 1680x1050


Software:
InnerSpace w/ISBoxer


Group comp:
3 characters, using PIP



Repeater config:

Using whitelist/blacklist atm. Have whitelisted 1-=, CTRL, ALT, SHIFT, and Q E Z V G. F-keys are not whitelisted.

Other details:
Currently have "hot character" switch bound to CTRL+F1-F3. On switch, ISBoxer is broadcasting a number associated with a /follow and /target macro on each client. This allows me to switch between characters without having to re-follow and re-target manually.

I haven't started configuring things in detail yet, so I've done a very basic setup using ISBoxer. I've created a team, put my chars in the team, set up regions, and the repeater. ISBoxer is configured to "force" EQ2 to the foreground as I understand EQ2 needs to believe it's in the foreground in order to process input.

Since I'm just using a repeater, I've been switching between "hot characters" using CTRL F1 - F3. When I switch, the other characters will, rather frequently, stop responding to input. In order to get them to start responding again, I have to switch to that character and spam some inputs. While I'm attempting to get the character to respond again, I can mouseover items in-game and bring up tooltips, but keyboard input and mouse clicks will not register. After a bit of mashing the keyboard, the character will usually start responding again.

I believe that either the Repeater is not working properly, and the "buffer" is overflowing, or that EQ2 is realizing that it isn't in the foreground and suspending input.

Has anyone run into a similar issue or have any input on this?

I've searched the forums but could not find any similar problems reported by other users.

Any ideas?



The only thing I've been able to think of so far is that I have CTRL set on the repeater whitelist. If IS isn't sanitizing its inputs, then this key would be broadcasted and may not be properly interpreted, resulting in the other clients thinking that I'm still holding CTRL down.



I'm going to try a keymap setup when I get home this evening.

Well, your guesses are wrong as far as why the input stops responding, but this is a known issue with certain configurations of Repeater (attempts to fix so far have only been able to mitigate the issue). Instead of using Repeater 100% of the time, you should create Mapped Keys in one or more Key Maps instead. This will give you greater control, and will help you avoid this issue (though yes is a little more work). Otherwise, it is best to disable Repeater before switching in order to completely avoid this issue.

Quote:

---

Originally Posted by 'Lax',index.php?page=Thread&postID=208122#post2081 22

Well, your guesses are wrong as far as why the input stops responding, but this is a known issue with certain configurations of Repeater (attempts to fix so far have only been able to mitigate the issue). Instead of using Repeater 100% of the time, you should create Mapped Keys in one or more Key Maps instead. This will give you greater control, and will help you avoid this issue (though yes is a little more work). Otherwise, it is best to disable Repeater before switching in order to completely avoid this issue.

---

Thank you for the response. I had an inkling that Repeater was causing the problem, so I think I'm going to go ahead and create keymaps. I was only using Repeater as a band-aid solution while I get my characters out of the newbie levels.



Just for posterity, I'll post in this thread if keymaps fix the issue.

I went through and configured all of my keymaps last night. After about 4 hours of work, I can say that IS and ISBoxer are absolutely amazing.



PIP switches near-instantly, no client hitches, and I actually have some fine control over my other characters outside of just repeating keys.



Thanks for the help. Your software is great!