As mentioned in my last post, not all default nor third-party aircraft come with an aircraft reference file. If needed, to create a missing one isn’t difficult at all.
The Aircraft Reference is basically an html-formatted file with a name containing “aircraft model” + “_REF“ and a filename extension of “.htm” It is located in the aircraft folder under “SimObjects/Airplanes“.
If you don’t have much knowledge about html, you could simply: Continue reading
Airspeed limitations are some of the most visited references to flightsimmers or even real pilots. I normally seek for them in the aircraft’s manual or via Internet. For sure, the process doesn’t take a lot of work but it can be hardly called handy, especially when you need these information during a flight session.
Last week, I found out that there’s actually a quick way of locating these information in FSX and P3D quickly. I don’t know if you know it or not, but I was not aware of it in my 15+ years of flightsimming. How hilariously.
All we need is Continue reading
The Carenado CT210M is one of my favorite aircraft and it actually was the first third-party aircraft I ever purchased for flight simulation many years ago. Nevertheless, I had felt something wrong about its cockpit instrument but I couldn’t figure out what it was until recently when I was asked to worked on the X-Plane version of the ASI Gauge for Logitech’s Flight Instrument Panels (FIPs).
It is the Continue reading
There are times that we may want to find out what Local Variables (LVars) are used on a specific aircraft for many reasons. If the developer doesn’t provide it, here’s a quick and simple way to generate a Local Variable list of the airplane, whether it’s a third-party or default aircraft.
During a flight session, Continue reading
When I was reinstalling A2A aircraft for P3Dv4, I grumbled what the heck the developers are doing in altering the aircraft installation folder from “SimObjects” to “Prepar3D v4 Add-ons” under Documents. But after reviewing the file hierarchy further, I have to admit that it is in fact a nice user-friendly touch.
The move not only avoids the chance of messing up with original files in P3D, but it also can eliminate the need of reinstalling aircraft after P3D is forced to clean install again for whatever reasons or when update is available.
Under the new structure, the P3Dv4-ready A2A installer (in my case) added the aircraft location to the “add-ons.cfg” in the Prepar3D.cfg directory after
installation. Then created an XML file called “add-on.xml“, which contains all the sub-folder information, in the root directory of the aircraft folder as well.
Since these two files Continue reading
This morning I received an email from Paul Wasserman who asked me why the red line on my A2A C172R tachometer is set at 2,400 rpm, rather than 2,700 rpm as shown on his cockpit. Looking at his photo, I was bewildered because I had never seen the gauge before; and it was the first time someone reported to me about this inconsistency.
In order to confirm that there were nothing I had missed, I re-downloaded, re-installed and re-updated the aircraft in the following hours. “Without luck”, the result was the same — the red line is still at 2,400 rpm. I really had my head scratched. 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
- “P:\Prepar3Dv3\SimObjects\Airplanes” to
Copy corresponding aircraft flying records (“state.cfg“) from “SimObjects” in
- “C:\Users\<username>\AppData\Roaming\Lockheed Martin\Prepar3D v3” to
- “C:\Users\<username>\AppData\Roaming\Lockheed Martin\Prepar3D v4“
Since P3Dv4 involves the using of new Windows system registries, Continue reading
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
Just purchased Alabeo’s R66 and C172RG Cutlass while they are on sale this week. I had no problem with the R66 but had my head scratched for a while regarding C172RG’s installation.
The major difference between the two installers is the C172RG one requires users to specify the version of P3D being used and the R66 doesn’t.
Under such circumstances, even though I am not using P3D version 2, I gave it a try on selecting the P3Dv2 option on the menu and browsed to direct the path to my current P3Dv3 folder on P:\ Drive. No surprise. I got errors of not finding files from the package and installation was aborted.
Then I tried putting the path of my P3Dv3 folder without checking the P3Dv2 option. The installation proceeded and reported a success. Continue reading