[DX11] Help regarding Nvidia Profile Inspector (NPI)

[BenganJ]

@Sansemiano

Yes, I don't think you will find any external solution to those occasional freezes in the game, as I
am pretty sure they are due to bad designed or an old game engine. About the shooter type of
games, I have no clue, as I very seldom play them and then it's almost ONLY Tomb Raider ones
together with my son.

[Sansemiano]

@BenganJ: I'm afraid so. No remedy for the freezes anytime soon.

[clear F1]

@BenganJ

I have received your previous cautionary advice, and the settings below have been set for more than a week.
--- Sharpening Value ------------------------------------ '0.35'
--- Texture filtering-LOD Bias (DX) -----------------'-0.7500'

If this is adjusted further, even the number on the meter will be blurred.
As I wrote earlier, flicker does not change with or without DSR (4K) (1440p native).

[JHTrucker]

@clear F1 @BenganJ
My point to trying 2xAA was to check if increasing the resolution far beyond native would reduce the need for 4xAA and therefore increase FPS at that point.

If it's bad... it's bad... test over. Thanks.

After all, the scs cheerleaders claim you don't need a "AA hack", you just increase scaling to fix it.

I assume you are changing desktop res to match game res on each test?

[BenganJ]

@JHTrucker

Yes, I've pointed out several times the necessity to keep the desktop and game resolutions the same and
I think he knows very well to do that. Right now I'm trying to get a grip on clear F1's classification of BAD
AA. What's that to him and I want to get rid of sharpening too in that equation.

[JHTrucker]

@Sansemiano
No one gave feedback to this posted last week viewtopic.php?p=24816#p24816

So here's a bit more info, i think you should try:
config.cfg
uset t_averaging_window_length "20"
That's the number of the past frames used to calculate the current frame duration.

Change to 60+ and you'll get a better average value for timing on the current frame.
At 20 that's just a split second. Any lag or stutter in those 20 past frames will impact the quality of the current frame timing, i think.

As a test i set it to 5 and found, with my always smooth vsync 30fps, got random rubber banding, the game world slows down and then quickly speeds up again, randomly. Running now with 60, as with 20, gives me smooth fps.

So people reporting that strange behaviour since DX11 game version came out should try this, increase to 60+, instead of the usual answer of turn off vsync.

It's worth a try.

[BenganJ]

@JHTrucker

Right, I changed 20 to 30 and felt it got a bit better, but as you say, this is
only a calculation help for the game, so as long as it doesn't have any bad
impact one could get a better average value by raising it more. I'll do some
more testing!

[JHTrucker]

@BenganJ - Well whilst you're driving around testing that...
Give this a go at the same time:
Use the in game zoom feature with head tracking instead of pressing a button.
viewtopic.php?p=24823#p24823
No comments yet after a week... disappointed!

[BenganJ]

@JHTrucker

I think I have told you quite long ago, that I changed controls.sii to enlarge the area in X and Z directions,
the horizontal plane, in the cabin just to be able to use my regular headtracking to zoom e.g. towards the
left and right mirrors. I NEVER use assigned buttons for that. But I'll see if I can test that too.

[Sansemiano]

@JHTrucker: I didn't realize you aimed the t_averaging_window_length config suggestion as a possible solution for preventing or dimishing freezes. I have in both games now configured t_averaging_window_length "100". Just did a 400 mile haul in ATS (a profile with all Team Reforma Maps) and had not a single freeze. BUT, ATS is less susceptible to this problem. I will report further after doing some hauls in ETS2.