Good morning everyone. After seeing some encouraging news about the 442.19 drivers and the Frame Rate Limiter v3, I downloaded the latest ones (445.87) for my rig (specs in my signature), and also updated my Nvidia Inspector to the latest version (2.3.0.12). However, in my sim (FSX-SE, using DX10 and DX10 Fixer, windowed mode) I can´t see any effects from the Limiter at all, either if set in the Nvidia CP or in Inspector. In other games I have, I confirmed the limiter works as intended, either in fullscreen or windowed modes.

As a workaround, I keep on using RTSS but, after reading all the posts here since the release of these drivers, I shouldn't need it and NCP/NI should do the job. Is it there a way to make the limiter work?

445.87 is rumored to be buggy for a variety of 3D apps. I didn't have any problems with it with any of the flightsims, but I was getting long pauses in Windows Explorer of all things. Those long pauses are generally indicative of the video driver stalling and recovering. Windows used to blue screen when that happened, but now the OS just restarts the driver if it stops responding for a short period of time (but that sometimes causes a a few second pause). I couldn't decide if it was a faulty install, so I went back to 445.75 and then everything was okay.

45 minutes ago, Luis Hernandez said:

Good morning everyone. After seeing some encouraging news about the 442.19 drivers and the Frame Rate Limiter v3, I downloaded the latest ones (445.87) for my rig (specs in my signature), and also updated my Nvidia Inspector to the latest version (2.3.0.12). However, in my sim (FSX-SE, using DX10 and DX10 Fixer, windowed mode) I can´t see any effects from the Limiter at all, either if set in the Nvidia CP or in Inspector. In other games I have, I confirmed the limiter works as intended, either in fullscreen or windowed modes.

As a workaround, I keep on using RTSS but, after reading all the posts here since the release of these drivers, I shouldn't need it and NCP/NI should do the job. Is it there a way to make the limiter work?

Beware with using the FPS Limiter from nVidia. I tried it weeks ago and got a lot of stuttering, so decided to disable it from the nVidia CP.

Cheers, Ed

1 hour ago, edpatino said:

Beware with using the FPS Limiter from nVidia. I tried it weeks ago and got a lot of stuttering, so decided to disable it from the nVidia CP.

Cheers, Ed

Ah, I wonder if that might be the reason I’m seeing lots of micro-stuttering even on default scenery in the middle of nowhere. For example, Alice Springs airport in central Australia is default with around 4 Ai aircraft yet there were so many tiny stutters it was ridiculous. Frames locked at 30 and Core0 was around 60% utilised.

What arrangement are you using now? That was useful as it allowed mouse movements at 60Hz.

I've never had good success with Nvidia Max Frame Rate.  Always slight micro stutters.  So I've stuck with what has worked best for me.  Using Nvidia control panel but just changing the refresh rate of my tv to 30hz.  

I don't have a fancy TV/Monitor, so I use RTSS with setting of one half frequency, giving me 30hz equivalent.

That seems to work well for me.

34 minutes ago, micstatic said:

I've never had good success with Nvidia Max Frame Rate.  Always slight micro stutters.  So I've stuck with what has worked best for me.  Using Nvidia control panel but just changing the refresh rate of my tv to 30hz.  

I've tried that and the mouse lag is annoying. I now have to decide what is least annoying. Microstutters or mouse lag! 😁

31 minutes ago, Ray Proudfoot said:

I've tried that and the mouse lag is annoying. I now have to decide what is least annoying. Microstutters or mouse lag! 😁

I know.  It's not the best but I accept it.  That's why when Max Frame Rate came out as an option I was delighted.  Nothing ever goes our way in this hobby

3 hours ago, Ray Proudfoot said:

Ah, I wonder if that might be the reason I’m seeing lots of micro-stuttering even on default scenery in the middle of nowhere. For example, Alice Springs airport in central Australia is default with around 4 Ai aircraft yet there were so many tiny stutters it was ridiculous. Frames locked at 30 and Core0 was around 60% utilised.

What arrangement are you using now? That was useful as it allowed mouse movements at 60Hz.

I try to keep things simple here. Using the P3D internal frame limiter, with FPS locked at 27.

I also have installed FFTF Dynamic for P3Dv4 (from FSPS), that gives very good results regarding fluidity on my two systems. So most of the time, except on those very congested areas that we all know (London, NY, Seattle, as I remember), my FPS remains around 27 without any stuttering at all.

Cheers, Ed

Quote

Recommended Game-Ready WHQL Display Driver for Turing GPUs

Performance-wise, and due to noteworthy and persistent performance inconsistencies, and the overall and significant stability regression in DX12/DXR scenarios, 442.50/.59 is still our current recommended driver.

However, if you favor certain "Game-Ready" optimizations, support for DLSS 2.0 in certain games and for new G-Sync compatible monitors, or are affected by certain recent bug fixes, the recommended driver would be the latest instead (or better the upcoming Hotfix driver that will fix certain noteworthy issues, such as the annoying bug related with the NV_Cache being prematurely cleared).

 

1 hour ago, edpatino said:

I try to keep things simple here. Using the P3D internal frame limiter, with FPS locked at 27.

I also have installed FFTF Dynamic for P3Dv4 (from FSPS), that gives very good results regarding fluidity on my two systems. So most of the time, except on those very congested areas that we all know (London, NY, Seattle, as I remember), my FPS remains around 27 without any stuttering at all.

Cheers, Ed

I'll bear that in mind, thanks.

5 hours ago, jabloomf1230 said:

 

I've downgraded to 442.59, However, it didn't work at all. Looks like, with FSX and my laptop display, I'll have to stick with RTSS and its scanline x/2. I can force a simple FPS limiter with RTSS, but I also end up seeing microstutters (despite having the FPS indicator steady at 30). Strange.

Thank you all for your responses.

Edited April 23, 20206 yr by Luis Hernandez

Just a point of information, if you read my posts in this thread, I had no problem running any flightsim (XP11. P3D4, P3d5 and DCS) with this driver. I had other issues. I also have stated that people that run more mainstream PC games with this driver have concerns. I also stated that I reverted to 445.75, the previous version. I suggest that any time one changes Nvidia drivers that they uninstall the driver, delete the flightsim's compiler shader files and do a clean install of the new driver.

The NVidia frame rate limiter in the NVidia Control panel never worked for myself (although when accessing the limiter via the NVidia Profile Inspector it did).

Otherwise never found it particuarly useful myself given I can vsync @ 30 Hz anyway.

FYI: I tested the 445.87 drivers and found the option of Silk Smoothness had been removed. This I noticed pretty much immediately in P3D, rolling back to the 442.50 driver set restored the option of Silk Smoothness.

Cheers

 

Hi,

445.87 appears problematic.

Nvidia have released a Hot Fix Driver 445.98.

https://nvidia.custhelp.com/app/answers/detail/a_id/5022/~/geforce-hotfix-driver-version-445.98

Some users were complaining of stutters with 445.87.

 

Regards
Mark