Catching up, spring 2024 feedback form

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!

PMDG 737 cockpit window, panels list

Welcome back to this week’s blog post. There is a lot in store for this week, so let’s get started. We put some heavy work into the PMDG 737 cockpit window, and got some panels converted. We will take a look below.

 

Tracking panel progress

 

It isn’t easy keeping track of panels and their progress when they are scattered over several blog posts. So, from now on, each blog post will list all of the completed cockpit panels, even if they were mentioned in previous posts. This will make it easier for everyone to keep track of a single list. Here are the finished panels at this point.

 

  • Overhead: ADIRU.
  • Overhead: CVR (formerly flight recorder).
  • Overhead: Dome lights.
  • Overhead: EEC.
  • Overhead: Gear.
  • Overhead: Oxygen.
  • MCP box: Altitude.
  • MCP box: Heading.
  • MCP box: Speed.
  • MCP box: Nav aids (formerly navigation or flight controls).
  • MCP box: Vertical speed.
  • CDU/FMC.
  • Transponder window.
  • Trim window.

 

PMDG 737 cockpit window

 

We spent a lot of time working on the PMDG 737 cockpit window and came up with some features that make the cockpit panels easier to use. Here is a list of them. Watch the video to see a demo of them at work.

 

  • Search for panels by keyword (F2)
  • Focus the panels tree (F3).
  • Clear search results (F4).
  • Factory reset panels (F5) [see below].
  • Rearrange panels (CONTROL+UP/CONTROL+DOWN).
  • Sort ascending or descending (Panels tree context menu).
  • Save layout (Close the window or panels tree context menu).

 

We look forward to seeing you for the next blog post. Don’t forget to register for FlightSim expo going on later this month in Houston TX USA. We hope to see you there!

Key command help for TFM windows

In last week’s blog post, we described TFM’s new user interface layout. In this blog post, we will cover what has happened since then, and cover new features. The newest: Key command help for the new TFM windows.

 

PMDG 737 FMC/MCP

 

The new PMDG 737 FMC and MCP boxes are complete. They have the same keyboard commands as before, with some additions. The FMC has two new commands: Focus line select mode indicator and toggle line select modes. As mentioned in last week’s blog post, the line select mode indicator is a constant reminder of the active line select mode. It has the following indications.

 

  • D – Default line select keys. These are CONTROL 1-6/ALT 1-6.
  • A – Alternate – These are F1-F12.

Toggle line select keys will switch the FMC between the default and alternat key sets. To access the available keyboard commands in the FMC, press CONTROL+SHIFT+F1 from anywhere in the FMC window. The PMDG 737 MCP boxes are now complete. The key commands are the same as before, with the following additions.

 

  • Auto brake – Use the auto brake key commands from anywhere in the speed box. There is no need to focus on it first.
  • Speed brake – Use the key commands for the speed brake from anywhere in the speed box. There is no need to focus on it first.

To see the key commands for any of the MCP boxes, press F1 while in an MCP box. Example: When in the altitude box, pressing F1 shows all key commands available for the altitude box. Until next week… happy flying!

TFM rebuild, new user interface

It has been a while since we last posted. We have been quite busy getting some fun and interesting things done with TFM. The big news: A new user interface! The rest of the blog post will explain.

 

Upgrading to dotnet 7.0

 

TFM currently uses dotnet framework 4.8, which is fairly old. The concern is when Microsoft discontinues support for dotnet 4.8, TFM will no longer get security fixes and critical bug fixes in its underlying libraries. Some time after that, TFM may no longer be safe to use from a security standpoint. Considering this, it would benefit us to upgrade TFM to dotnet 7.0. It is the newest .net framework, is more secure, implements current programming practices, and is generally faster than .net 4.8. We recommend anyone who uses or is interested in TFM, install the dotnet 7.0 runtime.

 

A new user interface

 

Along with the dotnet 7.0 upgrade, we are switching out TFM’s current user interface elements for new ones. As a result, you will notice a few things.

 

  • We have to back track through TFM and rebuild its UI, so new features are currently on hold.
  • The current preview is no longer supported. When we get significant portions of the new TFM done, we will release preview builds as before.
  • Portions of the new TFM are the same as the current version, and other portions are significantly different than before.
  • Any bugs reported on the official and preview builds are held for historical sake, and won’t be fixed in 23.3 releases. They will be carried over to the new TFM, provided they are present going forward.

 

Users should see a significant increase in speed, less errors and bugs, and more stability from the new user interface. We are also increasing TFM’s accessibility with assistive technology such as screen readers, braille displays, and magnifiers.

 

What’s new?

 

There are limitless possibilities with the new user interface elements we are now using. The below list outlines some new features in the new user interface.

 

  • It is generally faster than the old one.
  • If a control has a key command, it can be clearly labeled.
  • Generally, we can fix long standing bugs in the old TFM.
  • New features are easier to build, and will take less time.
  • TFM won’t be as resource intense as the old one.

 

We aren’t putting any deadline on the conversion. We ask everyone be patient and wait until we say that the new user interface is safe to use.

 

New TFM features

 

As already mentioned, TFM can bring you new features with the new dotnet upgrade and user interface rebuild. Here are some of the new features we are working on.

 

FMC new features

 

  • Faster performance. The new FMC is roughly 3 times faster than the old one.
  • Increased refresh rate from 30 seconds to 10 seconds.
  • The caret remains at its current location in the display after an auto refresh.
  • Includes an indicator that displays the current line select keys in use. A = alternate; d = default.
  • Change line select key sets on the fly with CTRL+L while working in the FMC.
  • All controls have clearly labeled names and key commands.
  • Pressing ENTER now types the scratchpad text into the FMC.
  • Pressing the clear button clears the TFM and PMDG scratchpad. When the scratchpad is cleared, TFM announces that it is now clear.
  • The font size increases or decreases as the FMC window size changes.

In general, you will see some of the following new features.

 

  • Controls in a window, especially small ones, will resize as the window resizes.
  • New controls such as a toggle button. Instead of using the words ‘on’ or ‘off’ for on/off controls, TFM can now use the pressed state of a toggle button to indicate the on/off state of an aircraft switch. An example is auto throttle. If TFM announces ‘auto throttle button pressed,’ it means auto throttle is turned on. Otherwise, it is turned off. This eliminates the old indicators which were bulky and time consuming to use.
  • TFM can now indicate the state of an aircraft switch with color. If the switch is on (toggle button pressed), it changes the background color to green and the text on the button to white. This makes it easier for sighted users to spot turned on switches.

 

There is much more possible than what we can put in a blog post. However, we will keep everyone updated on the current status of the new TFM redesign.

 

Flightsim expo

 

Don’t forget FlightSim expo on June 23-25, 2023. We are presenting on Sunday June 25 at 10:00AM EST. The entire weekend of presentations is streamed live if you register for online access. We hope to see you in person. If not, we will see you online!

 

SimBrief, first officer, and Flight sim expo 2023

Life has been busy over the past few weeks. Most of it related to TFM. This week’s blog post isn’t going to be very long. However, it has important points to take note of during the next few months. Our main topics this week are concerns about first officer pro/next, SimBrief, and SimFlight Expo in June 2023.

 

What about the PMDG 747?

 

We will continue support for the PMDG 747 series. However, other matters take priority. We will continue the 747 later this spring/summer. See the following sections for the reasons why we postponed the 747 cycle.

 

Concerns about first officer pro/next

 

We aren’t involved with first officer pro/next development. However, we did make some recommendations some time ago on how to make FSO more accessible. Unfortunately, most of those recommendations weren’t implemented, nor plan to be implemented any time soon. This is a cause for concern in the future. To address those concerns, we started working on our own first officer. So far, it is for the PMDG 737. We are starting with manual flows, then will work into auto flows later on. There isn’t a time on when it will be finished, so stay tuned in for future updates. The reasons why we pushed first officer/flows to the top of the list are below.

 

  • Accessibility is an unknown in future first officer updates.
  • It appears that first officer pro/next is expanding into other things, straying away from a first officer addon.
  • First officer seems to progressively get more difficult to understand and use.

 

SimBrief support

 

We are starting support for the popular SimBrief flight planning service found at www.simbrief.com. To support the first officer features in the PMDG 737, we have to move SimBrief support to the top of the list, pushing the PMDG 747 down to the bottom of the to-do list. So far, TFM has support for the basic parts of the navlog in the flight plan. For those who build TFM from source, you can find the navlog by validating your SimBrief user ID (a 6+ digit number) in TFM settings, then pressing right bracket, then CONTROL+SHIFT+B to open the SimBrief flight plan window. Note that the SimBrief flight plan window is under development and will change before it comes out in a preview build.

 

Flight sim expo

 

We are getting ready for Flight Sim Expo in June of 2023. The Expo takes place in Houston Texas, United States from June 23 – 25 2023. We are on the schedule and will give an update on TFM since the last time it was presented at Flight sim expo. For those attending in person, we will be there to meet you face-to-face. We hope to see you there. Updates on presentation time will be announced when we are close to that time.

 

PMDG 747 week 3 roundup

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

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`

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

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

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.