TFDi released a new update (I think currently only to Collector's Edition owners, I guess public release will follow very soon) which really improved pitch stability / trimming behaviour. There are still things that can be improved / fixed, but after a test flight, it felt way better than before, controlling the plane was way more "believable" and hand-flying was fun. Didn't felt like I was just an "observer" anymore like before, hoping the aircraft will somehow land on the runway while fighting the controls. Approach seemed very stable and managable. I think it's on a good way forward now.

Edited July 16, 20241 yr by roesti

That's great to hear. I was just thinking about the MD-11 today, wondering when the update is going to release. Hopefully some of the biggest issues mentioned in this thread will improve. 

I second the comment above - after the update things feel much better and I think most people will be pleased with the adjustments.

I'm still on version 1.0.1 😞 I have pre-sale edition from last year, no updates for me

The fact CE customers get fixes first for an undetermined amount of time as a perk is one of the strangest thing any flight sim dev has ever done. Weird.

36 minutes ago, ehrie said:

The fact CE customers get fixes first for an undetermined amount of time as a perk is one of the strangest thing any flight sim dev has ever done. Weird.

My take (as a recent purchaser) is they are treating the CE group as they are called as the primary QC team.  I’m not pleased with delay but I’m having a blast flying the 1.0.1 version and doing full auto lands and RNAVS and a host of other crazy daring pilot stuff! 😎😎😎

-B

Edited July 16, 20241 yr by btacon

49 minutes ago, ehrie said:

The fact CE customers get fixes first for an undetermined amount of time as a perk is one of the strangest thing any flight sim dev has ever done. Weird.

The perks for us ponying up the money a year before it was "ready" 😛

In all seriousness, it makes good sense. They have a small QA team who gets the initial new build. That then passes onto us CE customers, which is a much much larger group (and quite vocal in our CE area of their discord). This prevents builds from going to the full public with major patch induced issues. The opposite of this is like Flysimware does it...I will preface this that I own all the Flysimware planes in P3D and now in MSFS. HUGE fan of theirs. But he also tends to dump new releases multiple times a week/day at one point and this introduced a ton of patch induced errors/issues. Yes he reacts quickly, but if that went to a theoretical thousand customers for feedback before mass release the dumb little mistake would have been caught prior.

The CE patch is good. Much nicer pitch/pitch trim behavior. Colin has another small one incoming to polish some things and if that is good I think a patch encompassing both will be out for normal customers.

2 hours ago, CaptainNick said:

will be out for normal customers.

So we should have "abnormal" customers who pre-ordered a year ago! "Half-normal" customers who preordered November of the last year! And finally normal customers who just bought it 🤣

18 minutes ago, sd_flyer said:

So we should have "abnormal" customers who pre-ordered a year ago! "Half-normal" customers who preordered November of the last year! And finally normal customers who just bought it

I have to say this whole approach is one that I have never been comfortably with and a ready I have stayed on the fence regarding this aircraft.

According to a CE user I spoke to, TFDi team said that, after this update, their next 'big' issue to fix will be the N1 oscilations.

Changelog of updates for CE users for anyone interested:

1.0.5 (16 July 2024)
ADDED - Realistic parking brake engagement logic and option
ADDED - Altimeter sync setting and functionality
ADDED - AILERON DEFLECT OVRD code (button does not yet function)
FIXED - AUTOPILOT alert not playing on startup
FIXED - EVAC switch behavior with respect to the guard
FIXED - GPWS OVRD switch/guard not playing sound
FIXED - EVAC switch/guard not playing sound
FIXED - (P3D) EFB not applying DEFLECTED AILERON setting
FIXED - Horizontal alignment of vertical FMA
FIXED - Pitch stability and pitch trim flight performance
FIXED - ER buttons not animating
FIXED - Chocks preventing brake actuation
FIXED - PIP pylons not working
FIXED - Wingflex-related visual issue
FIXED - Gear handle release button not working
FIXED - Deflected aileron button not working
FIXED - Backward strobe lights
FIXED - Missing wingtip nav light
FIXED - Missing strobe ground flash
FIXED - Deflected aileron override button appearing with option disabled
FIXED - Gear handle animation
FIXED - Strobe timing
CHANGED - Improved display startup timing
CHANGED - Certain EFB settings saving to the airframe instead of user settings

1.0.6 (17 July 2024)
FIXED - PROF TO not showing in meters when meters are selected
FIXED - (P3D) Default GPWS conflict
FIXED - VS/FPA button in P3D
FIXED - Lack of fuel not causing engines to flame out
FIXED - Lack of fuel not causing APU to flameout
FIXED - Edge case crash in CAWS system caused by ADC power loss
FIXED - Spoiler toggle event only extending spoiler
FIXED - Engine start possible without air source
FIXED - Invalid RTE RSV FUEl entry when entered by weight
FIXED - VOR/ADF needles instantly snapping to values
FIXED - Canadian altimeter setting in MSFS EFB
FIXED - Missing FD1/FD2 annunciation on PFD
FIXED - CAWS alert power requirements
FIXED - MASTER WARNING/MASTER CAUTION/SD cue lights activating without DEU power
FIXED - ABS DISARM light not coming on when initially selecting AUTOBRAKE TO
FIXED - Windshield wiper INT behavior
FIXED - Windshield wiper timing
FIXED - AP heading bug not following aircraft heading on ground
FIXED - Brake behavior and baro sync options not being retained properly
FIXED - P3D EFB maximum fuel value not matching
CHANGED - Changed TCAS altitude calculation to attempt to resolve erroneous altitude reporting

i buy the product in Nov. I cannot get the update, crazy way to run biz!

If i had known this about the updates when i purchased the aircraft, i most certainly would not have. How can you have some customers getting updates, yet others that have paid the same money don't Crazy.

I purchased the aircraft during the pre-sale. Like Car147 stated, I also would not have purchased it had I known how TFDi were going to handle the updates/fixes.

I missed the part where it said Presale purchases had early access to beta updates? The updates listed above are not even the official release. I would rather have the final version that works then a bunch of betas that fix and break things as they make adjustments. 

While I get the frustration not having the update right now, I think there is some kind of misunderstanding.

These updates are not official yet and are in testing / QA. The order how people receive updates has always been the same from the start:

Internal QA -> CE Users -> Public. It is not like that CE Users get final updates which are "held back" for Non-CE users, it is more like CE users are part of the test process on a volantary basis. Which makes sense, since CE customers were part of this process when the plane was still in alpha (and barely flyable). Even then, internal QA had updates before CE users, eventhough these updates were far away from being polished. So during alpha it was the same situation with updates already in the pipeline, but CE users had to wait until it passed internal QA.

I think it's done this way to prevent disappointment about newly broken things. And indeed, the new update(s) broke a few things, even if minor. That is the reason they give it a few days. If these updates would have been released earlier, there would also be people who (rightfully) complain again why something goes out untested / not tested properly enough and I'd agree with them then. Like the release version.

To be fair, the upcoming update should have been the original release version. TFDi could made their lives easier by just holding back the plane a few weeks and everybody would have been happy.

Of course I can give only thoughts and no reason why it's done like that, but I guess for TFDi it makes sense, because the CE userbase is larger than their internal QA (large enough to have a good sample size of different setups), they helped testing the plane for quite some time which worked out so the developers have some reliable bunch of people who are enthusiastic about this plane and bought it way back when it was not even clear when and if this plane eventually arrives.

What they also did is offer CE users an option to "opt-out" of the test branch and switch to stable, to prevent people getting annoyed by unfinished updates breaking things. One could argue here they could also introduce some kind of "opt-in" for other people eager to help testing new updates and maybe I can make a suggestion to the devs and perhaps they consider it (no promises).

I can only encourage to remain patient, I'm very sure the update will come for everybody in the coming days / this week and it will be worth the wait.

Edit: There is now an ongoing discussion about this topic on discord amongst CE users, with pro and contra arguments allowing all customers accessing test builds. No staff response yet, my personal opionion is: Give everybody access, but only the devs can make a decision here, so let's see - but don't have high hopes.

Edited July 17, 20241 yr by roesti