2 minutes ago, somiller said:

it's been there from the beginning, and nobody seemed to ever complain about it.

I have never noticed any pitch up, only after this update.

40 minutes ago, threexgreen said:

I have never noticed any pitch up, only after this update.

haven't seen any pitchup either before or after update. 

21 minutes ago, Bobsk8 said:

haven't seen any pitchup either before or after update. 

Me either, don't know how some are having this and others don't, I flew the 738 5 sectors with v3.0.105 and 2 with v3.0.106, without this bug. Although, PMDG (Mathis) is aware of this bug and said it was going to be fixed.

I've never noticed it either, but then again I don't really focus on that as much to be honest. If it does happen, I probably sub-consciously adjust for it as I try to aim for my point on the runway. I never have to make significant corrections on the control column so if it is there, it must be pretty minor

It was definitely a problem with version 3.00.105 of my PMDG 737-600. I am keeping my fingers crossed that it has been fixed in version 3.00.106. To be honest, I also saw evidence of a pitch up problem on departure. Interestingly, that was probably at a similar altitude to the short final issue.

5 hours ago, flyingscampi said:

I upgraded my -800 using Hub before I installed the 1.0.106 update and the tablet/FMC report the latest version.

...similar, I can confirm I updated through Hub AFTER 1.0.106 install, latest version displayed in tablet & FMC.

Edited November 1, 20241 yr by TomCYYZ

"Nav data out of date" is still displayed on the FMS after updating via Navigraph Hub Can I just try it via the UFT without messing anything up? The FMS already displays "2411 rev1".

Edited November 1, 20241 yr by Christopher Low

It appears as though the nose-down trim limit on climb-out is still not fixed. I suppose it's possible that my issue is that I use an end-limit on elevator axis to make the pitch a bit less twitchy, but unless PMDG programming is allowing elevator sensitivity to affect stab trim, my end limit shouldn't affect stab trim sensitivity.

I've just updated and the EFB is still blank. Was this update not fixing that?

Thanks

2 hours ago, Christopher Low said:

"Nav data out of date" is still displayed on the FMS after updating via Navigraph Hub Can I just try it via the UFT without messing anything up? The FMS already displays "2411 rev1".

If the FMS displays 2411 Rev 1 you should not be getting “Nav Data out of date”. Are you sure that the time and date set in MSFS itself is correct? The current nav cycle should show it is valid from 11/1 to 11/27

That message did not appear this time, so maybe that problem has also been resolved (see below)? I see "AIRAC-2411 OCT31NOV28/24" on the FMS.

 

Edited November 1, 20241 yr by Christopher Low

1 hour ago, somiller said:

It appears as though the nose-down trim limit on climb-out is still not fixed. I suppose it's possible that my issue is that I use and end-limit on elevator axis to make the pitch a bit less twitchy, but unless PMDG programming is allowing elevator sensitivity to affect stab trim, my end limit shouldn't affect stab trim sensitivity.

Extremity dead zone on elevator axis won't affect trim.  So if this is still there, then the weird trim-state alteration through about 230kts to mitigate it is probably still there as well.

5 hours ago, Stearmandriver said:

Extremity dead zone on elevator axis won't affect trim.  So if this is still there, then the weird trim-state alteration through about 230kts to mitigate it is probably still there as well.

Yes around 230kts, maybe a bit before, but it seems to still be there.

I'm curious if you still experience it, and also will be interested to hear your comments on whether the 500ish foot float is still there. I've only done a couple of landings since updating to .106 and the thing seemed more stable overall on approach, including at around 500 ft. I expect to have to manage some changes in descent rate on final, but the 500 ft. thing was every approach at every airport and only seems to affect the PMDG 737's (haven't flown the 777 enough to know if it's affected) which certainly is NOT realistic. For example at KSFO coming in over the water there should be little to no variation in vertical air movement so unless gusty conditions are present the approach should be vertically stable.

6 hours ago, mikethe6th said:

I've just updated and the EFB is still blank. Was this update not fixing that?

Thanks

yep  all my pmdg  planes  are ok  except  for  the -600  black efb screen posted on the pmdg thread  and  had  to send  in a support  ticket

Works until the next reboot