After switching back and forth between Windows 7 and Windows 8, and FSX and Prepar3D, for over a dozen of times within the past seven days, I have to say that FSX is still my preferred simulator.
Over the week’s testing under Windows 7 and Windows 8, the new P3D performed satisfactorily, especially it off-loaded quite a bit of CPU processing work to the graphics card. However, FSX is still functioning better than the P3D in general. Moreover, P3D, as I mentioned in earlier posts, has some issues with the Saitek hardware — in particular the FIPs, which also stops me from choosing it as my new platform.
My 7 FIPs have no problem connecting to P3D but in general they react slowly than when they are working with FSX. And the most frustrating thing is the FIPs now frequently stutter and even pause a second or so intermittently, making reading on the gauges unreliable. The symptom is getting worse as a session goes by.
Since all my FIPs function normally under FSX, P3D logically is the blame. These errors are not OS-related. Actually, I found both FSX and P3D (even the errors) run more smoothly under Windows 8.1. So I am now having Windows 8.1 as the OS of my new computer.
Frankly, I am not saying P3D is bad and I really hope that it will replace the “long-lived” FSX. But I have to move on to further set up my new computer. And before I find a solution to the FIP issue, I have no choice but to keep FSX my simulator. Anyway, I’ll keep tuning the P3D and hope that a solution can be seen either from the company or buddy users very soon.