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
After the cockpit video, Father Dane further sent me the following information regarding the objectives of the simulator project that he built. It also includes a 6-part tutorial explaining the very basics of flying.
Although Father Dane mentioned that most followers of FSX Times (many are real pilots) should not need these simple information, and some of the followers might have seen them in his channel already, I am still very happy to putting them here as they are very inspiring.
I built the C172 simulator as a Lenten project last year for the use of some local young students who wanted to find out if they really had the flying “bug”.
As it happened, they did and now they are all involved in taking real flying lessons on their way to earning a PPL. Continue reading
A pilot friend (who prefers anonymous) sent me a note about how he connects the Reality XP GNS430 to the NAV2 CDI on the C172SP in X-Plane 11. I don’t have any products from Reality XP myself but I believe the instruction should be of interest to many others who own the product.
Followings are the instructions: Continue reading
Some friends email me saying that they are interested to know how I upgraded (“migrate” I think is more accurate) my Saitek drivers to the Logitech version. Again, as mentioned a few times, such a migration is not necessary if the Saitek drivers are working fine.
Anyway, it does no harm if anyone want to keep up with the Logitech version. But ensure to AVOID using version 0.8.144.0 as it has error. Version 220.127.116.11. is fine, which I am currently using.
Followings are the steps I took for the migration: Continue reading
It is commonly known that SPAD.neXt and Saitek/Logitech drivers cannot be run simultaneoulsy; otherwise conflicts will occur.
Here’s how to avoid the conflict when running the new X-Plane FIP Gauges (using Saitek/Logitech drivers) together with SPAD.neXt; since the development of my earlier X-Plane gauges designed for SPAD.neXt has come to a stop for the moment.
Edit: Just found that there are still conflicts between the Logitech plugins and SPAD.neXt. Under this combination, all basic functions work ok but not the many extra features provided by SPAD.neXt.
Will explore further if there are solutions.
Install the Saitek/Logitech FIP drivers (if they have been removed from the computer) — it is necessary for the Windows OS to recognize the hardware.
You could download the Flight Instrument Panel Drivers from Logitech’s support web page here. Or if you have the older version 7 on hand, it works fine as well.
Follow the instructions in Post 471 to install the X-Plane Plug-in.
After restarting the computer, right-click on the Windows Menu bar at the bottom to call up “Task Manager” Continue reading
As my FIP gauges are building up and support more aircraft, I have written a quick Selection Guide to help those who are interested in my Gauges.
Click here or the image above to read the guide.
Since there is a friend David who is asking for more description to allow FIPs to work in SE, here’s the details:
Type “%AppData%\Microsoft” in File Explorer to go to the “\Roaming\Microsoft” directory.
If you have FSX boxed version on the computer as well, you will see both “FSX” and “FSX-SE” folder under the directory. Otherwise, you will see “FSX” only.
Click on the “FSX-SE” folder and open the “exe.xml” file.
Note that this is the only file you’ll need to edit to allow FIPs to work in SE.
Inside the file, you will see the following script: Continue reading
From time to time I receive questions from simmers asking if my ShadeShifter utility is compatible with P3D, while they are requesting for the download link.
The answer is “No” because “Shade for FSX” by Mogwaisoft is written specifically for FSX as its name indicates. And since my ShadeShifter utility was built upon it, it therefore doesn’t apply to the P3D platform indeed.
However, as my Post 107 mentioned, “Shade for FSX” is basically a utility that modifies the sky texture in FSX to achieve a different look and feel. And since P3D is in general an upgraded version of FSX, we could therefore copy and paste the “sky textures” modified by “Shade for FSX” into P3D. That will achieve the same result, although this approach lacks the user-friendly interface the utility originally provides.
Perhaps some of you have been doing it already. For others who have both FSX and P3D and the “Shade for FSX” utility and don’t know how to do it, here’s the instruction: Continue reading
Putting FIPs on a networked PC could reserve system resources for the simulator but the FIPs on the remote computer have to be started manually.
Stefano Cancelli in the Comment section of the story provides a solution by using a Microsoft utility called PSExec. Via PSExec, the FIPs on the networked PC can now start up automatically when FSX on the local computer launches, and quits when FSX exits.
Very useful tips and followings are the instruction from Stef: Continue reading