[DX11] Help regarding Nvidia Profile Inspector (NPI)

[JHTrucker]

@Pit-O-Matic - I've used 2xMSAA 2xSGSS for the past 4 years (since we got this working) and combined with r_sun_shadow_texture_size "8192" really helps with the tree flickering or "6144" if fps drop too low around large groups. Default is 4096.

I have long since stopped updating my old driving pc, steam offline and game version 1.41. Higher versions have rebuilt areas that kill my fps and make for an annoying drive, instead of a pleasant one.

SCS added all the extra details so the view point fly around thing or city intros would look good... but it's a driving game and most of that detail can't be seen whilst driving, but you can certainly feel and see the fps drops in those areas.

[MercDriver]

Hi I am in the process of upgrading my system for what will be the last time.

I am looking at getting a Dell Alienware M18 R2 with a RTX 4080 GPU and Intel i9 14900HX CPU. I want to couple this with a LG UltraGear 4K Gaming Monitor 27GR93U, 27 inch, 4K, 144Hz 3840x2160 res.
Well that was my wish list! What I am not sure of is how this system will work with ATS/ETS2 both now and in the future post version 1.50 or how to set it up with NPI which I have been using with great results for many years.
Any help, or advice would be most welcome.

Thanks in advance.

[JHTrucker]

@MercDriver - I see you have your hardware answer on the scs forum.

In regard to NPI, let's just hope for 1.50+ scs has finally added proper AA to their games so we don't have to rely on these 3rd party hacks...

You say you've been using NPI for years, I assume its 4xMSAA, and that means a huge performance hit.
So, if you want to see what sort of performance your current hardware has then disable the NPI AA by simply changing in game scaling to 125% or 200% and look at your fps.
Whilst not a nice picture to look at it should give an idea of what fps to expect if the game were to have it's own proper AA enabled.
Set scaling back to 100% after test.

[truckcrasher68]

Just installed ATS "1.50 experimental beta". Without NPI the game still doesn't look "great". But with NPI when I hit "drive", all I get is a black screen. Is that the end of NPI? Thanks.

[JHTrucker]

Thanks for the report.

I'd already updated the first post because I suspected this would happen...
"MSAA works with game versions 1.36 to 1.49 using DX11 only.
Game version 1.50+ has TAA implemented and therefore this MSAA shouldn't be needed any more?"

SCS stated that they've been working on the rendering system and so I'd expect that the 'Antialiasing compatibility (DX1x) hex value' will need to be changed to suit... but that's a lot of guessing / checking / testing, again...

Perhaps it's just a case of making sure all in game AA is disabled?
Or
Ensure you are still using the step 2 file.
Or
SCS haven't quite finished working on TAA and it'll be improved during the beta, but then I'm sure they could have seen how it looked and improved it before releasing it if they thought it needed it...

Anyway, I don't use beta's, so can't help yet, if ever...

[Ronin]

Well I think we can close the chapter with v1.50
NPI doens't work anymore I think.

One thing is sure: "Antialiasing compatibility (DX1x) ------------------ '0x80000A7F' " Gives a black screen!

[Road Runner]

I'd be surprised if it was the end of NPI, after all you can use NPI with MSFS2020 and others that also use TAA! The likely cause is as suggested, the AA compatability hex.

[Ronin]

Well at the moment I can't use NPI

[ArtemiySvarog]

I did a driver update, the graphics enhancement stopped work. Then I rolled back a videodriver and it did not work - the graphics enhancement does not work.

[clear F1]

Did you save the NPI settings before updating the driver? If saved, load the saved file.
If you have not saved the configuration data, you need to re-configure the NPI settings on the first page.