[DX11] Help regarding Nvidia Profile Inspector (NPI)

[Arayas]

where do you drive when this is taken place?

[iberks]

where do you drive when this is taken place?

Promods, regardless of the location. Its same on all heavy under light conditions except highway poles/lights or roads between high amount of trees or when I pass another trucks (not cars or busses)

[JHTrucker]

@BenganJ - menu AA - A simple test:
ATS - 2xMSAA - Vsync 2 (30 fps) - traffic 0 - skybox 0 - weather 0
Using Afterburner to show info.
Use console to change menu_aa back and forth a few times:

Driving screen - no driving - just parked up.
0 = 54% gpu usage and no difference with gpu memory etc
8 = 54% gpu usage and no difference with gpu memory etc

Menu garage screen "Home at last" left to run a loop.
0 = ~20% gpu usage and no difference with gpu memory etc
8 = ~50% gpu usage and no difference with gpu memory etc

Now with 4xMSAA
Menu garage screen "Home at last" left to run a loop.
0 = ~40% gpu usage and no difference with gpu memory etc
8 = ~99% gpu usage and no difference with gpu memory etc

Conclusion:
menu_aa 0 = MSAA @ 4x or 2x = best image quality & lower fps
menu_aa 8 = SSAA + MSAA @ 4x or 2x = poor image quality & higher fps
So there really shouldn't be any issues while driving and the menu screen should run with a cooler gpu when using our MSAA only.


Until Hg201 answers my questions on this post viewtopic.php?p=39658#p39658 we can't do much more, his frame time might be 20 in which case change to 60 or 60 and needs increasing... ???

[BenganJ]

@JHTrucker

Thanks mate, as that confirms my findings too. I think though that his problem
could be dependent on where he was driving, so we'll see what he reports later!

[Hg201]

@Hg201 - "Driving a frog" was my line! From the other topic... glad it describes the problem.
uset t_averaging_window_length "60" <-- is this what you are using currently?

My t_averaging_window_length is "240"!
But this value is guesswork because I don't monitor FPS while I play.

I have a 120Hz gsync monitor and in NPI "Frame Rate Limiter V3" is set to 118 FPS.
Display resolution is 3840x1600.

What's the best way to monitor FPS? Steam's in-game FPS counter?
What about GPU and CPU usage?

Where were you driving when you got the rubber-banding effect? Can you verify that you get
it all over or is it only in certain areas?

I was somewhere in Spain when I got the frog-driving experience. It makes me very nauseous so I would prefer not to try and find all the places where it occurs.

[Hg201]

I just did a small job in Denmark with FPS monitoring. It stayed nailed at 118 FPS, maybe two or three times I saw 117 FPS for a fraction of a second.

[BenganJ]

@Hg201

And that drive in Denmark was with g_menu_aa_limit "0"?
If so, that indicates that your problem is more a question of WHERE than that value!

[JHTrucker]

@Hg201 - MSI Afterburner allows you to monitor gpu/cpu usage and fps etc but "frog driving" isn't about dropping frames, it's about the time each frame needs to display, ideally always equal to give a smooth motion. Your fps will always be stable when "rubber banding".
Your best bet is to lower your fps limit to 99? That will lessen the load in demanding areas and probably prevent the "frog driving". Yes you have an high end gpu but the game still only uses 1 cpu core to generate all those frames at your high res. Then the gpu easily renders those for you.

[Marx]

@BenganJ @JHTrucker

The ´g_meu_aa_limit set to "0" instead of´g_menu_aa_limit "8" made all the difference for me in ATS and ETS2. Both in the menus and the game. it´s a real game changer. Thanks for all your support. You guys are real experts.

[BenganJ]

@Marx

Don't look at me! I wish I could say the same, as this version of the game, 1.40, has ruined it for
me to some extent.