For the record, there's an option called "frc.target.tolerance", which is equal to 0.02 by default.

It is good!

ionutm80
Input framerate in the box 'fi_target'. It works too. In you case: 59.937

Hi, already tried that but no change, SVP is still showing playing at 59.94 ...
In the end I gave up on x64 chain and reverted to ReClock:
- set the resolution in Win 10 at 59Hz (59.938Hz as shown by ReClock and 59.9376 as shown by madVR)
- left display mode madVR can switch to empty
- set frequency of 59.94 in ReClock (manually for each movie for the moment ...)
==> now madVR does not drop anymore frames after ReClock turns green and even the estimated ones show 1 frame drop in either 3.xx hrs, 14.xx hours or even 1.2 days (I still do not understabd why it's not locked but nevertheless the estimated time interval for dropping a frame > movie length)
I decode audio with LAV Audio to PCM and then play through my Asus Xonar U7 analog output directly to Logitech z906 so ReClock can do "its magic".

Input framerate in the box 'fi_target'. It works too. In you case: 59.937

Hi, in order to achieve my desired fps of 59.937 I need a factor of 2.4999 to input in fi_target which is not accepted being rounded to 2.5, only 3 decimals works but that does not help.
Any ideas?

just use reclock / mpv (display mode here)

if I change target resolution from 59.94 to 59.937?

Maybe target refresh rate?
Use 'fi_target' parameter. It must work in your case. See droped frames in madVR statistics (by Ctrl-J while playback and in the fullscreen mode).
Just try.

Ok, I'll try that and see what is happening.

if I change target resolution from 59.94 to 59.937?

Maybe target refresh rate?
Use 'fi_target' parameter. It must work in your case. See droped frames in madVR statistics (by Ctrl-J while playback and in the fullscreen mode).
Just try.

Thanks in advance.

So, you want to make whether the SVP or display rate match exact each other, right?

Exactly my issue, what if I set SVP to interpolate to screen rate? Would this mean that it would try to reach 59.937, my display actual resolution, instead of 59.94?

Hi, Am I missing something here ... or in fact for you is the same because display is at 59.974... and composition rate at perfect 60 which also translates in dropped frames.
My problems is not with the composition rate but with the display rate enforced by NVidia driver being 59.937 instead of 59.9400x as I'm getting with Intel HD4400 for instance ...
Or I'm loosing something?

Oh, sorry, I misunderstood your first post.

So, you want to make whether the SVP or display rate match exact each other, right?

If your concern about the different about ~0.01 which the cause of dropped frames, you can rest easy that it wasn't the case.
Dropped frames is purely because the system couldn't keep up with the calculation so in order to sync with the audio, the renderer starts dropping frames (CMIIW).

In my case, the current system I have has very low specs so it just couldn't play smoothly without closing other resource-intensive apps such as firefox and chrome.

As long the different doesn't differ too much, it's neglectable.

Check the attachment of my setting for exact 60fps

Hi, Am I missing something here ... or in fact for you is the same because display is at 59.974... and composition rate at perfect 60 which also translates in dropped frames.
My problems is not with the composition rate but with the display rate enforced by NVidia driver being 59.937 instead of 59.9400x as I'm getting with Intel HD4400 for instance ...
Or I'm loosing something?