Just doing a bit of testing on an (open source) fully automated flight --meaning auto-takeoff, waypoint-based flightpath, with terrain follow, and auto landing, using simconnect so it’ll work for planes that would never in a million years be outfitted with any of that-- from Duncan, BC, to Port Alberni and I have to admit…
There are worse ways to run a test!
Also the actual science looks pretty cool. Monitoring sixteen different flight properties to figure out whether I need to change anything and where.
Though, the real enemy is the end of the flight.
Not the auto-landing itself, that part’s actually quite doable (if not what your flight instructor taught you), and it’s not cross winds (although auto landing in cross winds is a universally bad plan), nor is it traffic on the runway, or runway slope…
no…
it’s this.
Random trees at the end of the runway. Seriously, just why. The first real MSFS2020 package I wrote was “removing a bunch of trees because omfg why” for a local runway.
We just about made it, though!
I mean… we’re powered off in the middle of a runway instead of having taxied off, but unless Microsoft starts supplying SimConnect with airport diagrams, auto-taxi is not going to happen ; )
…
And when I say “planes that would never in a million years […]”, I mean it. Ever flown a Top Rudder 103 Solo—an ultralight that by all accounts just cannot ever be outfitted with even basic autopilot functionality—with a full auto flight package?
Because it’s amazing.
Best way to enjoy Tahiti. If you remember that there’s only so much vertical speed to be had!
And just for good measure: 4K Top Rudder goodness, but at Samsumg Oddysey G9 aspect ratio!
(I’ll take 49" super ultra wide screen with TrackIR over VR any day of the week. I like being able to look down and see my actual controllers)