I’m using the MSFS SDK and SimConnect to intercept events like COM_RADIO_VOLUME_INC or COM_RADIO_VOLUME_DEC. I want to handle these events in my client application and prevent them from being processed by the simulator.
How exactly should I use SimConnect_AddClientEventToNotificationGroup and SimConnect_SetNotificationGroupPriority to ensure the event is blocked and not passed through to the simulator?
Which priority value should I use to fully intercept and consume the event?
This is one of those Simconnect-related items that we’ve posted about since day 0 (i.e. alphas/betas of MSFS2020 before it was even released).
In a nutshell, priorities and blocking never has worked properly in MSFS.
No idea why, while promised, it was never given the attention required.
One time, I even got a “why would you want your app to block events? That’s for the sim to decide” response from one of the devs…
Thank you for your reply — I really appreciate the insight.
Based on my own testing, I was already starting to suspect that event blocking wasn’t actually working as intended, so your message helps confirm that.
It’s a bit disappointing to hear that this has been a known issue since the early days and still hasn’t been addressed, especially since the ability to block events could be really useful in some scenarios.
At the very least, the documentation should be updated to reflect this limitation — it would save developers a lot of time and confusion.
Thanks again for taking the time to share your experience.
As per @EPellissier 's request, I am reviving those Simconnect issues that I think need attention asap.