Received a number of inquiries recently from friends who asked for advises why their FIPs (Flight Instrument Panels) no longer work after upgrading to P3Dv4.
Causes are in general similar — the exe.xml and/or the DLL.XML are missing. Because these two files don’t come with the simulator nor created by the Saitek drivers by default. Moreover, the latest FSUIPC5 is also a prerequisite.
Fixes are simple: Continue reading
Windows 10’s Creator Update has been available for some time. If your system aren’t aware of it, you can download the Update Assistant from Microsoft here.
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.
I sometimes receive questions asking me “Why the knobs on one of my FIPs don’t work? They used to be working fine.”
It is a bug in the Saitek driver. When the SaiFlightSimX.xml builds up to a certain number (most likely over 15 from my experience), the knob command assigned to the last gauge (or the last two gauges) becomes not functioning.
Suggested fixes are follows: 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
A friend told me he heard no sound when flying A2A aircraft under 2D cockpit mode, and ask me if there’s a fix. I believe there is information about it on A2A’s Support Forum. Anyway, here’s the solution using C182T as an example.
- Open panel.cfg file in the aircraft’s folder
- Search for //gauge01=A2A_C182!cockpitBuilder, 2,2,2,2
- Remove the comment marks “//” from the beginning of the line
- And lastly save the file.
That will do.
Thanks to friends who praised me for removing the jaggies on the FIP gauges.
I really wish I did. But it is Ulrich of SPAD.neXt who actually brings the difference.
As Michael comments, we users of FIPs have been disturbed by the jaggies since their launch.
Over the years, I thought the jaggies could only be solved by replacing the LCD screen with a higher resolution one. Never expect someone could really get rid of them via a piece of software. It’s truly a landmark because it now opens a much wider possibility to the usage of the FIP gauges in the future. Continue reading
As I replied to some friends, my Post 369: Aerofly is Good but Be Careful was by no mean to scare anybody who is interested in the new simulator. The post simply states a fact that my card was burnt during the game and gives my personal comment to others who are using or are intending to use the software.
To play safe, I have installed Real Temp to monitor the CPU and GPU status of my computer. The utility can be configured to stay on top of all displays.
I used to run Real Temp Continue reading
During my recent system recovery, many trivial issues found on my computer before the crash are also fixed. That’s a good thing. But unfortunately, there are new little issues coming up that didn’t exist before.
For example, I used to leave my Switch Panel, Radio Panel and Multi-Panel with power-on all the time, so that whenever I start the simulator, they could be put in operation immediately. But now, I have to load the simulator first and then plug in the USB hub on which the Panels are connected. Otherwise, the display on the Multi-Panel won’t turn on. Fix is yet to come.
Another issue is also Saitek related. Continue reading
In the past ten months, I had failed to upgrade my older computer to Windows 10 numerous times. Various google-searched solutions were tried but futile in the end. The upgrade process always stopped at 20- or 70-somethings and reverted back to the original OS. It was quite frustrating.
Last weekend, I was finally successful to upgrade the computer to Windows 10. The optical drive was the key! Continue reading