• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

New Project: Structured SDK Docs Import for Events/SimVars/Units

MaxPaperno

MaxPaperno

Messages
32
Country
us-newyork
Hello,

I just published a new OSS repository to collect some MSFS-related things I’ve been working on for other projects, but I think can be useful in general. These are intended for other MSFS developers.

One of them is an effort to import all the Event IDs, Simulator Variables, and Sim Var Units from the HTML-formatted MSFS SDK Documentation into something more structured, like a database. Original intention was for use in a user-facing UI (where the user can select events/vars they want to use, or for example to know which Unit types can be substituted for each other).

But it also revealed a number of inconsistencies between the docs and WASM-side (Gauge API) KEY_* macro names, which it seems maybe no one really knew about before. There's a link to the relevant devsupport discussion in the project README.

There is also a little C++ utility in there for tracking SimConnect exceptions. Perhaps more to come.

Anyway, the project is at https://github.com/mpaperno/MSFS-Tools

As always, feedback, errata reports, or any other contributions are welcome.

Cheers,
-Max
 
You must log in or register to reply here.
Top