PMDG

Organizational shift, priority boarding

by

Hi everyone!

Welcome back to the blog! A lot has been going on lately. Eventually, we will talk about all of our updates, but for now, let’s just focus on the most recent. In this post, we are going to cover a few logistical/policy updates and an update on the task force. We are also going to cover a new upcoming feature and provide an update on our clipboard and checklist editor. So, without delay, here we go!

Task force resigns

Everyone in the task force had to leave because they had other responsibilities outside of TFM that demanded all of their attention. So, they are no longer representing us in any official capacity. We thank them for their valuable time and effort and wish them well in the future.

Logistical/policy updates

Normally, we don’t put these types of updates on a blog post, but this is an exception. As we try to be more transparent with the general public and our users, the way in which we conduct ourselves has changed. Even though Talking flight monitor (TFM) is closed source, we also try to be more open about what we are doing to create features, and a little about what goes into making those features (EG: design choices, etc.). Here are a few design choices we have made at an organizational level.

  • No more private preview – This means that users are not required to follow or sign an NDA. Preview features are available to anyone who wants to try them out.
  • Starting on 02/20/2026, anyone with access to an active license will have to pay the normal subscription price (TFM pricing).
  • Anyone who contributes to TFM such as documentation, source code, etc., is a paying user (see above).
  • All preview licenses and subscriptions will be discontinued after the new terms of use go into effect.

Now that the boring part is out of the way, let’s get on to something more fun.

Priority boarding

Starting at TFM 6.9.5, priority boarding will be available for features not yet ready for production use. We came up with the idea after several popular apps such as Visual studio, Chrome, GitHub, and Gmail have found success with this style of ‘preview’. In TFM settings, you will be able to go to the priority boarding section and check/uncheck the preview features you want or don’t want to use. Everything is unchecked by default. Once a feature in priority boarding is released, it will be removed from the priority boarding program and will be made available to everyone.

Clipboard

Since the release of the clipboard, we have seen some confusion about what it does and how it works. We will try to dispel the confusion here. However, if you still need help, feel free to contact us at info (@) talkingflightmonitor (dot) com.

In the PMDG aircraft, there is a clipboard that you can drop down from the yoke if the feature is turned on in settings. On the clipboard, there are checklists and flows you can follow. A green check means the item is done, and a red X means it is not done yet. Clicking on a red item will perform the task and mark it as complete. TFM’s clipboard does the same thing, just in an accessible format. Pressing enter/space on an item performs the task and marks it as complete. However, there are items that are set to ‘set as required’, ‘verify’, or some other language that indicates the clipboard doesn’t know what to expect for that item, or the item changes based on flight conditions. Examples are autobrake, MCP altitude, heading, speed, etc. Those items are ‘manual’ items that require you to set the values in the panels.

We had quite a bit to say today, so, we will go for now. Next time, we will talk more about some of our upcoming web features, the checklist editor, and anything else TFM throws our way. Until then, happy flying!

Preview 2024.1, updates, and spring feedback form results

by

Welcome back to this week’s blog post. Last time, we played catch-up and let you know about the spring 2024 feedback form we posted. This week I want to cover a few things, so this post may be a little longer than normal. We are going to cover preview builds, Talking flight monitor updates, project priorities, project restructuring, a new partnership, and results from the spring 2024 feedback form. So, let’s get started!

Preview builds

It has been a little over a year since we posted a preview build. Since then, Talking flight monitor has been going through growing pains in the form of a complete conversion from dotnet 4.8 to dotnet 8.0. We also started converting the windows and dialogs in Talking flight monitor over to a newer, more accessible user interface library. The conversion is going well. However, many people have been anxious, wanting to know when the next preview would be posted. We then posted a poll late last week, asking whether or not we should bring back the preview builds before the conversion was complete. The pole indicated that 99.9% of the respondents wanted the preview builds to return, even if the conversion wasn’t complete. In response to this interest, we brought back the preview builds. Preview 2024.1.503 is available for downloaded, and can be found on this website under the preview releases link. Make sure you read the entire release notes before downloading and using. By using the preview builds, you agree that Talking flight monitor and all of its associates, developers, and partners aren’t responsible for damage caused by the preview. The preview will be released around the 15th of each month.

Updates

After the preview release, the only updates are that the PMDG 737 overhead/anti-ice panel and the main area of the overhead panel are complete.

Project priorities

The BVI pilots communities have been talking about Talking flight monitor project priorities over the past week or so. It has come to our attention that a projected feature, ‘flows and checklists’ be implemented as soon as possible. This is because many of the community members feel that they would lose access to a first officer feature (provided by another developer) if we don’t act fast. Our official position is that we need to finish the PMDG 737 panels before attempting to create flows and checklists for it. Among other things, we are in the middle of a conversion/restructuring project at this time and might find it difficult to respond to the request quickly.

Project restructuring and new partnership

While we go through the conversion process, we will also go through and implement a modular approach to Talking flight monitor development. This means that when portions of source code can be isolated from the rest of the codebase, it should then be isolated and packaged so it can be reused in other projects. Doing this will make the software faster and more reliable. It also gives users the ability to download components or modules they are interested in using. For example, why force everyone to download Talking flight monitor with PMDG 747/777 support when they will never use it? So, while we work through the conversion process and other items on the table, we will work on the modular design for the project. This modular redesign will not require a redesign of what is already finished or planned, so no worries there.
On the restructuring side of things, I recently started a software development company that focuses on supporting other software developers in their journey of becoming a professional software developer, student, or other professional in the field. It develops accessible software tools for those students/professionals so they can independently complete their work tasks. Inspiragon (my company) and Talking flight monitor agreed to a partnership. The terms of the agreement are Inspiragon will provide me at no cost as a three-quarter time contractor to work on Talking flight monitor. It will also cover Talking flight monitor’s development related expenses, if any, in exchange for revenue on paid addons. This also means that Talking flight monitor’s website will change throughout the rest of this year. Inspiragon will add a new feature request form, a new contact form, and potentially a new bug tracker. This way, there is no need to create an account on GitHub. Just fill out the form and submit it, and you are done. Now, coming out of this partnership is the requirement that Talking flight monitor develop paid addons to be sold on Inspiragon’s website. So, at some point in the future, we will start working on those paid addons. At this point, I don’t know much about the paid addons, other than they will be on a monthly or yearly subscription rate. When the time comes, we will release more details. You can visit Inspiragon’s website at www.inspiragon.com. At the time of writing, the website is nearly empty. It is just getting started. Bare with us as we go through growing pains together.

Spring 2024 feedback form results

In the spring 2024 feedback form, we got some interesting results. Some we were expecting, others were a surprise. To start, Most participants use P3D. However, most of them also voted for us to drop support for it. Next, everyone used payware aircraft and voted to consolidate features, preserve the state of the trim toggle, and convert the automatic detection of aircraft into a manual selection process. Finally, most of the participants voted to have the left and right bracket (command keys) separated from the TFM virtual keyboard while providing a way to turn them on and off without affecting the TFM keyboard. There may be follow up polls or feedback forms throughout the year to further narrow down the interest of the communities that use Talking flight monitor.
This has been a long post, so I will end it now. Keep watching YouTube for new videos, the website for new content, and the TFM communities for support in your flying adventures. Until next time…

Catching up, spring 2024 feedback form

by

Welcome back to the blog. It has been a while since we last posted here. In the last post, we mentioned that we would start vlogging on YouTube. We also mentioned that any significant amount of text updates would come here instead. Well, here we are with a text-based update.

TFM progress

We would have to write a novel to cover the updates and things that happened since the last update. Some of them are listed below.

• TFM is now running on dotnet 8.
• We now recommend people build from source.
• * At this point, focus is on MSFS, not P3D.
• We are waiting for the upcoming PMDG 777 for MSFS.
• … and more.

We will be getting back to our text-based updates with more PMDG 737 development. It will be an exciting time for TFM/PMDG users!

Spring 2024 feedback form

There have been some technical problems with the fall 2023 feedback form. As a result, not very many people had the chance to fill it out. Besides, end of the year feedback forms might have a conflict with the end of year holidays. So, we decided to try our feedback forms at the start of the year. The spring 2024 feedback form is now available. We are seeking feedback from the BVI pilots community and others with a vested interest in TFM’s direction. This feedback form focuses on keyboard commands, consolidating similar/related features into a single feature, and removing legacy (no longer used) components. Feel free to fill it out. We are looking for solid direction, so be sure to follow the directions at the beginning of the form. You can find the link at the top of any page on this website.
This is all we have for this week. Stay tuned for more posts here and on YouTube. Until next time, have fun flying!

Post surgery update/P3D support

by

In last month’s blog post, we covered the heartbeat of Talking flight monitor and what it will take to address existing bugs and to do an in-place upgrade of the entire system. This week, we will update everyone on my surgery and provide some important news about supporting P3D and Navigraph.

 

Surgery update

 

Surgery went well. The doctor wants me off my feet for at least four weeks. This means I can do light weight activities inside. He put a limit on how long I can be on my feet, including how long I can sit at a desk during the day. As a result, I had limited time with my laptop, until my wife found a workaround. Now, I can “sit at my desk” as long as possible. This still means limited times because sitting on the couch with my feet up on my desk chair stresses out my back after a while. At least it is as many times during the day as I want. Doing flights is easy because I can be at my desk until autopilot takes over, then move to the couch. I will keep everyone updated on the next stage of recovery with the next blog post.

 

Navigraph support

 

Talking flight monitor is now added to the Navigraph HUB. Anyone with a subscription should be able to add the current cycle. This is only for the source builds though. If you would like to build from source to test bleeding edge code, follow the directions found at Building TFM from source. We are currently adding support for the database, so no new features will arrive until this is finished and tested.

 

P3D support

 

P3D 6 was released sometime last month. Some significant changes were made to improve the P3D framework and scenery. However, these changes broke support for the PMDG line of aircraft. In other words, PMDG aircraft do not work in P3d6. PMDG announced that after trying to add support for P3D 6, they had deeper problems than just changing some installer files. In the same announcement, they stated that revisiting this problem wouldn’t happen until the 777 and 747 were added to MSFS. This puts the timeframe sometime in mid or late 2024. As reported in the announcement, PMDG most likely won’t continue support for P3D if the changes require too many resources or too much time. Since MSFS arrived on the scene, the market share for P3D 4 and later has significantly declined. Even though more addons and scenery exist for P3D than MSFS, more addons are being altered or newly developed for MSFS. This brings us to Talking flight monitor’s placement in the market.

Talking flight monitor strives to support as many simulators as possible. However, we are also limited in time and resources. Since market value of P3D is declining in favor of MSFS, and PMDG doesn’t support P3d 6, we are not supporting P3D 6 nor continuing new development on P3D 5. Any new development in Talking flight monitor will be focused on MSFS. Keep the following in mind.

 

  • When features are identical in both simulators, we will support P3D5 and earlier.
  • If Talking flight monitor works in P3D6, it is at your own risk.
  • As long as the PMDG SDKs are the same or close to the same, we will support the P3D versions.
  • When the PMDG SDKs are drastically different, the MSFS versions take priority.
  • Navigraph support is independent of a simulator, so works in both P3D and MSFS.
  • We will not support Aerosoft products.
  • We do not support FS2Crew or similar products.
  • We do not support the PMDG DC6, TS4xxx, or similar aircraft.
  • Support for Osobo aircraft requires an evaluation.

Again, we will do our best to keep P3D5 and earlier support going. However, we can’t make promises to the effect. We hope everyone understands our decision to back off on P3D support. In the event PMDG does support P3D 6, we will reassess the situation.

 

PMDG 747 week 3 roundup

by

Welcome to week 3 of the PMDG 747 rebuild series. This week has given us some ups and downs. However, we made it through the week with some interesting changes to TFM. So, read on for some fun and potentially not so fun updates.

 

Changing the blog series name

 

Since we started the blog series on the PMDG 737, we have introduced new features and bug fixes not related directly to the 737. It is the same with the 747. We are introducing new features and fixing bugs not directly related to the 747. Keep in mind, we are still working on the 747. We are also working on things not related to PMDG aircraft. Given this, we are thinking of changing the series name to “TFM updates, week X” or something similar. If you have any other ideas, feel free to drop us a line on the contact form on the website.

 

What happened to Navigraph?

 

Some users might have seen the GitHub commits mentioning the removal of the Navigraph support in TFM. This is true. Navigraph has taken forever to get back to us about adding Navigraph support to TFM. Since they are taking forever and we aren’t using it anyways, we removed support for it. In the event we are able to make use of it, we will add it back into TFM.

 

PMDG 747 changes

 

Since we have been working in other areas of TFM, the 747 hasn’t gotten much attention. There are a few things to mention.

 

  • The Overhead Maint/Electrical panel buttons now work.
  • Added the Overhead Maint/Fuel panel, described below.

Overhead Maint/Fuel panel

 

This panel is self explanatory. It only has two buttons listed below.

 

ALT+S – Scavenge pump. Press SPACE or ENTER to toggle.

ALT+R – RSV 2-3 transfer. Press SPACE or ENTER to toggle.

 

While looking through the SDK, there are some controls or entire panels that have write-only controls on them. This means we can provide a setting, but can’t read the setting. These controls and panels aren’t much use to BVI pilots, so we will leave them out of TFM until PMDG can provide an outlet for reading the existing setting of these controls and panels. In the Overhead Maint panel, the following panels are left out of TFM until further notice.

 

  • EEC
  • EMU (748 only)
  • APU startup source (748 only)

Weather changes

 

Since we are working on other things along with the PMDG aircraft, we decided to start putting weather tracking into TFM. Adding weather is nice because we can add a few things at a time until the weather services are exhausted. Here are the weather events added this week. The below are added to the request wind command which will be renamed in a future release.

 

  • Visibility in knotts.
  • Turbulence level, none, moderate, severe, or extreme.
  • Precipitation level, none, light, moderate, heavy, very heavy.
  • Precipitation type, none, rain, snow, or hail.

We also added the ability for TFM to automatically announce when the aircraft enters/exits a cloud. The precipitation level/type will get added in a future release.

 

Bug fixes for this week

 

  • The PMDG 737 now only displays its own heading box. Previously, it would display the heading window for freeware aircraft instead of its own.
  • The rebuild database button in TFM’s airports database settings is now ‘build database’. Previously, it had the confusing name ‘rebuild database’.
  • The build database will only display if either P3D or MSFS is loaded into a cockpit. Previously, it would be displayed even if there were no simulators loaded. Pressing the build database button without a loaded simulator forced TFM to crash.

 

Other changes

 

  • Read instrumentation now works. Press right bracket (]), then SHIFT+M to toggle it on and off.
  • When using ‘Where am I?’ right bracket (]), then SHIFT+C while on a runway will now give the runway distance in feet.

 

What about the 737 comms panels?

 

We are still working on the comms/audio panels. There is a sequence of events we have to figure out to make the microphones and receivers change frequency type. We will keep everyone updated as things move along.

 

 

PMDG 747 week 2 roundup

by

Welcome back! Last week, we started rebuilding support for the PMDG 747. During the PMDG 737 rebuild series, the blog post titles got very long in some cases. During the PMDG 747 rebuild series, the blog titles will resemble this one: PMDG747 week 2 roundup. With that in mind, let’s get started with the PMDG 747 week 2 roundup! This post may be longer than most, but keep reading to find some interesting changes to the airports database, and the first panel to be supported in the PMDG 747.

 

Airports database

Why the changes?

 

The airports database structure has significantly changed since TFM 23.1, released at the start of January 2023. The new database design reduces the memory footprint of the airports data loaded into memory. When TFM starts, it loads the airports database. This database is over 3GB in size while it lives in memory. Each time a user requests information from the database, it calculates that user’s current location in relation to everything in the world. The resulting airports database takes up an additional 3GB of memory. To reduce the number of times TFM recalculates the user’s current location in the world, TFM constantly recalculates the user’s current location every 250MS. The consequence is that every 250MS, TFM eats another 3GB of memory. This forces the CPU to over work, pushing incomplete work on to the GPU, which eventually overloads. As a result, MSFS users experience audio buffering, jittering or jumping video, or significant lagging when the airports database is loaded. P3D users don’t experience these problems because the airports database is small enough to rebuild without taking up significant portions of computer resources. To make it easier to work with the airports database, all users will have the same changes to work with. Below are the changes made to the new airports database structure.

 

What’s new?

 

* When starting TFM for the first time, you must build the airports database.

* Start TFM.

* Go into TFM settings.

* Find the airports database section in the tree.

* In the airports database window.

* In the P3d airports database area, locate and set the P3D airports database folder.

* In the MSFS area, locate and set your MSFS airports database folder.

* Locate the “rebuild airports database” button and activate it.

* A message will appear, notifying you when the database is finished building.

* Press the OK button to close settings.

* Restart TFM by pressing right bracket (]), then CTRL+SHIFT+X.

* When TFM restarts, it will load the new database.

* Most TFM airport database features such as the ILS tracking system stay the same. We will announch any changes when they occur.

* Most airport database features run faster. A test of the ‘Where am I?’ feature accessed by pressing right bracket (]), then SHIFT+C significantlly improved in speed.

* Report bugs in the GitHub issue queue if you find any problems.

 

What’s missing?

 

* We removed the freeware flight planner. It requires a significant rewrite to comply with the new airports database design.

* We removed the airports search window found under procedures menu in the freeware flight planner. It requires significant rewrites to comply with the new airports database design.

 

PMDG 737 updates

 

The 737 isn’t quite finished yet. There are a few items that need finished. The audio/comms panels are taking a little longer than expected because we need to contact PMDG support for clarification on some of the controls. The FMC redesign is delayed because we are looking into what alternate design will work best. Aside from these outstanding items, the 737 is complete. If you have a special request for the PMDG 737, drop us a line and we will look into it.

 

PMDG 747 updates

 

Overhead Maintenance/Electrical panel

 

We added the overhead maintenance/electrical panel. This panel controls electrical activity in the engine generators and APU generators. It also defines how electricity flows from the APU and generators. As always, there is more than one way to access the controls in a panel. Either use the TAB key and move through the controls, or use the assigned keyboard commands, listed below. Since there are groups of controls in this panel, each keyboard command will take you to the group of controls linked to it.

 

Keyboard commands

 

ALT+G – Generator field reset switches. Group that contains 4 engine generator reset switches. Change by pressing SPACE or ENTER.

ALT+A – APU reset switches. A group that contains the 2 APU reset switches. Change with SPACE or ENTER.

ALT+S – Split system breaker. Change with SPACE or ENTEr.

ALT+N – Ground power test switch. Change with SPACE or ENTER.

ALT+P – Towing power switch (748 only). Change with SPACE or ENTER.

ALT+1 – Generator reset indicators. Readonly.

ALT+2 – APU reset indicators. Readonly.

ALT+3 – Split system breaker indicator. Readonly.

 

 

Other changes

 

The “Where am I?” feature has a new capability. In the past, this feature would announce the runway, gate, or taxiway where the aircraft is currently located when on the ground. In addition to these locations, “Where am I?” will announce the airport code if you are not located at a runway, gate, or taxiway, but are located somewhere within the airport’s geofenced boundaries. This helps identify when you are at the airport in the below cases.

 

  • You ran off the runway during landing.
  • You completely missed the runway during a landing.
  • You are landing on a runway that does not exist in your scenery.
  • * You attempt to drive around the airport and get lost.
  • * Pushback puts part of your aircraft in the grass or other surface.
  • * You attempt to taxi and run off the taxiway onto another surface.
  • * Other scenarios not listed.

 

It is our goal to give the “Where am I?” feature the ability to automatically announce location changes. This post is one of the longer ones we have written, so we will close for now. Until next week, have fun flying!

PMDG 747 week 1/PMDG 737 week 29`

by

Welcome to 2023. This is week 29 of the PMDG 737 rebuild series. This week we will cover some final items to get done in the 737. We will also cover the start of the PMDG 747 rebuild series. Let’s get started!

 

Finishing the PMDG 737

 

There isn’t much left in the PMDG 737 to finish. All that is left are the audio panels (3), comms panels (2), and the redesign of the FMC. I would suspect that it should take another 4 or so weeks to complete before another preview build comes out. Some users might want to know why it is taking so long to finish the 737. There are a few reasons. First, I ended up with a hard case of the flu over the past few weeks and had to recover. Now that I am better, we can continue. The second reason is covered below.

 

Starting the PMDG 747 rebuild series

 

This week (Jan 2, 2023) starts week 1 of the PMDG 747 rebuild series. It will follow a similar format as the PMDG 737 rebuild series. Each week there will be a blog post covering what has been finished each week, followed by a YouTube video showing the new features/changes for the week. When the 747 rebuild series is complete, we will feature a full flight on YouTube to show off the new features working together. As a reminder, the PMDG 747 rebuild series is expected to take around 52 weeks to complete. So, be patient during this cycle of previews.

We hope you have enjoyed the PMDG 737 rebuild series and are looking forward to the PMDG 747 rebuild series starting today. Until next week, have fun in your flying adventures.

PMDG rebuild series, week 27: Control Stand, MSFS performance, close to the end

by

Welcome to week 27 of the PMDG 737 rebuild series. A lot has gone into the past 4 weeks, and we have a lot to cover. The control stand is finished, and we have some bug fixes most people will like. The fall 2022 survey is now closed. Thanks to the people who filled it out. We will post the results on Sunday’s blog post for week 27. Now, on with the new content!

 

MSFS Performance fixes

 

Many users have noticed that TFM will cause MSFS to buffer audio, drop frames in the video, and on occasion crash. The obvious problem is the airports database and its size. The default MSFS airports database is around 780MB on disk. That’s almost 800MB of text files! When loaded into TFM, it expands to around 2GB. For some reason, loading the MSFS airports database caused GPU overloads, dropped frames, and code matrix overloads. We implemented a fix for it. However, our testing is fairly limited to a few users at this point. To check if the problem is fixed for you, do the following.

 

NOTE: The following steps requires Open broadcasting system (OBS). So, make sure you have downloaded, installed, and configured it for an MSFS recording session.

 

  1. Start MSFS and load into a PMDG 737 aircraft.
  2. Start OBS and set up for an MSFS recording.
  3. Start the recording session in OBS.
  4. While recording a video, force TFM to produce problems. A common way to cause problems is open the cockpit panels with left bracket ([), then Ctrl+P.
  5. When done trying to crash MSFS or TFM, stop the OBS recording.
  6. In OBS, go to help>logs>upload and activate the menu item.
  7. In the logs successfully uploaded window, press the analyze button. A webpage appears with the results.
  8. Read through the results. If TFM is not causing problems, you will have no GPU or code matrix overruns.
  9. Close OBS.

 

It would help us if you would send us your OBS analyzer results, especially if it identifies GPU and code matrix problems. You can send the results to info at talkingflightmonitor.com. Note the @ is spelled out with spaces around it.

 

The PMDG 737 FMC slash key

 

The slash (/) key on the PMDG 737 is now fixed. This includes the P3D and MSFS versions of the PMDG 737.

 

Control Stand

 

The control stand is self explanatory, so we wont go into much detail about its operation here. However, we will go over the keyboard commands for each section. Most of these sections are split into groups to accommodate keyboard commands. All of these controls have the ability to be silent. Just go to TFM settings/PMDG/737 speech events/Control Stand to find the sections below. Check the box to have TFM announce the value when it changes, and uncheck the box to have it remain silent when the value changes.

 

CDU

 

  • Has no keyboard commands.

 

Trim

ALT+T – Elevator trim. Use ‘U’ and ‘D’ to change the value.

ALT+A – Aileron trim. Use ‘L’ and ‘R’ to change values. Currently there is no method to center it.

ALT+B – Stab trim. This is a read-only view.

ALT+E – Electrical stab trim switch. Use SPACE or ENTER to change.

ALT+P – Auto pilot stab trim. Use SPACE or ENTER to change.

ALT+S – Stab trim. Use SPACE or ENTER to change.

 

Pedestal

 

ALT+F – Pedestal flood light. Use I and D to change the value.

ALT+P – Pedestal brightness. Use I or D to change the value.

ALT+K – Parking brake lever. Use SPACE or ENTER to change.

ALT+1 – Parking brake indicator.

ALT+2 – Pedestal unlock indicator.

ALT+3 – Unlock failure indicator.

 

Fire protection

 

The keyboard commands are grouped because there are too many controls for individual keyboard commands.

 

ALT+H – Fire handles. For each focused fire handle, press P to pull/push the handle, L to turn it left, and R to turn it right. The focused fire handle must be pulled out to turn I while a fire or fire test is in progress.

ALT+C – Fire alarm cutoff switch. Press SPACE or ENTER to change.

ALT+O – Overheat detector switches. Press SPACE or ENTER to change.

ALT+T – Fire tests. Press SPACE or ENTER to change.

ALT+1 – Fire handle indicators.

ALT+2 – Overheat indicators

ALT+4 – Extinguisher test indicators.

 

 

Cargo fire protection

 

ALT+F – Forward selector switch. Press SPACE or ENTER to change.

ALT+A – AFT selector switch. Press SPACE or ENTER to change.

ALT+W – Forward fire detector switch. Press SPACE or ENTER to change.

ALT+E – AFT fire detector switch. Press SPACE or ENTER to change.

ALT+I – Discharge. Press SPACE or ENTER to change.

ALT+T – Test. Press SPACE or ENTER to change.

ALT+1 – Forward extinguisher test indicator

ALT+2 – Aft extinguisher test indicator

ALT+3 – Forward fire indicator.

ALT+4 – Aft fire indicator.

ALT+5 – Detector fault indicator

ALT+6 – Discharge indicator

 

Transponder

 

Left bracket ([), then Shift+T – Opens the alternate transponder window.

ALT+E – Transponder code. Type a value and press ENTER.

ALT+S – Transponder source switch. Press SPACE or ENTER to change.

ALT+A – Transponder alt source. Press SPACE or ENTER to change.

ALT+M – Transponder mode switch. Press SPACE or ENTER to change.

ALT+I – Ident switch. Press SPACE or ENTER to change.

ALT+T = Transponder test. Press SPACE or ENTER to change.. WARNING: the test feature only works under certain conditions.

ALT+1 – Transponder failure indicator

 

The next update will come in week 29 or 30 when we finish up the PMDG 737 and push it out the door. Have fun with the new release. You can download it by clicking the preview releases at the top of the page. If you need help getting started with TFM, feel free to send us a contact by filling out the form on the contact us page. Have fun flying, and don’t forget the bug reports and feature requests.

PMDG 737 series, week 23: Lower forward panel, future features, next up

by

Welcome to week 23 of the PMDG 737 rebuild series. Last week, we covered the forward panel, the now available TFM 22.11 preview, and a test flight in MSFS with the PMDG 737-800. This week, we are going to cover the lower forward panel, keyboard help mode, simbrief support, the first run quick help dialog, checklists, and what is left to finish in the PMDG 737.

 

Lower forward panel

 

The lower forward panel is self explanatory. It does have quite a few brightness knobs on it though. As a reminder, pressing the letters I or d on your keyboard will increase or decrease brightness knobs values. There are 17 controls on this panel, so keyboard shortcuts take you to groups of controls. Included are the settings to select whether TFM should automatically announce the control state changes. They are located at TFM settings/PMDG/737 speech events/Lower forward.

 

Main panel group (ALT+M)

 

  • Main panel brightness, left side
  • Main panel brightness, right side
  • Main panel brightness, background
  • AFDS (flight directors) brightness

 

GPWS group (ALT+G)

 

  • Flaps inhibit switch
  • Gear inhibit switch
  • Terrain inhibit switch
  • GPWS inop indicator

 

DU group (ALT+D)

 

  • Outboard DU brightness, left side
  • Outboard DU brightness, right side
  • Inboard DU brightness, left side
  • Inboard DU brightness, right side
  • Inboard map brightness, left side
  • Inboard map brightness, right side
  • Upper DU brightness
  • Lower DU brightness
  • Lower map brightness

 

Keyboard help mode

 

Keyboard help mode is similar to NVDA’s or JAWS keyboard help mode. While TFM is running, press right bracket (]), then the question mark (?). Next, press any fully qualified TFM keyboard command to get a basic description of that keyboard command. To turn keyboard help mode off, repeat the keyboard command to turn it on. Another thing to mention here is the keyboard manager. You can now select any command in the lists and press ALT+E to execute that command. Don’t forget to turn keyboard help mode off to return to normal usage. I forgot once on a flight and ended up in a little trouble.

 

Simbrief flight plan support

 

We are going to start working on Simbrief support in TFM. This means that TFM will download the last flight plan generated through the Simbrief website. At first, users will have the ability to display different sections of the flight plan. The sections will be customizable in TFM settings when we get to that point. Later on, we will have the ability to bring the next waypoint feature over to the PMDG aircraft. It can also be used to finish the freeware flight planner, and a limitless number of other things. Get your ideas together because we will need them in the future.

 

Quick help dialog

 

The quick help dialog appears when starting TFM. It displays a few ways to get keyboard help and lists a few of the most common keyboard commands TFM has to offer. To hide the dialog during future TFM starts, check the don’t show me this again option and press the OK button.

 

Checklists and first officer features

 

Earlier today, we found a file in the PMDG 737 folders for MSFS that contained just about all of the checklists for the 737 we would want to use. After requesting permission to use the file, PMDG granted our request. This means we don’t have to come up with alternative checklists for the 737. Developing the automated/manual checklist system is going to be time consuming, but easy. These checklists will eventually work into a first officer type of feature. As with the Simbrief section above, get your ideas for future features together because we will need them later on.

 

What’s left of the PMDG 737?

We have to implement the control stand, fix some bugs with the electrical panel, and clean up code. If no major problems come up, or no more major features need implementing, I suspect that the PMDG 737 for P3D and MSFS should be ready by Christmas vacation.

We covered many things today. Hopefully, the next few weekly blog posts will wrap up progress on the PMDG 737 as well as introducing new features. As always, we will keep everyone up-to-date on what we know.

PMDG 737 rebuild series, week 22: Forward panel, MSFS test flight, preview 22.11

by

Welcome to week 22 of our PMDG 737 rebuild series. We are now 90% complete. This week and most of last week we took time to investigate issues with fs2020 and completed the forward panel. discussion is below. We will also cover The next preview (22.11).

 

The forward panel

 

We had to break the forward panel into different segments because there were over 50 controls on it. Some of them BVI pilots will never use, such as the DU selectors, some are used elsewhere in TFm, such as N1 or speed brakes.

 

Main forward panel area

 

ALT+W – Nose wheel steering. Press to cycle through options.

ALT+C – Capt. Disengage test. Press to cycle through options.

ALT+O – F/O disengage test. Press to cycle through options.

ALT+I – Cockpit lights. Press to cycle through options.

ALT+F – Fuel flow. Press to cycle through options.

ALT+1 – Left Below GS indicator.

ALT+2 – Right below GS indicator.

ALT+3 – Left FMC indicator.

ALT+4 – Right FMC indicator.

ALT+5 – Stab out of trim indicator.

ALT+6 – Anti-skid inop indicator.

 

MCP

 

ALT+1 – Left auto throttle disengage indicator (red).

ALT+2 – Right auto throttle disengage indicator (red).

ALT+3 – Left auto throttle disengage indicator (amber).

ALT+4 – Right disengage indicator (amber).

ALT+5 – Command A disengage indicator (red).

ALT+6 – Command B disengage indicator (red).

ALT+7 – Command A disengage indicator (amber).

ALT+8 – Command B disengage indicator (amber).

 

DU panel

 

ALT+D – Capt. DU. Press to cycle options.

ALT+U – F/O DU. Press to cycle options.

ALT+C – Capt. Lower DU. press to cycle options.

ALT+F – F/O lower DU. press to cycle options.

 

Standby panel

 

ALT+1 – RMI #1. Press to cycle options.

ALT+2 – RMI #2. Press to cycle options.

 

Speed panel

 

ALT+N – N1 selector. Press to cycle options.

ALT+S – Speed ref. Press to cycle options.

 

Brakes panel

 

ALT+T – Auto brake. See the MCP/Speed box for more information.

ALT+B – Brake pressure indicator.

ALT+1 – Speed brake armed indicator.

ALT+2. – Speed brake do not arm indicator.

ALT+3 – Speed brake extended indicator.

ALT+4 – Auto brake disarm indicator.

 

 

Flaps panel

 

ALT+L – Left flaps needle indicator.

ALT+R – Right flaps needle indicator.

ALT+1 – Flaps in transit indicator.

ALT+2 – Flaps extended indicator.

 

 

Gear panel

 

ALT+G – Gear lever. Press to cycle options.

ALT+1 – Nose gear in transit indicator.

ALT+2 – Left gear in transit indicator.

ALT+3 – Right gear in transit indicator.

ALT+4 – Nose gear locked indicator.

ALT+5 – Left gear locked indicator.

ALT+6 – Right gear locked indicator.

 

 

As always, we will include the TFM settings to turn on/off automatic announcements for all supported aircraft controls/states.

 

Preview 22.11

 

We will release preview 22.11 sometime later this week. Most likely, around the middle of the week. Keep an eye out for it, and don’t forget to read the release notes. This preview has a lot of working parts and new features, including MSFS support for the PMDG 737.

 

MSFS test flight follow-up

 

Last week, I tried an MSFS (fs2020) test flight in the PMDG 737-700 cargo aircraft. After some investigation, here are follow-up points from last week.

 

  • MCP controls such as L-Nav, V-Nav, level change, etc always report off. This is only true if you tell First officer next to leave the MCP alone.
  • The speed brake reports a float such as 4.93 instead of a whole number like 103. This is true and we will have to build a fix for it.
  • It takes TFM a longer time to load the MSFS airports database. This is true. In addition, you must point TFM to the FS2020 airports database after you use makerunways.exe. To point TFM to the FS2020 database, open TFM settings, navigate to the airports database setting category, then use the P3D airports database location to browse for the FS2020 database.
  • First officer fails to do auto flows. True if you have AutoFlows = 0 set in the first officer user.config file. Otherwise, it will use auto flows. The only condition is when it tells you to check doors on pushback. In this case, you will have to press the after start flow yourself.
  • Getting to the briefing, ops, and other features is difficult at best. The click points are icons with no alt text or focusable items. We hear he is going to make an accessible user interface by the middle of this week, so we will wait and see.
  • FSO next fails to program the route and other FMC items. We have mixed results with community members, and are trying to sort out the problem. If it doesn’t program the route pages, you can do it yourself.

My landing rate on this trip was -86. A never before seen in the PMDG 737, at least for me. This would prove that LNav and VNav works better in the MSFS versions. Also, auto throttle works much better in the MSFS version. A better part of my descent, the throttle maintained a .08% thrust.

We will close it up for week 22. We hope the TFM upgrades are working for you. Don’t forget to report bugs and new features, especially on the MSFS side of things. As always, if you need help, let us know.