OK , thank you , will try this .

 

Also 36 and 48 are quite high fps, try 144/5 = 28.8 fits nice with the 29fps NI limit or fixed in P3D Display settings.

Question about this NI locking concept. Is this the sequence of events? Assume that locking to VSYNC at a multiple of 1:1 is not possible because we can't get the frame-rate high enough. So:

- P3D delivers frames as fast as it can to the GPU on unlimited

- GPU is forced to restrict delivering frames to the monitor by the NI frame limit

- We try to match NI with multiples of the monitor HZ as best we can.

 

Conclusions that I reach from this:

1. NI frame-limit is quite imprecise
2. Monitor HZ is also not perfectly precise (can be tweaked with custom resolutions)
3. NI and HZ are NOT linked and so we are tuning the two like a tuning fork on a guitar string to try and tune out any non-smooth depiction and reduce NI-HZ to zero difference (but it will probably drift).
4. Flying in a straight line it can look smooth, but  the tighter the bank, the more the terrain panning jerkiness is modulated by a beat frequency which is NI-HZ (whatever the difference is)
5. There is absolutely no way to fix conclusion (3) above even with expensive hardware. You could throw the next gen PASCAL card at this and the smoothness issues would still occur
6. BUT - expect smoothness to improve with higher frame-rates not because of the frame-rate itself but because the difference between NI and HZ decreases in relative terms as the frame-rate increases.

Are these conclusions sound? If so, my ultimate conclusion is that NI frame limit of 30 is no man's land because the frame rate is not really high enough to mask the problem of conclusion(3) above, and GSYNC doesn't work at NI30 either. From my own experience, smoothness really starts to improve at NI40, but this is unsustainable unless you are on default scenery -but if it were - you wouldn't even need this NI fix proposed by SteveW because then you could use GSYNC (if you had it).

Yes, pretty good synopsis. Whatever we do it's a compromise.

Can you move your addons above core zero? Put them on 1,2,3 with a .bat.

 

Or enable HT use AM=85, put addons above core zero (LPs 0 and 1) put them on 2,3,4,5,6,7. Or use AM=116, and run addons as-is.

 

Or if you want to keep HT off use AM=14 and run addons as-is.

 

Steve if you start charging you will be rich  :wink:

No worries Richie. I'm always working on this stuff. If I find anything out worth knowing I'll pass it along to you guy's.

No worries Richie. I'm always working on this stuff. If I find anything out worth knowing I'll pass it along to you guy's.

 

Steve and Rob what a team 

An update on my situation: 

 

 

 

Regarding the GPU issue: I don´t use Nvidia Inspector. I´ve only set "Prefer Maximum Performance" in the NVCP prepar3d.exe application profile. I use GPU-Z to monitor GPU utilisation, and after v 3.2 it seems a bit lower than in 3.1. I use 2x EVGA GTX980 Classified custom loop watercooling, and both hover around 40-50%  at EGLL RW27L. in fair weather. My goal is to create a setup that works between EGLL and KJFK, for the Concorde-X. The Concorde is a heavy hitter, and you have no time to be looking out the window while flying at low altitudes/speeds, so I intend to keep the scenery amount to a bare minimum. Smoothness over eye-candy   

 

I finally got rid of the panning jerkiness, after several hours of antagonising investigation. Startet by turning every slider down to it´s absolute lowest setting possible, disabled all add-on scenery, and tested to see if the jerkiness was still there. It was. I then tried numerous Nvidia Inspector "tweaks", limited framerate (combinations of NI and Internal), and got nowhere, until i tried the good old "Negative LOD Bias: Allow" vs "Clamp". In "clamp" mode, the jerkiness finally went away! I´ve experimented with this setting in the past, and it has always caused stutters on my computer, but not this time.. strange! 

 

Now I can hopefully go back to tweaking the sliders for a good compromise, and hopefully complete a flight over the pond;) 

 

(Btw - all testing done in the FSLabs Concorde X (cleared for takeoff panel state), RW27L at EGLL, fair weather.  )

As a new guy around here, and a new cockpit builder, I want to thank Steve, Rob, Rich and the rest of you guys for this thread and many others like it. It's really helped get my system dialed in, and I have my AM at 116 and have Lasso'd the rest of my add-ons per the guidance for a quad-core. Interestingly, when I used NI to set FPS to 30, my frame rates tanked - like down to 7 or 8 FPS just sitting on the tarmac, which was shocking given I'm using a 980 ti GPU and a quad core running at 4.6. I backed all settings out to default and things were fine with rates of 40-60 across my three-monitor setup with some healthy ASN weather to boot. 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, but if anyone has an idea why the NI setting crashed my frame rates I'd be all ears.

 

***

 

www.ontehglideslope.net

Hi Steve,

 

Any chance I could get a screen shot of your NI settings? I can't see them in this thread. Apologies if you have posted them elsewhere!

anyone has an idea why the NI setting crashed my frame rates I'd be all ears.

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

 

 

Hi Steve,

 

Any chance I could get a screen shot of your NI settings? I can't see them in this thread. Apologies if you have posted them elsewhere!

Complete defaults except for single display performance and the NI fps limit (if it works lol).

Complete defaults except for single display performance and the NI fps limit (if it works lol).

 

Thank you.

Steve and Rob what a team 

That's for sure!

A thorough overview of some of the terms being used in this thread:

 

http://www.tweakguides.com/NVFORCE_7.html

Steve and Rob what a team 

 

+1 :Applause: