stuart wrote:(I'd be interested to see how their G1000 simulation compares with the FG1000, but I think you'd need quite deep familiarity with the Garmin manuals to determine which is correct.)
FWIW, since you're the one most likely to be familiar with the FG1000 specifically, here's a review of the G1000 variant as implemented in X-Plane (obviously, we don't currently support synthetic vision, at least not until the Canvas View element and/or the Compositor is fully reviewed and integrated):
Also, reviews covering specifically the G1000 in MSFS 2020 are currently showing up on youtube:
The first impression is that from a purely technical standpoint, we're in comparison well equipped with the Canvas system - but we could obviously use a few more dedicated Canvas primitives for things like chart rendering (think GeoPDF/ESRI), synthetic vision (Canvas View/Compositor), and elevation maps computed from actual scenery tiles.
At that point, we would at least have all the building blocks in place to allow people to implement modern avionics, i.e. without them having to be C++/OSG coders.
Looking at garmin.com, it seems obvious that Jules' CompositeViewer work might have a huge impact on FlightGear's capability to model modern avionics - because modern cockpits routinely display a handful of independent scene views showing different overlays/features (i.e. stuff which simply isn't easily done using just Nasal and XML):
https://www.garmin.com/en-US/blog/aviat ... ight-deck/Regarding the VSD at the bottom of the center display, I am not sure if any of our Canvas avionics have implemented a generic VSD already or not, but there's plenty of related code already.