Captains,

 

A quick NOTAM on the 737 that is important enough that I felt it should be separated from the usual announcement cycle:

 

UPDATED 2230Z/07MAR24: We have released the updates described below for PC users who purchased from PMDG directly. Please see the PMDG.com/PMDG Operations Center Users tag below to get your 737 updated.

 

 

PMDG 737 for MSFS: Update 3.00.0091 is Pending:

On Friday, we anticipate releasing update 91 for the entire MSFS fleet of 737 products. This update is primarily focused on stability improvements to eliminate some problems causing cockpit freezes that have become more problematic since the introduction of SU14 and the SU15 beta. A significant amount of work has gone into locating and correcting the issue causing this disruption and we are bringing this update cycle forward specifically to address this issue.

 

It is important to be clear that this is a stability update that carries a number of changes that are specifically designed to improve stability of operation, but few-if-any changes that are unrelated to stability. Areas that received attention include memory use, TCAS target handling, system initialization on scenario loading, a few drawing functions and some data parsing routines. Effectively, we have been focused on some very technical areas to provide greater protection against issues that might disrupt your flight and thus your enjoyment.

 

PMDG.com / PMDG Operations Center Users:

If you purchased from us directly, you will receive this update on Friday via the PMDG Operations Center.

 

VERY IMPORTANT INFORMATION FOR OPERATIONS CENTER USERS:

We recently pushed an update for OC2 that you unfortunately have to trigger manually, otherwise OC2 will not be able to connect home to handle the 737 update, among other tasks. To update OC2, simply navigate to

 

C:\Users\<YOUR USERNAME>\AppData\Roaming\PMDG\PMDG Operations Center

Once you have this folder open, execute the program: 'OpsCenterUpdater.exe'

 

You should then be all set to run normally.

 

(This requirement was a design flaw in the OC2 that we have corrected effective with this update, so you won't have to do this again in the future, fortunately!)

 

 

Marketplace-PC Users:

If you are a PC user who purchased via MS Marketplace, we will submit the new build to Marketplace for intake today. We anticipate it will be the week of 18MAR24 when the updates complete the intake/validation process via Marketplace and ultimately become available to you. (We don't control the speed there, sorry!)

 

Marketplace-Xbox Users:

If you are an Xbox user, we have not yet submitted these changes, but anticipate doing so before the end of March. Currently we are pushing multiple test updates onto the Xbox beta process in order to see if we cannot get the tablet fully running on the Xbox platform. Currently the tablet runs, but we are unable to get keyboard input to the tablet either from it's own keyboard, a hardware keyboard or the on-screen keyboard native to Xbox. Keyboard entry to the tablet is important to nearly all of it's functionality and we have requested help from the platform developer to see if we cannot crack this nut and thus clear the last obstruction to getting our Xbox users up-to-snuff with their PC counterparts. We cannot run an Xbox beta build and an Xbox release build through intake at the same time- so we need a few more weeks on the Xbox side. If we are unable to get the tablet working properly with Asobo's input- we will suspend beta builds of the 737 to Xbox and push a release build to bring Xbox users up-to-date and then return to the beta build process on Xbox.

 

(The testing and intake process for Xbox testing is painfully slow- but it is the best we have...so we are leveraging it the best we can.)

 

 

Okay- that is all for this NOTAM. We are directing the testing team back to 777 and preparing another new build for them just in time for the weekend. I'll have more on that topic under a dedicated header, sometime later.

All that I get is cannot reach server.

1 minute ago, JamesIL said:

All that I get is cannot reach server.

Did you manually update the Operations Center first?

I literally just updated to this latest version, 2 mins ago.  Worked fine.  I'm in the UK, so quite a distance for servers access to the US and update was fast.  (Always find PMDG's server access is nice and quick).

I just found the thread and now it works. Thanks

 

And RSR noted....this was one tough bug to find and squash!  We all parked our 777s and jumped back to the 737 to extensively hammer the updated build (for all NINE models) to make sure it was ready to go.

I have to say it was refreshing to hop back into the "tiny" Boeing for this round...and I proceeded to criss-cross her across the US, hoping to not find the bug, nor any others that sometimes reappear when making a major bug fix.

Since it was the 737, you know I could not resist snapping a few pics (that I could share) of her journey...(well...I've also snapped 100s of the 777 thus far...and can't wait to share those with you when I'm able)

Here is the -700 in Jviation's excellent Florida One livery, rocketing out of my home airport, on her way to the site of the 2024 FSExpo this year.

After landing in Sin City, it was a short hop to KLAX in yet another Jviation masterpiece, this time in the -700's bigger sister. (I feel hands-down J  is the best painter out there, a testament to his abilities, coming from a 20 year veteran of painting myself...I fly HIS paints, hehe)

And a final shot that just makes me smile when I see how incredibly far we've come in this hobby in the last 20+ years!  (this livery looks so good that the Vegas Sphere could not help but sneak a peak as she departed.) 🙂  

I have to return to my sequestered briefing room that holds the 777 and get busy with the new Build RSR noted is coming (or may have already come) our way.

It was truly refreshing to hop back into the 737 for a while, and its pretty amazing how different the 2 aircraft are, systems and automation-wise.  I had to remember when transitioning back from the 777.

In the 777

• Packs...set'em and forget'em
• Pressurization? the 777 knows the landing elevation, no need to play with switches or dial in elevations
• 3 position landing get? Ha! Up or Down in the 777
• AutoBrakes, the 777 turns them off after liftoff.
• Setting ILS freqs and headings....humph....old school, the 777 knows them and sets them.
• Paper checklists?....how 20th century.  Forget checklist items when taking the runway for departure...you get a warning on the EICAS, calling you out that you missed something (quite embarrassing hehe)

Other things to get used to when moving up to the 777....Size, weight, inertia.  This beast is huge....don't try to taxi her like a 737....go into a turn thinking you're a 737, and you'll put her in the grass...or worse.  And remember how much wing you have out there, hanging over the taxiway edges or when pulling into a stand.

The only things that are similar between the 2 aircraft is that they are both Boeings, have 2 wings and 2 engines.  After that, they are almost completely different machines.

I would love to be able to taxi the 737 precisely in MSFS. At the moment, I cannot get it to turn properly at anything more than walking speed. It is very annoying.

3 hours ago, Christopher Low said:

I would love to be able to taxi the 737 precisely in MSFS. At the moment, I cannot get it to turn properly at anything more than walking speed. It is very annoying.

The issue you describe seems to be related to a combination of ASOBO and PMDG.

You can change the following in any PMDG 737 aircraft for satisfactory results.

We have to take in consideration the following, in real life we don't exceed 5 KTS GS in turns more than  80-90 degrees. Of course, it can be done, but you will skid.

 

These are the changes: 

In flight_model.cfg section

 

[contact_points]

 

Change only value 78 to   50

point.0 = 1,  40.209974,  0.000000, -8.334975,  800, 0, 1.125, 78, 0.960516, 1.613, 0.6, 8, 7.5, 0, 485, 0, 5
 

to

point.0 = 1,  40.209974,  0.000000, -8.334975,  800, 0, 1.125, 50, 0.960516, 1.613, 0.6, 8, 7.5, 0, 485, 0, 5
 

Change

 

steering_time_constants= 3, 5
 

to

 

steering_time_constants= 10  
 

Add  

allow_stopped_steering = 1

 

In section [flight_tuning] change

 

yaw_gyro_stability   =2.80
 

to 

yaw_gyro_stability   = 0.15     

 

If you have a tiller or joystick, use these settings as a starting point for your assigned axis sensitivity.

2 hours ago, LRBS said:

The issue you describe seems to be related to a combination of ASOBO and PMDG.

You can change the following in any PMDG 737 aircraft for satisfactory results.

We have to take in consideration the following, in real life we don't exceed 5 KTS GS in turns more than  80-90 degrees. Of course, it can be done, but you will skid.

 

These are the changes: 

In flight_model.cfg section

 

[contact_points]

 

Change only value 78 to   50

point.0 = 1,  40.209974,  0.000000, -8.334975,  800, 0, 1.125, 78, 0.960516, 1.613, 0.6, 8, 7.5, 0, 485, 0, 5
 

to

point.0 = 1,  40.209974,  0.000000, -8.334975,  800, 0, 1.125, 50, 0.960516, 1.613, 0.6, 8, 7.5, 0, 485, 0, 5
 

Change

 

steering_time_constants= 3, 5
 

to

 

steering_time_constants= 10  
 

Add  

allow_stopped_steering = 1

 

In section [flight_tuning] change

 

yaw_gyro_stability   =2.80
 

to 

yaw_gyro_stability   = 0.15     

 

If you have a tiller or joystick, use these settings as a starting point for your assigned axis sensitivity.

Hi, LRBS, first thanks for sharing, I had already applied the yaw_gyro_stability as per pmdg forum user advise (maybe it was you) some time ago, works amazing (i have a separate tiller hardware). What will steering_time_constants add? Thanks a lot again.

16 hours ago, JamesIL said:

All that I get is cannot reach server.

Same on my end......cannot reach server.....

Same here-no server reach

1 minute ago, aero943 said:

Same here-no server reach

It is in the original post:

VERY IMPORTANT INFORMATION FOR OPERATIONS CENTER USERS:

We recently pushed an update for OC2 that you unfortunately have to trigger manually, otherwise OC2 will not be able to connect home to handle the 737 update, among other tasks. To update OC2, simply navigate to

 

C:\Users\<YOUR USERNAME>\AppData\Roaming\PMDG\PMDG Operations Center

Once you have this folder open, execute the program: 'OpsCenterUpdater.exe'

 

You should then be all set to run normally.

 

(This requirement was a design flaw in the OC2 that we have corrected effective with this update, so you won't have to do this again in the future, fortunately!)

36 minutes ago, SN737 said:

 What will steering_time_constants add?

 You are very welcome, "steering_time_constants" refers to the setting that determines how quickly the aircraft responds to your control inputs when steering on the ground.

9 hours ago, LRBS said:

 You are very welcome, "steering_time_constants" refers to the setting that determines how quickly the aircraft responds to your control inputs when steering on the ground.

Thanks buddy, will try it out.

9 hours ago, LRBS said:

 You are very welcome, "steering_time_constants" refers to the setting that determines how quickly the aircraft responds to your control inputs when steering on the ground.

Just tried it, even smoother movement now, thanks very much man.👍

I'm starting to wonder if I should crank up the failure rates when I fly my PMDG

 

You know, this is a simulator after all

 

 

(sorry if this joke is hackneyed at this point)