bobr wrote:Wow, thanks for that info fenflame. I was getting terrible performance and trying many different fixes, but your solution cleared it all right up. Things are butter smooth now, even in a pmdg 737 at EHAM with full UTL traffic and lots of clouds in the sky.
Another thing that's often true Bob, if you are getting good numbers like 40/90 or even 35/90 and the right number stays at or slightly above 90 and you have stutter issues, its usually not a FI related problem. The trouble is FI is the interface we have to the program and its 3D world, if there's an issue, its common to shoot the messenger....in this case FI.
The symptoms you had are very typical of a driver issue when the numbers remained good.
When the right number drops below 90 (with ASW of) the left number usually jumps up at the same time, that's typically a resource problem. Settings too high, one processor core maxed out (usually core 0), bottlenecks in the GPU. Basically a hardware horsepower problem. I've made posts detailing how to optimize the cpu when you start P3D. Even though its 64 bit now, it still doesn't do a brilliant job of spreading the work around the cores, but you can force it to manage itself better once its up and running and it will be great for the whole time you have the app running. you can't really use affinity masking like in FSX because you don't always know which core its going to load up to 100%.
Win10-64, i7-4790K OC to 4.7GHZ, 16GB DDR3, EVGA GTX1070 8GB OC, 1 Monitor , CV1, Saitek Rudder Pedals, CH Eclipse Yoke, P3DV4.5
FI P3DV4 Beta Tester. FlyInside Moderator.