@delta558 thank you. Preliminary testing since the update and the issue seems to have been fixed. Thank you.
I will let you know if it pops up again, but I am pretty sure it is fixed. I do need to fly the Arrow more to be sure.
@bobsk8 It seems that you've missed the point of this thread.
As I said, I know I'm not bouncing because I've watched it in Sky Dolly (no guessing) and my landings are smooth. It's the touchdown sound that makes it sound like a bounce that is wrong.
@scnrfrq1 You need to turn on the NAV radios first in order to be able to turn on the COM radios.
I think they should be able to be turned on independently but I think I recall JF saying that's a limitation of MSFS.
https://community.justflight.com/topic/2972/com-nav-issues/11
@delta558
I'm only an end user but beeing also an real life glider pilot I have some understanding of aerodynamics. Obviously it is completely different perspective since I use MSFS for fun not as a training tool. It's always nice to have plane behaving as real as possible, but I'm not going to fly pa28 in real life.
Maybe I'm just used to the fact, that all PC simulators have been more or less inaccurate in the past - especially when close to stall conditions.
But I understand how much extra work is required to model fde correctly under these circumstances - with no guarantee that the internal flight model will not change in the next MSFS update.
@jmcrowe01 The HSI is using the default 'NAV CDI:1, number' and 'A:NAV GSI:1, number' variables for those needles, or 'A:GPS WP CROSS TRK, nautical miles' and 'A:GPS VERTICAL ERROR, Meters' if operating in GPS mode.
The ASI TAS scale position will be included in state saving in the next update.
Unfortunately I can't find any information on the radio/avionics lighting.
