Followings are the P3Dv4 Settings on my new computer before Orbx addition to come next, with which overall frame rate at present stays around 53 stably except in those extremely dense areas. Continue reading →
One of the most important tunings to me after upgrading to P3Dv4 (actually any update or upgrade) is to ensure the continuity of the newly reinstalled or copied aircraft to be run as they did in the previous version consistently .
Followings are the steps:
Copy corresponding “Aircraft.cfg” files from
Copy corresponding aircraft flying records (“state.cfg“) from “SimObjects” in
“C:\Users\<username>\AppData\Roaming\Lockheed Martin\Prepar3D v3” to
This post is originally the first aritcle in the “My P3Dv4 Setting Up” series. However, since I do normally perform the configuration back up mentioned in the second article first, I therefore rename this post to #02 and the second post #1. Publishing time adjusted as well to reflect the proper order.
As stated in the About FSX Times of this blog, my goal is to achieve a stable flight simulation system performance with a minimum 30 fps in average. Luckily, I’ve been able to achieve that goal with some compromises. But unluckily, that 30-something fps level also acts like a barrier that stops me from passing.
I am not sure yet whether the 64-bit P3Dv4 and my new hardware would help break this spell for good. But the 120 to 210 fps initially gained from the new system without any tuning seems like a promising start.
As the hardware side of my new cockpit is still not ready, I’ll take it slowly to install addons and to finetune the system. Continue reading →
Actually this is the second piece in the “My P3Dv4 Setting Up” series of articles. However, since I normally do the back up before migrating FSX aircraft described in the last story, I therefore name this post #01 and rename the last one #2. Publication time is adjusted as well for proper display order.
After every installation (whether it is P3D or FSX or other similar programs, and no matter if it is a new install or a re-installation), I’ll immediately do a back up for the key configuration files first. In P3Dv4, most of the user-configurable files are located in the following folders:
I just ordered P3Dv4 tonight. I didn’t plan to get it now because my new rig hasn’t been set up properly. But I have no choice because more and more friends are asking the compatibility status of my gauges with the new version. Although some users reported to me that my gauges on their system function as usual, I still need to ensure that myself that they are truly in good shape.
From time to time I receive emails about the availability of FIP gauges for bigger airplanes. The B737 wet compass and flaps indicator, in particular, are two instrument mostly inquired. So here they are.
Different from my previous attempts, these two truly implement the panel light effect on the gauges. And they look particularly appealing in a dim environment. Continue reading →
Followings are the storage drives I so far added to my new computer. Except the 2TB Backup drive (O:), all are SSDs of various size from previous purchases.
Major System Folders have been reassigned to various drives, so that user data could be kept intact and independent from System drive (C:) in case Windows is required to be restored or even reinstalled. Continue reading →
Received a number of friends who report to me that my gauges function properly as usual under the new P3Dv4. So happy to hear that because I, myself, still haven’t purchased the 64-bit version yet. Thank you all.
Speaking about gauges, just finished a new set for the DHC2 Beaver. Although it is no way comparable to Beaverpilot’s full-scale Beaver Simulator, the instrument still provide good fun to those FIP users who enjoy float-planes flying.
To complete the instrument set, Continue reading →
Again, before proceeding the update, you’d better unplug all attached USB devices (except the one for the mouse and keyboard) and CD/DVD drivers first. This helps minimizing the chance of many known errors.
Basically I found no errors or hits to my system or the flight simulator.