DX11 strange "rubber banding" effect - possible solution (1.36-1.49)

[clear F1]

I'm sorry. The previous test result was no cargo. When I execute the delivery test, it repeatedly decelerates and accelerates. fps is between 40 and 60.

[BenganJ]

@clear F1

But then you haven't tested without GSync yet? Can you test by deactivating GSync,
but with these settings in config.cfg?

[JHTrucker]

@clear F1 & BenganJ

When i first worked out what this uset t_averaging_window_length was all about and i posted the info in NPI thread for feedback. At that time i changed 20 to 30 but had no noticeable change as i was running in 32 bit with 3Doverrider providing the triple buffer and so i didn't have a problem to start with.
It was only when i set it to 5, a week later, to try and force a problem that i got rubber banding. i then remembered why i don't use 64 bit... it rubber bands.
So i set it to 60 and started driving around in 64 bit mode. It worked well over the past week, so i made the post.
What i don't know is what is the best number to use for everyone. Twice my 30 fps worked... 60 but perhaps if the number is too high then cpu usage increases for working out the average and cause other issues, stutters?
Perhaps the advise should be try 30,40,50 etc one at a time? I may give 40 a try next.

But as this is frametime for vertical sync then i don't think it will help with gsync or freesync because they don't use vsync, i don't think. I can't test this for myself.

I would say, try using your monitor as standard, without gsync on, for a test.
If it works well then that's good for this game only. Use gsync for other games that suit it best.

I might add, that until dx11 was added into ats/ets2 i could run 32 and 64 bit in dx9 without issues... dx11 64 in these games, as standard, doesn't work well for me until this change.
Project cars 2 is dx11 64 bit only and works fine on the same pc with all 4 cpu cores constantly in the 90's for a full hour long race!

[BenganJ]

Mind you folks, if you are on a Nvidia driver version above 442.74,
you have lost the NPI setting SILK_Smoothness functionality, which
works much like what we're talking about here. I have talked about
this in the DX11 NPI topic several times, so be aware!

[clear F1]

I saved the starting point and did 6 different tests in the same state.
Turn off g-sync on the monitor side and NCP
144Hz, 120HZ, 100Hz vsyinc2
And 3 (72,48,60,40,50,33)
I tried, but both repeat acceleration and deceleration at the same place. It happens when you turn left or right at an intersection and when you can see many plants.

I turned on g-sync and returned to 144Hz, vsync=1.

[BenganJ]

@clear F1

Which Nvidia driver version are you using?

[clear F1]

The NCP setting SILK_Smoothness is 4.

4274

[BenganJ]

@clear F1

But which driver version are you using and also which NPI version?

EDIT: I am off to bed now, see ya later!

[clear F1]

4274 and 2.3.0.10

As I said in the beginning when I changed monitors, Vsync is useless to me other than 1.
Regardless of whether g-sync is on or off.

[BenganJ]

@clear F1

442.74 and 2.3.0.10! Then you have the SILK_Smoothness functional.
Well, we have now tried most of the available options, so choose the
one that works best for you.