Hello, do you confirm that CTRL SHIFT and ALT mapping via
MapInputEventToClientEvent doesnt work at all ? @FlyingRaccoon
MapInputEventToClientEvent CTRL+ KEY ALT + KEY SHIFT + KEY doesnt work . Fabio
Hello @Kartijno You want to use VK_LCONTROL , VK_RCONTROL ,
VK_LSHIFT , VK_RSHIFT , VK_LMENU and VK_RMENU instead.
@Nocturne will fix the wrong examples in the doc and we’ll try to provide a
list of entries you can use. Regards, Sylvain
Hi @FlyingRaccoon , thank you so much for your help ! Fabio
I wanted to reopen this issue, because while the modifiers DO work, they
cannot be used to differentiate between a key and the same key + modifier.
Have a look at the slightly modified InputEvent sample from the SDK: I
modified it to have the brakes triggered when pressing z and the parking
brakes when pressing shift-z What happens, instead, is then pressing z
triggers the brakes, while shift+z triggers both brakes and parking brakes,
which makes adding modifiers basically useless, since they are commonly used
as alternative function for the same key.
InputEvent.zip
I would also like to report the same findings - is there any way we can get
this looked into, as it would really help with adding key events with
modifiers. @FlyingRaccoon @Boris
It would be oh so very nice if we could get a looksie into this bug please…
@EPellissier @Boris @FlyingRaccoon Thanks all!
Is there any way this bug could be given some Tender Love and Affection please? It renders any key input useless if modifiers (Shift/Ctrl/Alt) are to be used, as the underlying keys are also “pressed” that way…
@EPellissier @Boris @FlyingRaccoon
According to what I know, key input for WASM modules doesn’t work very well at this time because any keyboard input that you intercept, is still forwarded to and processed by the simulator.
Yes, that’s also something that we’ve noticed (the “Maskable” flag isn’t respected at all), however, that’s a separate issue from the Modifier keys not being respected.
Without trying to sound like a pest, I am wondering why this issue has not been given any replies from the devs, or at least an indication that it is on the radar.
It is starting to feel that reporting becomes less meaningful as some issues get immediate attention and others are completely ignored despite repeated tagging of support personnel. A quick reply of either
“this is on the backlog”
“this is being worked on” or
“we’ll not implement this”
will go a long way in ensuring the communication path is not broken between 3rd parties and Asobo devs.
1 Like
Yes, they are different things indeed but, in fact, having the modifiers not respected makes the lack of the “Maskable” flag even more problematic because, it makes it easier to end up with conflicts/double-events because, if we could at least work around those by using uncommon combinations of modifiers to reduce the chance of a conflict with a default key, with the modifier not working to create an unique hotkeys combinations, it’s even worse.
1 Like
Just to reiterate that this issue is not fixed in SU14 beta…