I've sent a pull request, based on the latest commit.
Sound: I'll look at the sound code, but I'm hesitant to put in anything that would be specific to any sound manager. I'll admit however, I have never looked at sound and I have no idea how that works. Happy to learn. Some type of generic sound event hook, or call would be nice.
I can understand your hesitant because if the sound engine is no longer supported, you will have to re-write the sound code.
However, using a sound engine will make your life much easier, you have default sound files that come with every installation (Prevent duplicates), an easy to use SDK with a lot of functions, advance memory management (Important if your project is big), etc. And we don't have a new Orbiter version every week :rofl: so it doesn't worth to use a generic solution.
If you still want a generic solution, you have
Enjo MFDSound++ library. It's based on Windows SDK so the sound works without any need to external engines. But it's very limited and doesn't contain advanced functions.
Re-entry: The procedure in the manual is just something I came up with and I have not tried that with the 2016 version. I have also not tried any of the re-entry MFDs that are available, I don't know how they would work. A re-entry program in the flight computer is something that interests me from a development stand point, so that is on the list. As well as ascent.
To re-enter, you need BaseSyncMFD to align the base, and AerobrakeMFD to perform the actual re-entry. AerobrakeMFD shows the expected trajectory to the touchdown based on AoA, as well as many useful data. It needs a data file for each vessel class. The way to create a data file described in the manual.
Documentation: <insert template developer excuse here
>
Documentation is very important. Without proper documentation, you are the only one who can use the vessel :lol:
I understand how bad writing a manual is, but it's really necessary for other users.
---------- Post added at 09:31 PM ---------- Previous post was at 09:12 PM ----------
Even with the updated, the gauges still not correctly displayed. Hover doors and airbrake are good.
Photos:
LH2 indicator doesn't appear.
LOX indicator is a little below the white dot (assuming it's the mounting point).