Lockheed Martin has finally released P3D v5.1. Seems like not too many people are aware of it (based on the number of respondents in its support forum) while most people are keeping their eyes on MSFS — me the same.
Anyway, hope this update solves or at least improves the many issues reported after its launch. There are still many features MSFS can’t or doesn’t do properly today.
One of the nice designs of MSFS is many of its cockpit instruments can be used across different aircrafts (despite practicability in real life), which in a way simplifies the construction of DIY cockpit using my MSFS Multi-shared FIP gauges.
Following is the table showing key instruments on the default propellers and turboprops in MSFS implemented and to be implemented.
Via the table, one can check out the usage of each instrument on different aircraft according to the reference number or alphabet assigned to them, and further find out what gauges are included or not included from the cockpit layouts captured below.
Update 1: The number and alphabet indications are added to the corresponding gauges in respective cockpit images for clearer references.
Have burnt some mid-night oil in the last few days to finish the remaining gauges (except the Engine Gauges) for the MSFS C152, C172 and DR400 bundles as soon as possible.
Glad that the last few Navigation gauges have done and sent out earlier today. Will take some breaks before moving on to the Engine gauges as well as some documentations plus the MSFS specific GaugeSwitcher.
Followings are the image updates for the MSFS-specific gauges being developed. Some of them are completed in general but I will keep them for now because there are still new changes coming up for style consistency.
In the past weekend, Lukas, a friend who was experiencing similar MSFS installation issue I had had two months ago asked me how I had the issue solved in the end. I told him I really had no idea since I didn’t do anything but just waited for about a month to get the app with the update patch again. The issue was solved by itself, probably due to the new updates, or something else.
He replied he wouldn’t want to wait and asked if there were any suggestions.
Hm…after some thoughts…I recalled Michael Basler in Germany once recommended me to get the simulator via Steam instead of the Microsoft Shop. So I passed the suggestion to Lukas. Continue reading →