There's a bug with the current drivers when you undock certain panels the fps halves when you use the NI Limiter.

 

Aha. Thanks, Steve. So would unlimited FPS in the sim and 1/2 refresh rate (for 30 fps on 60 hz monitors) in NVIDIA Control Panel be the right setting, or should I keep the sim pegged to 30 fps in addition to the 1/2 refresh?

 

Rich is right: you should start charging fees.

 

Many thanks.

 

***

www.ontheglideslope.net

 

 

Ultimately I've gone with TB ON, Vsync ON, frame rates locked at 30 in the sim, and refresh rates set to 1/2 adaptive in the NVIDIA control panel. I'm getting extremely good and smooth performance with this

 

Nick over at SimForums confirmed this a while back, unless something has changed since then.

 

It's what I run and all seems to be well.

 

Mark

 

 

Ultimately I've gone with TB ON, Vsync ON, frame rates locked at 30 in the sim, and refresh rates set to 1/2 adaptive in the NVIDIA control panel. I'm getting extremely good and smooth performance with this

 

Nick over at SimForums confirmed this a while back, unless something has changed since then.

 

It's what I run and all seems to be well.

 

Mark

What you have to watch out for with these limiter/vsync setups:

Top. 1/2 refresh adaptive retraining between refresh and half frequency - bad news.
Middle. NI 30fps Limiter shows problem that halves fps with undocked panel
30fps fixed in display settings slider shows best results, but requires fast machine.

Running the fixed fps on the display settings slider there was a small wobble when setting NI 1/2 adaptive. However, when the NI fps limit was used the fps remained constant, but the undocked panel caused the fps to run at around half fps. So probably best to leave out any limiting with P3D and NVidia drivers at the moment. Reducing look ahead buffer to one, made no difference on this scenario, coming in to KLAX.

I´ve went down the NVCP custom resolution route, adding in a 30hz resolution for my 3440x1440 monitor. By enabling VSYNC in P3D, the framerate stays at 30 all the time, and the sim is very smooth (wish i could say the same for UI and mouse movement, but everything has a price)!

 

But - there is a flie in the ointment - so to speak: while changing the view position in the VC, either with EZDock or the default hold spacebar and look around, it sometimes judders like crazy, even though the FPS is glued to 30 (monitored with the internal counter, and Fraps, for good measure). I´ve tried almost everything I can think of (global terrain view =1, disable SLI, turn off all autogen, lock fps internally etc), but it´s still there, and drives me crazy. I haven´t seen this is P3D before, so it might be that, or a combination with the latest Nvidia-driver. 

 

Have anyone else experienced this, or is it just on my computer? 

 

Best regards, 

 

Kristoffer

hey kristolz,

 

i am using a 3440x1440 monitor too, do you see image stretching on your monitor sides? if yes how do you minimize it ? what zoom level do you use?

 

kind regards,

 

jaff

hey kristolz,

 

i am using a 3440x1440 monitor too, do you see image stretching on your monitor sides? if yes how do you minimize it ? what zoom level do you use?

 

kind regards,

 

jaff

 

 

 

Hey Jaffer!

 

I use 0.30 zoom factor, and WideViewAspect off. I used to have it on, but it all depends on the aircraft. I can´t remember from the top of my head exactly which ones, but I think i need to use WideView with the Q400. I don´t see any stretching at that zoom level. 

 

All 2D panels get a bit sqashed, but you learn to live with it.. There might be a way to fix this, but haven´t got around to look into it yet. More important to get the sim running OK and smooth..!

 

I use EZDok to set up all the views btw. 

Running the fixed fps on the display settings slider there was a small wobble when setting NI 1/2 adaptive. However, when the NI fps limit was used the fps remained constant, but the undocked panel caused the fps to run at around half fps. So probably best to leave out any limiting with P3D and NVidia drivers at the moment. Reducing look ahead buffer to one, made no difference on this scenario, coming in to KLAX.

Thanks, Steve. I'll turn off the 1/2 and peg to 30 in P3D. I am lucky to have a fast machine so we will see how it goes. If nothing else the current setup seems to be working well.

Yes, the 1/2 vsync maybe pulls the fixed around a bit, but hardly anything. Although could be seen as if the look ahead depleted dropping the trace suddenly as the plane turned more scenery into view. Leaving that off would be better. The limited would be good if it worked reliably. Once you've set Fixed fps below unlimited on the slider, it's solidly making a straight line on the graph so should be good enough.

Bonjour,

 

New to P3D, since yesterday.

Everyhing went OK during the installation. On my first flight, I noticed shimmering and what I think is a vsynch problem.

I decided to look at shimmering after and concentrate on the VSynch problem.

The terrain seems to be displayed in horizontal bands which are shifted vertically during sharp turns or panning. Otherwise the PFS and smoothness are very good.

 

So I found this thread, and after reading, and tryng everything it seems for my config that there is nothing to do.
Otherwise the display is beautifull, but I am a bit disapointed as I do not have this problem with Steam FSX.

 

Compare to FSX the CPU is very low, so could it be that my GPU (780GTX) is not enough powerfull for P3D ?

 

And what is the difference between P3D and FSX in the way they handle VSynch. It seems completly different.

May be a question for Steve who knows how it works.

 

Thank you in advance.

Cheers

Claude

P3D is an elaborate desktop window in fullscreen mode, but FSX in fullscreen uses the Windows exclusive mode. This gives proper access to vsync functions. The P3D desktop window vsync complies with the current desktop settings.

 

 

With P3D the limiter can delay the frame to keep the same frame for two periods when set at 30fps on a 60Hz monitor. But the partial refresh setting interferes with the display as it aims between 0x, 1/2x and 1x the monitor refresh frequency.

 

 

With FSX the 1/2, 1/3, 1/4, refresh partial vsync in exclusive mode set to 1/2 x 60Hz refresh = 30fps, shows the same frame twice very precisely on a 60Hz monitor without stalling. And so in windowed mode the partial refresh does not interfere with the display.

Thank you very much Steve for the explanation.

 

I tried FSX windowed, not in fullscreen exclusive mode, and the behavior is the same than in P3D.

So why LM doesn't choose the fullscreen mode like FSX does ? Seems difficult to understand  as P3D  derive from FSX.

 

So no solution for this problem other than LM returning back to fullscreen exclusive mode ?

When you talk about partial refresh, you mean refreshing individual region not well synchronized with the global frame display. ?

 

Best regards

Claude 

Partial refresh 1/2, 1/3, 1/4... 1/2 x 60 = 30.

So, Steve, should we just use the VSync control in P3D and run the NCP Vsync as "Use the 3D Application Setting" or "On" ?  I have been using "On"  (and the P3D setting as "On" also)  and it seems to run fine, but based on what I am now reading, I'm not sure that is correct.

 

Thanks,

Jeff

 

 

So no solution for this problem other than LM returning back to fullscreen exclusive mode ?

 

It would be amazing to offer it as an option. I would personally love it. I doubt they will do it because fullscreen exclusive introduces more system dependent issues that they would then have to support (which costs money) as well as other issues like support for multiscreen monitors lah de-dah. If you look at the smoothness of it in FSX, it is the best so long as the underlying minimum framerate is significantly in excess of the locked framerate. P3D can get fairly close but only if you throw a lot more hardware at it. In any case, all this is old technology because with the coming of VR, there are new technologies that will control smoothness - but you will have to throw more new hardware at that too!