Error upon launching ISBoxer Suite

[Aerandria]

Hey, first post on the forums here. I'm new to ISBoxer and I'll be looking around the forums here today in an attempt to get a grasp of this program's incredible depth. I'm trying to setup ISBoxer for 6 EVE Online accounts and the number of potential options and configurations has me a little overwhelmed.

Before all that, however, I'd like to see if anyone happens to know what this error message indicates.



It occurs when I attempt to open ISBoxer Suite.
ISBoxer Suite will open just fine and appears to function despite the error.

So basically I'm not sure if its even a problem, but I figured it would be good to get out of the way before I go in-depth with asking configuration questions.

[lax]

You have an Input Device that happens to be producing corrupted data for Inner Space's InputDevices.XML file. Send me this file -- C:\Program Files (x86)\InnerSpace\InputDevices.XML -- to lax@lavishsoft.com and I can solve the problem permanently. Temporarily, you can delete the InputDevices.XML file after sending it to me

[Aerandria]

You have great customer service

I've sent the requested file, let me know if you have any problems with it or need additional info.

On a completely unrelated note, I'm trying to find a method of syncing my interface configuration across all my accounts for mouse click cloning purposes. Is there any simple method or utility that could assist with this task?

[Alge]

On a completely unrelated note, I'm trying to find a method of syncing my interface configuration across all my accounts for mouse click cloning purposes. Is there any simple method or utility that could assist with this task?

Yes, see the FAQ.

[Aerandria]

Thanks! That was super useful.

On another note, is it possible to use repeater regions on a monitor of a differing resolution from the main display?



The left side is a Catleap Q270 running at 2560x1440 resolution (27"). The right side is a 32" TV running at 1360x768, so although the right side looks smaller due to vastly lower resolution its actually physically quite a bit larger.

I play on the left side and rely on information from the right.

It's a great system as it is, and I'd be fine with this level of utility.

Ideally, however, I'd have everything you see on the right side fully interactable, but I can't find a way to make it work with the resolution differences.

[Alge]

Is that a dxNothing window on the right hand monitor with Video FX viewers in it? If so, I'm not sure why you are asking about Repeater Regions. Do you mean as an alternative? My experience with Repeater Regions is that they work best when the resolutions match. You may get acceptable results in your case though. There is something you can do to make things better by naming the Repeater Regions, though I am not clear on the details.

I would suggest using a Stacked Window layout on your main monitor and then a dxNothing window on your secondary monitor. That dxNothing window can contain Video FX Viewers (either parts of windows or whole windows) which are fully interactable.

[Aerandria]

Is that a dxNothing window on the right hand monitor with Video FX viewers in it?

Yup!

If so, I'm not sure why you are asking about Repeater Regions. Do you mean as an alternative? My experience with Repeater Regions is that they work best when the resolutions match. You may get acceptable results in your case though. There is something you can do to make things better by naming the Repeater Regions, though I am not clear on the details.

As an alternative to what? I wasn't aware there was another method, besides basic broadcasting, but I don't see how that would work here. Am I missing the most obvious method, again?

I would suggest using a Stacked Window layout on your main monitor and then a dxNothing window on your secondary monitor. That dxNothing window can contain Video FX Viewers (either parts of windows or whole windows) which are fully interactable.

Yup, I have all 6 clients running via Stacked Window layout on the main monitor and, as you say, a dxNothing for management on the secondary. The only part I'm missing is the interactivity.

You have an Input Device that happens to be producing corrupted data for Inner Space's InputDevices.XML file. Send me this file -- C:\Program Files (x86)\InnerSpace\InputDevices.XML -- to lax@lavishsoft.com and I can solve the problem permanently. Temporarily, you can delete the InputDevices.XML file after sending it to me

I deleted the InputDevices.XML file as suggested, and, as you mentioned in the e-mail, I updated my InnerSpace with the development patch. Unfortunately, I'm now getting a fairly serious error that I don't recall having experienced before the patch. When using my hotkey (page up and down) to insta-swap between clients I now frequently (but not always) end up with stuck keys. I don't believe its a physical problem with the keyboard, since it seems to be coinciding with the most recent patch, and I'm not having any similar issues outside of ISBoxer. To be clear, I press Page Down and instaswap to a new client. That client thinks that my Ctrl key is being pressed. If I swap to a new window and immediately try to interact with it, I often experience serious issues as a result. Worse still, sometimes entire sets of windows think that their control keys are being depressed even when I'm not using them directly, and my broadcasted commands get completely fubared.

The issue is resolved by entering any client with the issue and pressing my Ctrl keys.

[Alge]

To make your Video FX viewers fully interactable, ensure "Repeater pass-thru" and "+ Keyboard" are selected in the Video FX Editor. You will then need to click "Apply" in the Video FX Editor and "Save As" in the ISBoxer Control Panel.

[Aerandria]

Thanks, got everything interactable! This is basically everything I wanted from ISBoxer

Unfortunately I'm still having the sticky key issue. Anyone else using the dev patch having similar problems?

[Aerandria]

The sticky key problem is being a pretty big problem. If I get could get some recognition that the issue is being addressed in some way I'd appreciate it

Let me know if you need any files from me.