[DX11] Help regarding Nvidia Profile Inspector (NPI)

[BenganJ]

@Pancreas

I agree totally, on those power lines, there you have absolutely NO AA!
Before I ask you to produce all your settings, I must ask you, if you have
gone through the Q&A, questions and answers in the first post? If NOT,
please do that first, because if it still doesn't work, you and I have to
work hard and you will have to give me all your settings! Especially I
want you to look at these Q&As:

Q - My gfx have no AA.
A - RE-CHECK STEP 1 and also make sure game SCALING is always 100%.

Q - My settings are EXACTLY as your instructions state - STILL NO AA
A - Ensure you picked SPARSE GRID SUPERSAMPLING and not SUPERSAMPLING in NPI STEP 1.
-- OR --
A - Rename or delete global config,cfg and start the game to generate a new one.
Now make the "basic" changes only - STEP 3.
-- OR --
A - Reinstall the current Nvidia driver making sure to select "clean install" option.
Start again from STEP 1.
-- OR --
A - If you have a multi screen setup, you MUST use the supplied multimon_config.sii file from STEP 2.

And READ carefully!

[Road Runner]

@BenganJ

Re: Frame Rate Control recommendations in first post:

Could I suggest enlarging on the advice regarding GSync monitors.

If frame rates for ETS2 are ALWAYS LESS than the refresh rate of the GSync monitor then simply set GSync to ON in Nvidia Control Panel/NPI

If frame rates for ets2 are ABOVE or VARY between being sometimes above and sometimes below the refresh rate of the GSync monitor then: 1. Set GSync ON, 2. Turn VSync ON, 3. Set Low Latency to ULTRA in Nvidia Control Panel/NPI


By way of explanation, if frame rates are always less than the refresh rate then GSync is always on and will do its job! However where the situation is that frame rates always or often exceed the refresh rate then GSync is disabled resulting in tearing. Setting VSync acts as a brake to stop excesive frame rates asnd using ultra low latency reduces the frame rate by 3fps thus ensuring that the refresh rate remains in the GSync range.

[BenganJ]

@Road Runner

Now I have to clarify one thing first. What about the case when the frame rate is alternating
below and above the refresh rate? We have to be VERY clear here, so please, take another round
of brainstorming on the formulation of the words!

EDIT: The world of solutions to monitor syncing of the output from games are PLENTY, as I tried to
explain in the Note 3! But isn't it basicly so, that for a G-Sync compatible monitor, the only thing
you should have to do is enable G-Sync support in NCP? How about in that case also set in the NCP
Max Frame Rate to a proper value or as it is called in NPI, Frame Rate Limiter V3? To be honest, I
can't see ANY gain in getting as high a frame rate as possible. I would say, set a MAX frame rate,
and both CPU and GPU will be happy and thank you for your cooperation! :D :D :D

[Road Runner]

@BenganJ

Have edited above post - hope its clearer now. :D

There seems to be a misconception about GSync monitors in that you only need to enable GSync and the refresh rate will always sync with the video output of the game. Sadly that is not true - with game output above the set refresh rate of the monitor - GSync is disabled. It is also disabled if frames drop below a certain level, around 30 fps, I believe. Where the output frame rate varies both above and below the solution from Nvidia is given above. I suppose if your game output is always above then simply use VSync - then perhaps why did you buy a GSync monitor?

In terms of max frame rate control using max frame rate in NPI isn't best practise. For example a monitor set at say 100 is probably not 100 but maybe 99.7. Not all individual frames render exactly at the same time rate. Using VSync is a much better method of capping to ensure synchronisation. Using Ultra low latency ensures that the monitor remains in GSync.

I do hope that this clarifies everything! :D

[BenganJ]

@Road Runner

In terms of max frame rate control using max frame rate in NPI isn't best practise.

Why isn't it best practice? And mind you The Frame Rate limiter V3 in NPI is exactly
the same as Max Frame Rate in NCP. Let's say you have a 144Hz monitor. Do you REALLY
need to get that high frame rate, which you mostly won't get anyway? Or let me put it
this way, why do you have to let the frame rate be at maximum generated all the time?
If I had a 144Hz monitor I would definitely cap the frame rate at say 60 Hz, because you
don't need higher frame rate than that and every frame you DON'T generate, the CPU
and GPU will credit you for!

[JHTrucker]

@Road Runner @BenganJ
I don't have a GSync monitor, but reading what has been written, wouldn't it make sense to set frame limiter to a value lower than your refresh rate and therefore GSync is just always on?

[BenganJ]

@JHTrucker

That's about exactly what I suggest! As usual I use too many words though!

[JHTrucker]

UPDATE: Files deleted as this idea didn't work as expected, the reduced widths glow when the sun is pointing at you.

If you're currently enjoying using Triple AA V2 and really like the image quality you've got but would still like a few more frames, then you may or may not like this idea.

Full image width reduction to reduce the rendered area but keep the same quality for the rest.
Basically, the left & right monitors have a reduced width leaving a black vertical bar at the far left and far right.

See the attached low res pic to illustrate the difference between full width, 10% WR (5% left & 5% right) & 20% WR (10% left & 10% right).
Compare right hand side door window area.

My tests showed that a 10% width reduction gave approx 8% FPS increase and approx 16% FPS for 20%.
So if you're around the 50 FPS area you could hit a stable 60 using 20% WR.

If you want to test this, assuming you've already got triple AA V2 setup as per first post, steps 1, 2 & 3, then do this:
Rename your current multimon_config.sii for safe keeping.
Replace with new multimon_config.sii from Triple.AA.WR10.zip or Triple.AA.WR20.zip - both have FOV 50.
Fire up ETS2/ATS and see what you think. Is the Width reduction worth the increased FPS? Only you can answer that.

Still keen to test further?
Changing to your preferred FOV:
Using FOV 60 and 10% WR as an example.
3 x 60 = 180 : 10% of 180 = 18 / 2 = (9 FOV reduction)
Dummy FOV 60 - Left monitor FOV 51 - Center FOV 60 - Right FOV 51
Dummy FOV must always equal Center FOV.
Do not make any other adjustments to DUMMY as this is the key to AA on multi-monitors.
Now adjust the left/right image projection:
9 (FOV reduction) = 0.09
Left / Right horizontal_fov_relative_offset: (+/-)1.000000 - 0.09
Left: horizontal_fov_relative_offset: 0.910000
Right: horizontal_fov_relative_offset: -0.910000
(+/-)0.910000 is the new default. You then add your bezel adjustments to this new base value, if that's what you do to make your bezel adjustments.

As an extra thought, looking at the full width image (top), you could just lose the whole 10% from the left side only as it's just cab interior anyway, thereby keeping the full right door window.
3 x 60 = 180 : 10% of 180 = 18 FOV reduction
Dummy FOV 60 - Left monitor FOV 42 - Center FOV 60 - Right FOV 60
Dummy FOV must always equal Center FOV.
Left: normalized_x: 0.100000 (10% from far left)
Left: normalized_width: 0.233333 (10% off left monitor standard width)
Left: horizontal_fov_relative_offset: 0.820000 :18 (FOV reduction) = 0.18
Right: normalized_width: 0.333333 (full standard width right monitor)
Right: horizontal_fov_relative_offset: -1.000000

And that's it... couldn't be simpler!

If you've read this far, thanks for humoring me.

[BenganJ]

@JHTrucker

SPOT ON! I'm already off to link to your post in the first post! :D

EDIT: Reference to that post added to Step 2 information! :D

[JHTrucker]

@BenganJ - Thanks.
You stopped me from thinking about reshade...