New features

PMDG 737 rebuild week 4: Flight controls and navigation/displays

by

This week, we continue with our series on rebuilding TFM support for the PMDG 737 aircraft. In week four, we will cover the flight controls and the navigation/displays panels. Before we get started, a quick reminder that there are plenty of websites that show how the 737’s panels are used.

 

Flight controls panel

The flight controls panel has two parts. The top section that contains the controls to manipulate, and a bottom section that holds the indicators. Below are the shortcuts for the flight controls panel.

 

  • ALT+ A – Captains controls, or control A.
  • ALT+B – F/O controls, or control B.
  • ALT+P – Spoiler A.
  • ALT+O – Spoiler B.
  • ALT+Y – Yaw damper.
  • ALT+N – Alternat flaps armed on/off.
  • ALT+F – Alternat flaps position switch.
  • ALT+1 – ALT+0 – the different indicators for this panel.

 

Navigation/Displays panel

 

The navigation/displays panel is fairly simple. It has no indicators and only 5 switches. Below are the keyboard shortcuts.

 

  • ALT+V – VHF navigation selector switch
  • ALT+I – IRU selector switch.
  • ALT+F – FMC selector switch.
  • ALT+S – Source selector switch.
  • ALT+C – Control pane selector switch.

 

To report bugs and new features, while TFM is running, press right bracket (]), then CTRL+SHIFT+I to open the issue queue. Take a look at other bug reports/feature requests before posting a new one. If one similar to your own idea exists, comment on that one before creating a new one. Have questions or want to get started? Fill out the contact form and we will get back with you soon.

PMDG timeline, partial aircraft support

by

We get several questions on how long it takes to build support for an aircraft, and will partial support be released to the community. I want to take a few minutes and answer these questions.

 

How long does it take to build support for an aircraft?

The short answer to this question is it depends on the aircraft. It can take a short amount of time for some of the freeware aircraft because they don’t have any panels or controls not provided by the simulator, and checklists are usually short. On the other end of the time scale, it could take a long time if the aircraft has a large SDK and detailed checklists. Each PMDG aircraft has a detailed SDK that provides access to most controls and indicators. On the other hand, the Aerosoft A3xx series SDKs are detailed, but compact. They provide access to most controls, indicators, and markers for the start, in progress, and end for each stage of flight. Each SDK will require evaluating what it can or can’t provide, building support, and testing. Evaluating and testing are the most time consuming parts of building TFM support for an aircraft. Below are estimated due dates for each of the PMDG aircraft.

 

sept 22 2022 737

mar 20 2023 777

sept 22 2023 747

 

Since these dates are estimated guidelines, we could finish early. Each week of the rebuild process will feature a blog post covering the completed items for that week and a video demonstration of those items.

 

Will you release partial support for an aircraft?

In the past, we would release support as we built it – the alpha versions were the released version. Now, we only release a feature when it is complete. Sure, it might need more work, but the feature is still complete. The new ILS feature is an example of this. It is complete, but we can still add to it. From now on, aircraft are part of this decision. An incomplete aircraft means beta or alpha versions, which we will not release. Since TFM is open source, anyone can retrieve the source code, build it, test it, then report on it. You can report bugs, new features, confirm existing bugs, and report a fixed bug. For this, you need Visual Studio 2022, a GitHub account, and a local install of git for Windows. I recommend consulting the documentation for these products to get started with testing preview versions of TFM.

At the end of this week, we will continue our series on the PMDG 737 rebuild process. If you have any new features or bugs to report, press right bracket (]), then CTRL+Shift+I while TFM is running to reach the GitHub issue queue. Try to find existing bugs or features to comment on before creating a new one. Trying to get started and need help? Feel free to fill out the contact form. We will get back with you soon.

 

PMDG 737 rebuild, week 3: Looking “Forward” to next week

by

Over the past two weeks, we have been rebuilding the PMDG 737 Aft Overhead panels. This week we finished them. They follow the same format as the previous ones. Switches and buttons first, then indicators. As always, each panel has its own set of settings found in TFM’s settings dialog. Below is a list of panels not covered in previous weeks.

 

Dome lights

It has a single switch to set the dome lights. Choices are dim, off, and bright. This panel has no keyboard shortcuts assigned to its controls.

 

EEC

 

  • ALT+L – Engine #1.
  • ALT+R – Engine #2.
  • ALT+1 – ALT+6 – The various EEC indicators.

 

Oxygen

 

  • ALT+X – Oxygen needle.
  • ALT+O – Oxygen switch
  • ALT+1 – Oxygen indicator.

 

Gear

 

  • ALT+1 – Nose gear indicator.
  • ALT+2 – Left gear indicator.
  • ALT+3 – Right gear indicator.

 

Flight recorder

  • ALT+F – Flight recorder switch.
  • ALT+1 – Flight recorder indicator.

If you would like to provide feedback to TFM, while TFM is running, press right bracket (]), followed by Ctrl+Shift+I to launch the GitHub issue queue. Here, you can create new issues to report a bug or request a new feature. If you see a feature or bug report similar to your own, comment on that one before considering making a new one. If you need help on a one-on-one basis, or need help getting started, feel free to contact us. We will get back with you soon.

 

PMDG 737 rebuild, week 2: PSEU and service interphone

by

In week 2 of the PMDG 737 rebuild, we took time to rebuild the aft overhead panels PSEU and service interphone. These panels are fairly simple, featuring a single control for each. The PSEU panel has an indicator, and the service interphone panel has a switch that turns the service phone on and off. Again, these panels come with companion settings for TFM found at settings>PMDG>speech events> 737.

PMDG 737 rebuild, week 1: ADIRU panel

by

This past week, we started working on the rebuild for the PMDG 737 series of aircraft. The process requires moving around source code and building new user interface elements. This week we present a new IRU panel with some exciting new features. This new 737 panel allows a pilot to jump directly to major sections of the window, check the state of panel lights quickly, and going to TFM settings allows the pilot to change whether the switches and lights speak or stay silent. As an added bonus, the IRU panel sports two flashing IRU lights when the FMC is ready for the GPS coordinates found in the IRU display section of the panel. Below are the keyboard shortcuts for the IRU panel.

 

NOTE: The new IRU panel is named ADIRU and is found under the Aft Overhead when in the cockpit panels dialog.

 

  • ALT+D – jump to the display selector.
  • ALT+L – jump to the left IRU mode selector.
  • ALT+R – jump to the right IRU mode selector.
  • ALT+1…ALT+9 – jump to individual lights on the panel.

 

The panel lights will automatically announce their states when gaining focus. To check for the two flashing lights, press ALT+2 and ALT+3 for the left/right IRU indicators. Then, read current line with your preferred screen reader. If the value constantly changes between on and off, the indicator is blinking.

To provide feedback on TFM, feel free to fill out the contact form, and we will get back with you soon. To leave a feature request or bug report, press Ctrl+shift+I while TFM is running. This takes you to the GitHub issue queue where you can look up other bug reports and feature requests. If you see a similar bug or feature already posted, add a comment to it. Otherwise, feel free to create a new one.

 

Developer update 5/22/2022

by

This last week, we fixed a few bugs and added a few new features to TFM. One being that the glide slope indicator for the new ILS system reads up/down instead of above/below. We wanted a more consistent flow of information telling the pilot what needs done, instead of telling them were the plane is located. The FDU, offsets for the PMDG 737, and 737/777 cross-grades take up the rest of this post.

 

The FDU

The FDU or flight display unit gives key information about flight systems. This post only covers parts of the MCP or mode control panel. In the PMDG 737, requesting an autopilot instrument value such as heading, or altitude announces the aircraft component in charge, the value of the instrument, and the navigation aid controlling the instrument’s flight mode. An example for altitude might look like the below output.

 

MCP altitude 8000 VNav.

 

We upgraded the 777 series to show these values when requesting readouts from the autopilot.

 

PMDG 737 offsets

Last fall, we started rebuilding support for the PMDG aircraft. One of the processes includes reorganization of the PMDG offsets. The new way of accessing them gives us the ability to add one within a short period of time. Each PMDG series like the 737 can have up to 250-300 offsets. Adding these to the 737 will take time, especially when adding them in consideration of future updates.

 

PMDG 737 and 777 equality

Since TFM started PMDG support, the 737 and 777 were not on equal ground. Either the 777 had better support, or the 737 had more of it. This time in the near future will focus on bringing the 737/777 up to the same level of support. As the PMDG rebuilding process continues, we will get closer to rebuilding the support for the 747 series. Since these upgrades and rebuild processes take time, TFM may not have a release until the second half of June 2022.

We look forward to your feedback. If you want to make a bug report, press Ctrl+Shift+I while TFM is running to launch the issue tracker in your default browser. If you have any questions or need help getting started, feel free to fill out the contact form on the website.

Developer update 5/12/2022

by

In a short while, TFM 22.5 will release. This version has three major updates. The new features include a fix to the settings dialog, a setting to find the location of the airports database, and a new ILS system.

 

Settings update

In the past, the PMDG CDU soft keys setting in the PMDG settings refused to save. Going forward, all settings will keep the user’s preferences. We also added some new settings described in the following sections.

 

Airports database location

There is a new category in settings named airports database. When exploring these settings, there is a text field that accepts a folder path where P3D’s airports database is found. You will also find a browse button to aid in finding the required folder. This setting is needed in order for TFM to make use of airport functions. The new ILS system is one of those features requiring the use of the airports database.

 

New ILS system

The current ILS system is based on the aircraft’s navigation system. For example, NAV1 has a localizer needle that moves from left to right showing your position on the localizer. The same method occurs for the glide slope. When NAV1 is tracking the glide slope, the radio needle moves up and down to show your position on the glide slope. TFM represents these positions as a percentage value. For example, “99% left, 80% up”. It is difficult to understand the meaning of these values, so we rewrote the current ILS system to supply heading values for the localizer, and altitude values for the glide slope. For example, TFM might announce “40 left, 1500 below”. In this case, turn 40 degrees to the left for the localizer, and descend 1500 feet for the glide slope. Along with the new ILS system are two settings under aircraft in the settings dialog. The first one is ‘announce localizer headings’. When it is checked, the localizer will supply directions in the form of headings. The second one is ‘announce glide slope altitudes’. When checked, the glide slope will supply directions in the form of altitude values. When these settings are unchecked, the ILS system will revert to the original percentage values.

The new ILS system comes with a dialog opened by pressing the right bracket key (]), then pressing CONTROL+D. You must make selections in this dialog for the new ILS to work. When the dialog opens, focus is placed on the airport field. You can then type the airport code of interest, such as KMIA or KATL. When done, press ENTER on your keyboard. TFM should announce the number of runways loaded. Otherwise, it will announce that the airport is invalid. When you have the runways of interest loaded, press ALT+R to jump to the list of runways. Use the arrow keys to choose a runway. When done, press ALT+I to jump to the ILS information field. Review the details. If needed, revisit the runways list to make another choice, then revisit the ILS information field to review the details again. To revisit the airport field, press ALT+A, then type in a new airport code and press ENTER on your keyboard. When satisfied with your choices, press ALT+O for the Ok button. Otherwise press ALT+C to cancel and close the dialog. Feel free to make use of the destination runway dialog any time during a flight. As long as the settings are set before final approach.

 

Known issues

  • The destination runway dialog has no method of clearing current settings. To fix, load another airport.
  • The ILS details field in the destination runway dialog only gives essential information. Report a new feature to have more information added.
  • The distance lines in the ILS details of the destination runway dialog may give false numbers when on ground or before aircraft power up. This is a limitation of the database.

We want your feedback on any TFM features. To report a bug or new feature request, press the right bracket key (]), then press CONTROL+SHIFT+I to open the GitHub issue queue. Please look to see if your feature or bug has already been reported. If not, feel free to post a new report. Otherwise, make a new comment on an existing report discussing your bug or feature. To contact us about getting started with TFM, feel free to fill out our contact form. One of us will get back with you soon.