For the developer, programming the WASM modules comes with its own quirks, too, not to mention the time involved.Īnd regardless of the supposed isolated environment a WASM module is supposed to run in, it's still very easy to take down the whole Simulator with Multiple versions of modules which all do eseentially the same thing, and it may be confusing which WASM module they need to support which tool,
There is nothing wrong with this, of course, but for the Sim user it can be a disadvantage on several levels. One of the motivations for this project was seeing multiple MSFS tool authors and casual hackers creating their own WASM modules and protocols just to support their "transport" layer, but this usage is abstracted into, essentially, an implementation detail. To SimConnect for basic functionality like reading/setting Simulation Variables or triggering Key Events. The system also provides direct access to functions from within the Simulator environment and in many cases could be used as a simpler alternative NET managed assembly from C#, Python, or other languages. The Client API can be utilized natively from C++, or via. Inaccessible via SimConnect, such as locally-defined aircraft variables or custom events. This project is geared towards other MSFS developers/coders who need a convenient way to remotely access parts of the Simulator which are normally Remote access to the Microsoft Flight Simulator 2020 "Gauge API."Ī WASM module-based Server and a full Client API combination.
0 kommentar(er)
