I spent a couple of hours to sort out some bugs and I added a couple more features to the MDC Generator. Namely:
Fixed a couple of functions giving errors (victims of the code “clean-up” I did right before posting).
Added True Bearing calculation to the MDCp1. It estimates the route changes to get to the next waypoint. It helps to mentally visualize the flightplan, increasing the pilot’s awareness. As per the distance, the TBRG is an estimation.
Added some default Codewords, I found re-writing them post reset a bit tedious. These codewords are taken from some used in the 132nd Virtual Wing.
Added Data Sources: if you fly with different groups or on different servers, frequencies, agencies and pre-fixed waypoints can change. Overwriting the same tables every time can be both time-consuming and, honestly, annoying. Therefore, I added a simple field in the “Payload & Mission Options” sheet that allows you to define which table is going to be used to feed airfields, waypoints and agencies.
Simply duplicate the original table, rename it and adjust it as you prefer. Then, in the above mentioned fields, paste the new tables name and everything will work as before, as long as you have maintained the consistency of the tables (i.e. fields order and type).
In the example above I created a different table with default agencies used by the 132nd VW. You can do the same and change values depending on the group you are flying with, or even depending on a specific scenario or mission.
The number of rows in the table also allow to quickly verify if the table name matches an existing sheet.
As usual, this simple MDC Generator is based on Google Spreadsheet. You can make your copy by clicking here.
If you need instructions or directions have a look at this article or feel free to contact me.