[DX11] Help regarding Nvidia Profile Inspector (NPI)

[BenganJ]

@clear F1

Thank you for participating in these tests! Sleep tight, see you later my friend!

[Tapir]

If someone wants my Eurotruck2.nip :

https://drive.google.com/file/d/1SuEzFG ... HOJOS/view

[BenganJ]

@Tapir

I'll have a look at it when I've got time!

[Tapir]

:D :D :D :D :D :D :D :D

[Road Runner]

As sadly we still haven't progressed with those graphic anomolies 9fingers still crossed) - could we look at at some further graphic improvement. Time perhaps to look at Ambient Occlusion!

For the last few days I have been testing various AO flags. One that appears to work very well indeed 0x000E0000.

For the technical:
Setting 0x000E0000 contains
FE 31 80 89 63 80 8C 0C 00 00 00 00

This is a group of three values:
FE 31 80 89 - Insertion logic bits
63 80 8C 0C - AO parameter bits
00 00 00 00 - ??? (Debug bits?)

Now this flag is already in the Nvidia driver. It is in NPI Ambient Occlusion compatibility just scroll down til you find it listed as Crysis3. All your other settings can be retained
Ensure that after entering the flag into NPI AO, you have turned on AO. Under common:
Ambient Occlusion setting: High quality
Ambient Occlusion usage: Enabled

The only other recommendation I make for this test is please turn off all Shades (without a shade you will need to use the work around method - sorry!).
So please test, I think you will find it worth it. For me it has most impressive and have given up on Shades (Sorry Mr B).

Let us know how you get on.

My NPI Settings:
Ambient Occlusion compatibility: 0x000E0000(CRYSIS3)
Antialiasing compatibility (DX1x): 0x80000072
Frame Rate Limiter: Off
Frame Rate Limiter Mode: Default
Maximum pre-rendered frames: 3
Vertical Sync: Force on
Vertical Sync Tear Control: Adaptive
Antialiasing Behaviour Flags: Disable Antialiasing at NVIDIA Control Panel
Antialiasing - Line gamma: Enabled
Antialiasing - Mode: Override any application setting
Antialiasing - Setting: 8xQ [8x Multisampling]
Antialiasing - Transparency Supersampling: 8x Sparse Grid Supersampling
Sharpening: 0.17
Sharpening Filter: On
Sharpening Value: 0.50
Anisotropic filtering mode: User-defined Off
Anisotropic filtering setting: 16x
Texture filtering - Driver Controlled LOD Bias: Off
Texture filtering - LOD Bias (DX): -1.5000
Texture filtering - Negative LOD bias: Allow
Texture filtering - Quality: High quality
Ambient Occlusion setting: High quality
Ambient Occlusion usage: Enabled
Power management mode: Prefer maximum performance
Memory Allocation Policy: x00000002
SILK Smoothness: 0x00000004

[BenganJ]

@Road Runner

Wow, you haven't been sitting still lately! Sounds very interesting,
but I must know what you mean by "turn off all Shades"! Do you mean to NOT use
the shaders in ReShade? If so, what about the flipping graphics? If not, what do you
mean?

[Road Runner]

@BenganJ

By turning off shades, I mean not using them at all, at least for your first test. It is importent that any result should be unaffected by any other input. You can then make a fair judgement of using AO. To avoid flipping graphics - the workaround from an earlier post:

Before initial drive set scaling to say 25% (probably anything other than 100%) go into Drive tht should clear any previous anomoly. Hit Esc, then into settings/graphics restore Scaling to 100% Hit Drive again and you should be all set to go.

On ending a session hit Esc and before quitting change Scaling to 25% and then quit. On your next session simply load the profile and then change the scaling back to 100. Before quitting reset scaling to (say) 25%


After testing you may wish to try with Shaders (I did). For me, I am looking to find a shader that is extremely benign in order to avoid the work around. Give it a try Mr B, I think that you will probably be impressed. I confes I was blown away! :D :D :D

[BenganJ]

@Road Runner

I will surely test this and I will start without my ONLY shader, the Smart_Sharp one,
then if all goes well, I will test with it too! But it will probably have to wait a bit,
as I'm VERY busy testing other cool stuff right now! I will be back! :D

[Tapir]

FOLKS: A big mistake has crept in:

You all use the wrong DX11 compability settings: WRONG : 0x800000F72

Here see :

On the Steam ETS2 forum there is a post suggesting the use of a dx11 compatibility setting of 0x80000F72 with AA and SSGSAA x 4 settings scaling at 100% On testing it appears to work well with great AA! However on closing the game crashed and the profile became corrupted.

Suggest caution with anyone testing - create a new or have a test profile.

Interested to see what you and others find Mr B

correct and NO RAIN in cabin therefore is 0x80000F72 :!: :!: :!: :!: :!:

[BenganJ]

@Tapir

You're talking SHIT now, mate! FIRST of all, I have already researched and pointed out that the F
in that pattern do NOTHING, so I have since then run with 0x80000072, which also is what I say
in first post! SECOND, you say that 0x80000F72 is WRONG, then you say the CORRECT is 0x80000F72.

PLEASE, mate, don't do these horrible things! You just confuses people with these kind of acts!