Captain Campion

If the next upgrade demands the addons to be updated, how many third parties will come back to patch their products? How many users will upgrade to the next version then? P3D is in a very complicated position now. Customers demand updates, but LM must be really careful with said updates.

Try waiting a little more, i had the same problem but now that i wait for 3:50 or something it always works.

They declared the intention to release it this year when FS2020 wasn't under the radar (have been anxiously perusing my calendar ever since) so i wouldn't call them opportunistic. I really really hope they get this plane right, i want their Learjet with Proline 21 too.

Switched it to Fluffyflops if i'm not mistaken

Hello. really loving this product, but i'm having problems with PM turning off engine 2. Of seven flights i have only managed it once, and can't figure out what the problem is. After landing i exit the runway and stop the plane, follow the after landing flow and make the after landing checklist. However when i say "shutdown engine 2" nothing happens, even when i can read in the green text that the message has been understood. Only once managed to get the PM to obey the command (and he turned the electric pump afterwards). I use the chrono to ensure the 3 minute cooldown period, any help appreciated with this. What does the program check for this procedure?

Don't forget FS2Crew , 90% finished according to Bryan York.

Do you integrate the latest changes in ATSU functionality?

Fantastic, eagerly awaiting further developments 👍

Patch is out, anything to share?😋

My brother's been testing and looks like EZCA is the culprit. He started a flight and during climb ATC was nagging him to reduce speed to 250...when he was climbing at 180/200 knots. he used the global disabled option to quit EZCA and then ATC went silent and the flight went smooth. Looks like there's a conflict between these two products and it messes with the airspeed (looks like true airspeed is much higher than indicated airspeed). That would also explain why FS2Crew goes silent at takeoff...if true speed is indeed higher than indicated then the 80 knot mark may already be surpassed as soon as the plane starts rolling for takeoff...even V1. And it would also explain my overstress crash. I'll report this in the EZCA forums.

Hello I want to check if other people has encountered the following problem. I have started suffering it since last week after many months without issue. I have my suspicions on two programs wich are the only thing i have installed lately: EZDOK3 and the last Activesky Prepar3d patch. The problem is this: i get overspeed warnings even when my flight speed is way below the red tape. The first time i suffered it when descending at 240 knots at FL100, and it was the end of my flight (stress damage). I have disabled stress damage but overspeed messages keep appearing. I have tried disabling EZCA effects to no avail (but i could be doing something wrong, i'm not used to this new version yet). Sadly the Majestic forums are down (an annoyingly usual recurrence lately) and i can't check if there's any topic on it. Anyone has experienced this with the DASH? My brother has started flying it in his rig and he also gets the overspeed messages (he uses EZCA3 and Activesky too). FS2Crew voice edition is acting strangely too, after i start the takeoff and say "check power" the FO responds and then goes silent, not acknowledging the 80 knot mark, positive rate or anything afterwards. This must be related to the above problem, both started simultaneously. Any help appreciated.

I have received an email from them and i'm currently downloading it

Oh yeah, there's Carenado, wich i won't touch with a 100 foot barge pole...and that's it.

I really wish Flight1 would upgrade their Citation Mustang. After they released the King Air i expected it would follow soon after but alas nothing...Prepar3d is sorely missing a modern bizjet (and by modern i mean 1980s forward).

Great photos! Wich scenery are you using for Fez?