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

[clear F1]

@BenganJ, @JHTrucker

SILK_Smoothness is set to 4 as before.
Thanks for all the help.
I've done a lot of testing, but sudden acceleration after deceleration is uncontrollable.

[BenganJ]

@clear F1

Can you give me one specific location, where you get this "rubber banding" problem?

[JHTrucker]

This is a frame time fix and not a frame rate fix.
If your vsync fps are constantly dropping below the vsync level then this won't / can't fix that problem.

In this pic you'll see 10 frames displayed one after another for a 1 second time period. 10 fps.
Each frame has 0.1 of a second to display itself.
.

Frametime example.png

.
1 = Choppy motion caused by frames being produced at different speeds within each 0.1 interval.

2 = Very choppy motion caused by most of the frames being produced very quickly and leaving a gap.

3 = Smooth motion. All frames produced at a constant rate.

All 3 examples run at a constant 10 fps, no fps drops, but 2 will show a slow down/speed up motion, but it still produces 10 fps.

[BenganJ]

@JHTrucker

Nice illustration! BTW, I've added this parameter setting to the first post of the NPI topic,
with a reference to this topic for a more in-depth explanation and recommendations.

[clear F1]

@clear F1

Can you give me one specific location, where you get this "rubber banding" problem?

Everywhere it happens. There is no specific place (city name), but it is a road after turning an intersection or with many vegetation.
I've often tested the roads to Białystok and its suburbs.

[BenganJ]

@clear F1

I watched your video today, where you delivered to Bialystok, but there were not a single "rubber banding"
event. I watch ALL your videos and I never see any "rubber banding" in them, why? Can you record a short
video with only a sequence you think is a "rubber banding" event?

[clear F1]

As reported, it repeats rapid deceleration and acceleration.
I'm using vsinc=2,3 and trying 144Hz, 120Hz, 100Hz, 60Hz. (60Hz only tests Vsync=2)
Each time, I rewritten and tested t_averaging_window_length in Config.cfg.
Now 144hz and Vsinc=1
I'm using Gsync. Same setting as today's YT Video.
I have not posted a video with rubber banding on YT.
Last but not least, there is a problem except Vsync=1 and it cannot be used.

Same as my previous comment, but can't you understand my English?

[clear F1]

2560x1440 144hz, Vsync=2, t_averaging_window_length=144.
You can see 72fps on the OSD on the upper left.
You can see it going up and down violently.
As mentioned above, gsync on/off happens regardless.
There is no such fluctuation at normal 144Hz.（Vsync = 1）
It will take a while before you can watch it on Vp09.



The blinker sound is also accelerated/decelerated.

[BenganJ]

@clear F1

I am sorry if I did upset you now, that was definitely not my intention. I just have seen very good looking
videos from you and wanted to see, what you you see when this phenomenon happens. From this short video
we can see a clear example of "rubber banding", where it normally should not occur, so I am very curious as
to what it is caused by. At the end you show in-game graphic settings, where one can see, that you specify
a Refresh rate as 144 Hz. What happens if you set it at the Default refresh value instead, any difference?
Maybe JHTrucker have an idea why this happen to you and not to me or JHTrucker e.g.! Let's wait and see
what he has to say! I only want this to be solved or at least explained why it happens, so that info can be
told to other people, who gets the same problem. Thank you very much for your cooperation my friend!

[JHTrucker]

@clear F1 - That short video isn't what i mean by "rubber banding", for me the forward driving motion slows down like you press slow motion button for a second and then it speeds up like pressing fast forward for another second. My fps don't change when that happens but yours do.
If i increase gfx settings too far then that's what i see in your video, fps up and down when looking a round etc.
The game only really uses 1 cpu core so if it's too busy it can't pass frames to GPU.

Perhaps gsync monitors are best kept at their highest hz with vsync off and set a frame limiter to control gpu usage. Recheck Roadrunners advise in NPI first post.

But it's crazy to keep trying to fix that when you/we don't know the cause.
So... start again:
Default NPI
Default config.cfg
Start game and set only in game gfx, No extras.
Drive around again. Ok?
Add NPI steps 1, 2 & 3 only.
Drive around again. Ok?
Add extras one at a time (AO / mirror distance / LOD's / DSR etc)
Drive around again. Only add more if it's ok.
That way you should find the cause.