question

I confirm, the joystick events created with SimConnect_MapInputEventToClientEvent cannot be masked.

Hello,

This is a known issue and our developers will have a look at it.

Regards,
Sylvain

Hello @virtuali
Our dev is looking at this but it's a bit more tricky as we're not sure we want to allow people to override all possible inputs and we also have to consider potential conflicts between several third party products.
I'll let you know when I have more info.

Regards,
Sylvain

I checked the latest SDK and, while the release notes say

• SimConnect_SetNotificationGroupPriority has been updated with the correct information

It doesn't seeem to be the case, since the relevant page says:

The SimConnect_SetNotificationGroupPriority function is written by the developer of the SimConnect client, as a callback function to handle all the communications with the server.

Which doesn't seem to be right, since that's not what that function does, the explanation seems to be just copied/pasted from the Dispatch explanation:

The DispatchProc function is written by the developer of the SimConnect client, as a callback function to handle all the communications with the server.

Even the sample syntax and the parameters list for SimConnect_SetNotificationGroupPriority is copied from the DispatchProc

The C++ Header file, of course, has the function declared correctly:

SimConnect_SetNotificationGroupPriority(HANDLE hSimConnect, SIMCONNECT_NOTIFICATION_GROUP_ID GroupID, DWORD uPriority);

Now, I would like to use this post to repost my last question about the Priority not working correctly, meaning it's not possible to mask an event to prevent it from reaching it the sim.

This feature worked well since FSX, and many developers relied on it. Without it, it would be extremely trick to achieve some things, which will invariably end in developers that really need it, to rever to strange hacks, hooking, and other questionable methods.

An example how this could be used:

An add-on simulating data input in the FMC might want to momentarily switch into a "keyboard input" mode, allowing the user to use the keyboard to enter text faster. Some hi-quality airplane add-on had this feature but, while for a traditional FMC it might just be optional, think about something as complex as an A350/A380, which has a REAL full size keyboard in front of the pilot so, what's best than just enabling the PC keyboard the user has to easily simulate the real thing in that specific input mode ?

So, please, try to reconsider your doubts about adding back the not-working Event Masking from FSX. This, together to the other big missing feature ( Simconnect_text text lines and Simconnect_text menus ) are basically everything still lacking in Simconnect to create some kind of custom UI interaction required by lots of add-ons which were successfull in FSX.

Hello @virtuali

Allow me to give a more complete answer on this.
First, we agree that third party developers should be able to define their own events and bindings. The examples you provided with the FMC is a good one, we can also think of very specific actions that don't exist yet and that third party developers would want to add.
But when this topic was discussed internally, we also agreed that we didn't want to do it the way it was possible in FSX and this for user experience reasons:
- what's the point of creating a control menu where you can modify the bindings and handle conflicts if any third party product can override these controls and potentially create conflict with each other.
- what if a third party product masking an input creates a bug, either involuntarily or because we add that input later on in the game?

That said, this subject is being worked on as we speak in a way that will allow that kind of features but integrated in a better way in the game. I can't give any more info than that.

Regards,
Asobo / Sylvain

@FlyingRaccoon , I'm all for improvements and reliability so, as long what we need it's available, it's not a problem at all doing it differently than on FSX.

Something like allowing add-ons to "publish" their own custom events, so they will appear in the standard Controls UI and users possibly reassign them just like the "official" events, would be a big improvement, and won't require every add-on having to handle key assignments in a different UI.

Hello,

just wondering if anything has changed in this - our internal testing is finding that setting the bMaskable flag is still not respected and events that are masked out in all other platforms (FSX, ESP and all P3D versions), are still propagated to the sim.

We'd really like this functionality fixed as masking events from the sim is imperative for us so that they are correctly handled.

We need this too. An update on the status of this feature would be appreciated.

Yes please, the current documentation seems to suggest masking is possible, so it's very confusing for us, and it's difficult to explain users that something doesn't work as it should because the SDK prevents to mask events, yet they check the docs and see it is. And, considering masking is allowed from JS, there's no point of not allowing it from Simconnect, since bad-behaving app can be written in JS too.

*bump* - is there a possibility for an answer on this one, perhaps?

Thank you in advance!