Strange issue since Isboxer 42 update

Hello all

I have a weird issue with the new Isboxer 42 version.

I'm using the same old Pro config, 5 boxing, 2 screens, with a DxNothing on my 2nd screen to display the 4 inactive clients, pretty simple.

Everytime I switch between clients, I send a specific "swap" (swap1, swap2, etc) keymap in order to destroy and recreate the VFX viewers in my DxNothing, and at the same time, I run a couple of WoW macros (High settings and Low settings) to apply changes on my graphic settings on the fly, nothing fancy, I use this technique for ages now (thanks to Mirai :p), and it works fine.

Well, almost fine, cause since 42 version, I have a small issue.

If I switch by using a click method on any of my 4 VFX Viewers, or if I use a focus -previous or -next action, or if I Alt-Tab, it's ok.
But If I switch by using any Global Hotkeys (Ctrl+Alt+1, Ctrl+Alt+2, etc) assigned to each Slots, the good old /follow {FTL} macro stored in my Game Helps WoW Quick Setup 41 don't work anymore on the previous active slot.
In short:
Slot1 active (foreground) : I hit my follow key, slots 2, 3, 4 and 5 are following prefectly, no issue.
Then I switch to Slot2 by using the Ctrl+Alt+2 hotkey (global): I hit my follow key again, and slots 3, 4 and 5 are following my Slot2 character , fine , but ... the previous active char, Slot 1, don't find its target and don't follow (I have a red error message in WoW 'You don't have any target")

But as I said previously, if I switch by using any other method (click on a VFX viewer, previous/next window action, alt tab, etc), no issue.

Even more bizarre, if I remove the Swap settings part of the Swap macros, it works fine again with the Global Hotkeys.
The 2 swap setiings WoW macro are pretty standart

High Settings :

Code:

-- Camera
/console cameraSmoothStyle 0

-- Distance
/console graphicsViewDistance 3

-- Environnement
/console graphicsEnvironmentDetail 3
/console weatherDensity 1

--Texture Filtering: 4x Anisotropic
/console graphicsTextureFiltering 4

-- Ground Clutter
/console graphicsGroundClutter 5

-- Render Scale
/console renderScale 1

Low Settings:

Code:

-- Camera
/console cameraSmoothStyle 4

-- Distance
/console graphicsViewDistance 1

-- Environnement
/console graphicsEnvironmentDetail 1
/console weatherDensity 0

--Texture Filtering: 2x Anisotropic
/console graphicsTextureFiltering 3

-- Ground Clutter
/console graphicsGroundClutter 3

-- Render Scale
/console renderScale 0.5

I've tried many things (change the Key combinations of the WoW macros, change the different Slots restricted Global Hotkeys, etc) and I haven't found any fix yet.

I'm using exactly the same character set as before the Isboxer update (even tried to reload a backup)
The only thing I haven't tried yet is to rebuild eveything from scratch but well, so many macros, clickbars, menus, key maps ... :p

So, is there anything new in relation with the Global restricted hotkeys, or WoW macros, or Do Mapped Key actions, or anything else.

It's not game breaking, but it's really ... weird

Any help will be greatly appreciated.

[lax]

It's 42 actually, but it's ok we get it I will say that nothing you're describing changed in ISBoxer 42.

It might help to see your configuration -- http://isboxer.com/wiki/Configuration_Sharing

Hi Lax, thanks for the "faster than light" reply and sorry for the "4.2" thing, fixed haha

Here we go : https://www.zerobin.net/?258f93ae3eddcf ... 2lE5ATaSA=

The issue is in the Swap SLOTX Mapped Keys.

Without the last "do Swap Settings" action, it works.

[lax]

That is interesting. I don't see anything particularly wrong config-wise.

Presumably what must be happening is that F11 must be getting pressed with either no modifiers, or a different set of modifiers than intended. This could somehow be related to the modifiers you are holding as you're switching windows (Shift+Alt); it is not unheard of for a bug to leave a key "pressed" in the game instance in that scenario. However, the Named WoW Macro Action should also be enforcing the correct modifier keys (as long as it does not end up being Held).

A couple other things it sounds like you could test.
1. Try disabling "make this hotkey global" for the Slot switching Hotkeys. What this will do is make the hotkeys only work from ISBoxer-managed game instances, not while you're using other processes (e.g. a browser), but it also means that Inner Space is managing the hotkey rather than Windows, and it might behave better for you
2. Disable the Hold option on Swap SLOT1, Swap SLOT2 etc. I don't think this will change anything in your current setup though, since "Swap Settings" is not set to Hold.
3. If you comment out the lines in the macros instead of disabling the Do Mapped Key Action, does it still occur? (This would indicate whether it is an issue with the commands in the game)

That is interesting. I don't see anything particularly wrong config-wise.

Presumably what must be happening is that F11 must be getting pressed with either no modifiers, or a different set of modifiers than intended. This could somehow be related to the modifiers you are holding as you're switching windows (Shift+Alt); it is not unheard of for a bug to leave a key "pressed" in the game instance in that scenario. However, the Named WoW Macro Action should also be enforcing the correct modifier keys (as long as it does not end up being Held).

A couple other things it sounds like you could test.
1. Try disabling "make this hotkey global" for the Slot switching Hotkeys. What this will do is make the hotkeys only work from ISBoxer-managed game instances, not while you're using other processes (e.g. a browser), but it also means that Inner Space is managing the hotkey rather than Windows, and it might behave better for you
2. Disable the Hold option on Swap SLOT1, Swap SLOT2 etc. I don't think this will change anything in your current setup though, since "Swap Settings" is not set to Hold.
3. If you comment out the lines in the macros instead of disabling the Do Mapped Key Action, does it still occur? (This would indicate whether it is an issue with the commands in the game)

Lax, you're my hero

You've found the issue, it's related to the modifiers.

I've changed the Shift+Alt+1, 2, 3, etc keys to some generic F1, F2, F3 etc instead, without any modifier, and it seems to work flawlessly.
So you're probably right, one modifier is maybe stuck sometimes in pressed position when the windows are switching.

It's weird because I've never seen this happen with any previous version of Isboxer, at least never noticed.
But since the patch, it's very noticeable.
And it never happens without the do Swap settings mapped keys (even with completely empty Swap setting keys, the problem still occurs)

I've tried your others options as well, but sadly, no effect.
(For the Hold option on the Swap SLOT1 , SLOT2 etc mapped keys, it was just a test, the option was disabled previously, but it doesn't seem to change anything in that case.)

So I guess I'll have to fight against my muscle memory, and learn to switch with F1, F2, etc instead of Alt+Shift+1, 2 I was using for ages
Or maybe exclude the LShift and LAlt from the /follow {FTL} macro modifiers, and don't use these 2 specific mods for the Slots ID ("FTL") Modifiers in the Switching tab of the Slots configs. (Not tested yet)

Thanks again Lax, and keep up the good work, your software is a gem