Isn’t it wonderful that you get to fly those planes in both sims? If that was the only reason for you to fly 2024 then I guess you don’t have to any more! ![]()
I’m flying in 2020 and didn’t expect them to come across from 2024.
Absolutely delighted with the Albatross. Cessna Titan looks interesting, but I already have a lot of very good twin engine prop aircraft.
Kind of surprised A2A didn’t put the Aerostar out on both sims, perhaps 50% of the market lost.
Not sure where you’re getting your information from about the A2A Aerostar, but I understand there are FS20 and FS24 versions available.
Thanks for that!!!
Read so much on ‘t’internet’ I have no idea where it came from. Absolutely no idea where/ how I thought that.
Good news, I’ll buy it fairly soon, bad news I keep trying to stop spending.
Also it’s still surprising that they chose the Cessna 404 over the Cessna 421 and 402C for career mode aircraft that could have been more utilized in free flight than the 404
All depends on what aircraft the developer had the best access too. These are built on a budget, plus time is money and deadlines change so they usually model the aircraft they have easiest and cheapest access to.
It does not seem correct.
I’ve made a bug report a while ago.
This may be my bad, but are the range buttons on the Titan 404’s Garmins the wrong way round in MSFS2024? They seem to be the opposite of the same plane in MSFS2020.
Probably. The 172 Garmin is the same. I mentioned it on working title’s discord ages ago, and got some half ■■■■■ answer. Those people are low on my respect ladder, for such an easy fix. Just zero care.
I’m fairly certain that control is done by the aircraft developer and is not related to the avionics themselves, which is why it’s correct in some planes and incorrect in others, despite them both using the same Working Title 530/430 package.
So two default sim planes have the same problem? Maybe others. So who is responsible?
Whoever developed the plane itself, not the avionics.
Edit: Well, to be more clear, Microsoft is ultimately “responsible” as they’re the owners of the product. They would need to contract the work necessary (either from the aircraft’s original developer, such as Asobo, Carenado, Got Friends, etc or to a different one) to fix the issue.
In the default cockpit camera position, the lights on this devices are off, but when I zoom in a little bit, the lights go on and then zoom out, they go off…
Is anyone else not getting full power on takeoff? Sea level and I’m only achieving 37”MP & about 2100 RPM, instead of the rated 40” & 2235 RPM.
I dearly wish Asobo would un-encrypt the performance files so we could make improvements.
Also, I’ve just noticed that even though the 404 has a slaved compass system, the HSI experiences significant gyro drift. To make it worse, the compass controls on the top left of the instrument panel are non functional, so it’s impossible to correct the drift manually.
I’ve only today just seen your post regarding the incorrect button logic on the Garmin on this aircraft and the 172 classic.
I reported this issue via the correct procedure back in May 2025. It eventually got bug-logged status (after some cajoling of the staff) but is still not fixed after SU4. It’s hard to believe it only has 12 votes (as of this post) but I guess that’s why it remains low priority and unfixed.

