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!

PMDG 737 rebuild series week 9: TFM database, support options

Welcome to week 9 of the PMDG 737 rebuild series. This week, we step away from building panels and focus on a much larger feature that TFM desperately needs: database support. I would also like to remind everyone of support options at the end of this post.

 

Database support

The following discussion on TFM’s new database support has nothing to do with Navigraph, which is a different feature from the below description. Read carefully before spreading the word.

TFM now has the ability to store data it generates in a database. We start by focusing on speech history. The new features include the following.

Brings 2 new settings to the output category. ‘Save output to a database’ and ‘Include timestamps in the speech history’. When checked, ‘save output to database’ will make use of a TFM generated database to store different information. When not checked, TFM will revert to its current behavior. The speech history size control in the output category in settings will not be available when using database support. When using database support, a new feature, ‘Include timestamps in speech history’ will become available. When checked, timestamps are included in the speech history found by pressing right bracket (]) then CTRL+S while TFM is running. When not checked, the speech history behaves the same as before with the exception that history is kept forever, and across restarts.

TFM automatically generates the database and everything it requires to use the new database features. The current location for the database is the user’s documents folder under Talking flight monitor/data/TFM.db. Manually deleting this file or folder structure will force TFM to regenerate the database on next restart. To stop regenerating the database after it is deleted, uncheck the ‘Save output to a database’ box in output category in TFM settings before deleting it and restarting TFM.

The new database support provides limitless possibilities in the future. With something simple such as speech history to something as complex as storing complete flights, landing rates, custom panel states, and more. The only limit is your imagination. This brings us to an important topic. TFM support and feedback channels.

 

 

Support and feedback

 

TFM has a few support and feedback channels available to users. With new users coming on board, joining different BVI communities, and the number of BVI pilot communities growing in number, it is impossible to reach everyone in person or on a Team Talk server. So, it is critical that new feature requests/feedback go through one or all of the following channels. We can no longer take feature requests, bug reports, and feedback by word of mouth.

 

Available support channels

 

 

Other options  will come available in the coming weeks. We would like to request users make use of the options above when requesting support. It goes a long way in speeding up fixes, implementations of features, and reviewing feedback.