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; as the development of my earlier X-Plane gauges designed for SPAD.neXt has come to a stop for the moment.
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 →
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 →
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.
Running Flight Instrument Panels (FIPs) will drag the performance of the simulator to some extent. To minimize the impacts on some not so high-end PCs, off-loading them to a spare computer isn’t a bad idea.
To those who are “network-phobia”, here’s an example how I put the FIPs (with some help from Ricardo in the first place) to work on a spare computer in my family network. Continue reading →
The ability of starting up multiple FIPs in specific order everytime has been a feature requested by almost all FIP users for a long long time. Saitek has finally implemented it onto its new drivers. However, this feature may need another tweak in order to function.
After the installation of the new drivers, a file called “SaiFlightFip.xml” containing the current setup information of the FIPs and the gauges should be created accordingly.
Via this “SaiFlightFip.xml”, the start-up order of the multiple gauges can be specified as desired.
Normally, driver installation should be no more than pointing-and-clicking on the mouse. Saitek’s new ProFlight drivers, “ProFlight_FSX_Plugin_7_0_40_9_x64_Software” and “Saitek_Pro_Flight_Instrument_Panel_7_0_40_9_x64_Full_pfw”, however, might need a little tweak.
Some friends said to me that the installation of these two drivers was as easy as snapping fingers. However, there were others telling me the opposite. To be more exact, their FIPs wouldn’t start up after the installation, even though all the other Saitek gears work as usual.
To me, both statements are true since I experienced both extremes myself over the last few days. Continue reading →