v1.1.0 - New API for multi-parameter Events, SU10 SDK updates.

Changes since v1.0.0

Updates for MSFS 2020 SU10 changes and new event trigger API for sending multiple values.

WASimModule

• Added new feature to trigger simulator Key Events with multiple value parameters (Gauge API trigger_key_event_EX1()).
• Removed ability to get or set Local type variables with Unit specifiers (turns out MSFS hasn't supported this from the start).
• Added Key Event lookup names for new KEY_PROP_FORCE_BETA_* events.
• Added Token variable name lookups for CIRCUIT_NAVCOM4_ON and BREAKER_NAVCOM4.
• Remove usage of deprecated send_key_event() for SendKey command in favor of trigger_key_event_EX1().
• Module is now built with /clang:-O1 optimization level (the newly-recommended O3 level revealed a nasty MSFS memory corruption bug which should be fixed in SU11; I will have an update after SU11 release).

WASimClient

• Added sendKeyEvent() methods for sending simulator Key Events with up to 5 values, either by event ID or by name.
• Unit type specifiers for getting/setting Local variables are ignored (no longer sent to the server even if provided in the method call).

WASimClient_CLI

• Added sendKeyEvent() methods (see above).
• Added .NET Framework 4.6 and .NET 6.0 targets/builds (pre-built DLLs added to SDK distribution).
• Re-targeted project for VS2022, MSVC v143.

WASimUI

• Added new form for sending Key Events with up to 5 value parameters.
• Added connected WASimModule (server) version number display.
• Fixed that the calculation result display text field could not be cleared.

Shared Components

• Minor optimization fix in SimConnect exception reporting module during lookup of a cached request record (for logging exception details).

---

The release contains several download options (the actual file names have version numbers appended):

• WASimCommander_SDK - All header files, pre-built static, dynamic, and managed (.NET) libs, packaged WASM module, pre-build GUI, reference documentation, and other tools/examples.
• WASimModule - Just the WASM module component, ready to be dropped into a MSFS Community folder (so that the folder wasimcommander-module is inside the Community folder). MSFS would need to be restarted after adding the module for the first time.
• WASimUI - Just the GUI application, which is very handy in combination with the WASM module for exploring the system. No installer, simply unzip and run the WASimUI.exe file from either Explorer or a command line.