ISBoxer.com

I'm having a couple of issues with in-game shortcuts. These issues don't happen when I run EVE from a stand-alone client so it's definitely ISBoxer/InnerSpace related.

* If I'm typing in a chat box and the chat includes a character mapped as a shortcut, the shortcut will activate... For instance, lets say I want to type the following in Local.
"Can you please give me the build for that? It seems it might work, like quite well."

... then the following will happen...
C - My camera stops tracking
A- remapped to Approach, so my ship might start approaching something (I remapped all nav keys to make them easier to remember)
G - custom mapped as drop drones, so a rack of drones gets dropped
V- Direction scan will activate
A- approach again
B - Probes will start scanning if deployed
D- ship might dock
F - Mapped as Fire drones so better check my safeties
R- Ship might start "Keeping at Range" (remapped same reason as a)
S - Ship might allign (remapped same reason as a)
, - Custom mapped as decrease probe zoom
q - ship might start orbitting (remapped because "q" is closer to the first letter of 'orbit' than 'approach' which was remapped as 'a')
w - ship might warp
. - probe area zooms out
So yeah... pretty damn annoying

* Additionally, If I'm typing something in a box other than a chat box, say a contract description, or a mail message, if I type a space, the focus will swap to one of my chats and continue there. If I hold down "shift space" the focus will stay on the contract description or whatever it is I'm typing into.

Things I've done to try and fix/investigate:
- Ran game as stand alone client - issue resolved, so it's definitly in ISBoxer
- Reset my in-game keymaps to default (no difference)
- Checked cache (no difference)
- Unplugged keyboard and used inbuilt laptop keyboard (no difference)
- Loaded a backup profile from years ago (before this was an issue) (no difference - so while it's definitely ISBoxer related, it's not necessarily the profile that gets exported to InnerSpace.

Profile pastebin
https://pastebin.com/jTQH4hHR

Any help would be appreciated.... I swear I'm gonna lose a rack of geckos this way, or uncloak a covie... or something !!


Tragedy strikes after Meathead writes up a contract

Did this problem start recently? Are you on the development build of Inner Space? If you are, does switching to the live build solve the issue?

If not, then you should try going into the game without ISBoxer, open the chat box, and type those same keys while holding Alt (repeat with Ctrl if necessary. Shift should not be in question here as it is used for typing...). I can't imagine any other reason why the game would process hotkeys while you're typing in a chat box or other text control within the game. The keys in question are not even related to your ISBoxer configuration, so there's nothing in ISBoxer that I can say "oh just turn off X and then it wont do that when you press C" -- this config is no different than everyone elses, it's almost default.

If that does NOT make the same behavior occur without ISBoxer, then we may have to start looking at Compatibility Diagnostics (http://isboxer.com/wiki/Diagnostics) to try to find the ghost in the machine.

Just to follow up with this, I have the exact same issue! And it caused me to accidentally ECM burst on the Amarr undock while I was typing, lol.

Something causes the game to register the typing as both entries into the chat box AND activate a module. It started very recently (last month or so I think)....I've always had my keybindings the way they are and never had issues.

I can confirm that it works 100% fine with the non-development build of Inner Space. Something in the development build causes this issue!

Thanks, that is the information I needed. I will see what I can find out before these changes go live

Inner Space build 6279 is now available as the development build of Inner Space. This build includes a possible fix for this issue -- please give it a try and let me know. Thanks

Word from the ISBoxer Discord is that Inner Space build 6279 has indeed resolved the issue. If you continue having this issue, please post again. Thanks!