[DX11] Help regarding Nvidia Profile Inspector (NPI)

[Tapir]

No shit look at the original steam link please :!: :!: :!: :!:


https://steamcommunity.com/app/227300/d ... 696614801/

The Difference is only a 0 :!: :!: :!: :!:

WRONG: 0x800000F72
RIGHT: 0x80000F72

[BenganJ]

@Tapir

BUT WE HAVE NEVER USED THAT VALUE HERE AT ALL, SO STOP NOW!
WE HAPPEN TO KNOW THAT AFTER THE x THERE SHOULD BE 8 DIGITS!

[Tapir]

See page 1:


---------------------------------------------
Presently recommended NPI settings:
---------------------------------------------

--- Antialiasing compatibility (DX1x) ------------------ '0x80000072' //We're hunting for bit patterns that resolve the present anomalies. [See Note 1]

That`s WRONG!!!

Original link:

https://steamcommunity.com/app/227300/d ... 696614801/

[BenganJ]

MATE, COUNT THE DIGITS, INSTEAD OF THE 'F' THERE IS A '0'!!!!
YOU ARE VERY NEAR A BANNING HERE NOW, SO STOP, PLEASE!

[Road Runner]

Mr T, with the greatest respect, please read ALL the posts in this topic from page 1 to date. You will see that 0x80000F72 was the very first one we actually tested - suggested by Guru Knight some 5 years ago, except ofcouse ets2 didn't have dx11! I can create and test multiple flags that will turn on AA in a Nvidia driver, All of them including 0x80000F72 produce rain in the cab! Therefore there are so many flags, so that to avoid confusion BenganJ decided to run with just one (the one on page 1). A decision I fully support. It was originally believed that profiles under test were being corrupted - in fact they weren't, it was not then understood that matters could be prevented or corrected by using a workaround or Reshade!

So please bring yourself fully up to speed by reading the developments in this record as they happened.

[BenganJ]

@Road Runner

I ran a couple of tests here with that Ambient Occlusion compatibility bits set.
To be able to run at all, I had to totally remove ReShade from the game, but
for a test, that's OK. To me, setting that parameter felt like a HUGE FPS drop
and it blurred the graphics heavily. Also I felt that flickering got worse, so can
you describe exactly what you mean is the gain setting this parameter? For me
this was a step backwards!

[Road Runner]

On my system it runs extremely well, everything clear and sharp and no flickering. No problem with frame rates either. I wonder, assuming your sig is still correct and you are running win 8, wonder if that could be an issue. Sorry, interesting to see how anyone else gets on! :(

For me it's the icing on the cake :D

[BenganJ]

@Road Runner

A while ago I actually looked at the options for that bit pattern in NPI, but
didn't find any specific for ETS2 or ATS, so I skipped that, too many to test
one by one.

I'll do some more tests later, but for now I have to test another goodie!

[Road Runner]

@BenganJ

Unfortunately Mr B Ambient Occlusion (HBAO) is very computationally intensive. Please forgive me when I say that your hardware (maybe OS) does not appear to be up to it. So now having looked more closely at your specs, I am not surprised of the result of your test. To successfully use AO requires a good fast processor with a good performing graphics card. So unfortunately is not going to be of universal benefit!

Sorry for having to say the above Mr B but be assured my regard for you and all your efforts remain undiminished. :)

[BenganJ]

@Road Runner

Oh, don't be sorry mate! Things are there to be investigated and I'm fully aware of the
hardware limitations I've got. Ambient Occlusion is a question of getting better lighting
conditions, especially the shadowing result, so I'm not surprised at all. I can probably
use it, but I will be on a sort of limit then and that is most often not recommendable.
I will probably add something about it in the first post for those, that have capable
hardware, so thank you for the tips. BTW, how have you come to the conclusion that
the Crysis 3 pattern is the best for this game, as there are pretty many to choose from?