Hi guys,

 

Completely disregarding the common mantra "don't fix it if it is not broken" I recently upgraded my system to Windows 8. This included a complete reinstallation of P3D. My problem now is that I am unable to recreate the experience of performance that I had before the reinstallation.

 

My specs are i7 [email protected], 16GBram, GeForce560Ti.

 

I used to be able to run the NGX around Europe locked at 30 FPS with most sliders to the right, except for complexity at dense and autogen normal. The same goes for GA aircraft around PWN. After the upgrade I get around 20 FPS with the same settings for both scenarios. Moving the scenery sliders up or down does not have a very large impact on my system (15 at everything maximum, 30 with everything minimum), and also playing with AA settings in nvidia Inspector does not adversely affect the results (as long as I do not put them too high). It is therefore not clear to me where my bottleneck is.

 

I use the following tweaks: affinitymask = 14, HT off, UsePools = 0, FFTF=0.1. The CPU is running at around 75% which seems consistent with the affinitymask. I tried both with and without frame rate limiting, and the internal limiter brings things down a bit, but as long as it stays there it is a very smooth experience. Currently my only solution seems to be to pull down the scenery sliders a bit more and lock everything at 20FPS. This is not what I want!

 

I also checked that I do not have any something issues with the CPU, it runs stable at 4.35GHz as long as P3D is running, with temperatures around 70°.

 

Is there anything obvious I have forgotten that will magically solve my problem?

Gosh! Was this an UP grade or a DOWN grade. Are there any benefits to Win 8 outside P3D? Sounds like it's time for a roll-back to me.

Could be, but I find it hard to believe that this difference is just up to the os. Three must be something else I have forgotten.

It's something I'm battling with another member here, we can't find the reason, and he is on the W7... same problem as yours.

 

First I suspected MS update or something, but since you are running W8... hmm... weird indeed. No solution though, sorry!

Thanks anyway. My next thing to try is to change to the latest driver from nvidia, although the one that came with win8 seems quite recent.

Update: Things have improved after upgrading to the latest beta drivers from Nvidia. I also did a fresh generation of the configuration file and reapplied the affinitymask, fftf=18, and bufferpools tweaks.

 

I'm still not able to lock it at 30FPS with autogen normal at ORBX KORS, but when airborne and most other places it works out okay. I decided to try the internal limiter, which is the cause of some of the drop in FPS. I must say that it is extremely smooth, and as long as the system handles the locked FPS, the amount of blurries is very small.

fftf=18

 

18 or 0.18?

 

For the smoothness, check for vsync tweak in my blog's tutorial. It's the A&O for perfect smoothness with nvidia cards.

It should be 0.18 :-P

 

I'm running in windowed mode with 1/2 refresh rate vsync in the inspector. I'm not seeing any issues with tearing at all. I remember having significant issues with this in fsx

1/2 RR in NI has no impact on the windowed operation of the sim. This is only for the full screen.

 

Windowed is impacted by the ForceWindowedVsync line in FSX.cfg and the quitting of the dwm.exe from task manager (either manually or via FSUIPC like described in the guide).

Oh, I see. I'm not using ForceWindowedVsync now, but I have used it earlier. To be honest I'm not seeing any difference, mainly because I don't have any tearing anyway .

 

I might try it just for fun, though. Is dwm.exe also present in Win8?

I don't know about W8, why don't you open the task manager and look yourself?

Good point, but I am not at my windows eight system now, so I thought I would just ask. Will check and let you know later how it works out.

Just out of curiosity why is your CPU only running at 75%? My 3770k runs usually at 100% on all 4 cores when in complex flying scenarios.

It should be because of AffinityMask = 14. This allows P3D to run on all but the first core. The first core is the one that is most utilised by Windows, so the idea is to leave this free to run Windows services, add-on applications, and so on. With several add-ons such as ActiveSky, Plan-G, and so on, I am pretty close to 100% on every core.