Direct Gimbal control support upstream (via mavlink - we can pass on some details about this if needed).
Adsb dongle support (currently only supported via onboard Adsb)
Importing maps (can only import maps that were exported by qgc can be imported).
Locking access to parameters (with a password pane). Biggest thing we’ve seen is people changing things they shouldn’t and often by accident.
More control over the checklist (should be able to be specific although that might be a wip already).
Use only degrees during landing convention. % and degrees intermixed is chaos for people who don’t know what the difference is and how to convert from radians etc. one thing only to be consistent.
Scaling min speed by actual mtow from baseline - we have extensive testing on this and the backend math done for ourselves but would be great for other users to use and put into qgc.
Much more clarity (toggle) in the planning view on what the flight plan estimate will be when taking turning radius into account since we are rounding things out while flying.
Wind estimates pulled in from any of the public sources. Good for people to know that don’t have a anemometer.
Illustrate (just with a number or letter) which gps unit is being used for multi gps enabled systems.
Probably a lot more out there. That’s just off the top of my head.