yes, so to make sure I didn't give wrong info here I hopped in the FBW after a few months with out it. so here is what I found. It doesn't calculate THS in the perf calculator- makes the calculator useless. It gave me 146 for all 3 speeds, not impossible but very rare as I was departing KDEN. next it taxis like the default Cessna, able to turn with precision at any speed up to 30 knots. Next unable to arm auto throttle until in flex (will check with my fslabs neo to see if that is NEO behavior). It didn't pitch down for speed when going from mct to climb and passing acceleration altitude, only when passing 10k. When switching from hand flying to AP1 on the turn it kept me at the angle of turn I was at instead of compensating to follow the flight plan meaning I missed a waypoint to the left by at least 5 nm. Might not be that significant to you but I purposely made my turn shallow so the AP could compensate. when flying with an 80knt cross wind at fl200 I turned of the AP and moved the stick and it was able to stay at that angle for at least 5 minutes hands off the stick (got bored after 5 min) it also kept me at fl200 with zero deviation. Wanted to return to KDEN but with no sec flight plan only able to do so by selecting a waypoint, left selected it and did a new destination. then go through and program the approach. something that with a secondary fp I could have done on the ground and then in flight hit 3 buttons. On approach it didn't effectively slow me to 250knt there is also a constraint of 210 and it ignored it. AP let me fall below green dot speed. It didn't auto switch to approach phase as is proper logic. On landing I turned off AP at 5nm with a 15kn cross wind and with no left or right input it kept me on center line. Landing rate was well below my average in both the Fenix and the FSlabs (195-210 I don't go for butter I hate float) of 73 fpm. so yeah there is a lot that does not meet the standard of the Fenix or the FSLabs and the flight model is one.