[DX11] Help regarding Nvidia Profile Inspector (NPI)

[JHTrucker]

@AfxTwn
That guy isn't using our AA, just our AA bit.
Antialising Compatibility: 0x80000A7F
Antialiasing - Gamma Correction: On
Antialiasing - Lime Gamme: Enabled
Antialiasing - Mode: Application-Controlled
Antialiasing - Setting: Application-Controlled / Off
Antialiasing - Transparency Multisampling: Disabled
Antialiasing - Transparency Supersampling: Off / Multisampling
Also, x16 does nothing when set like this:
Anisotropic Filtering Mode: Application Controlled
Anisotropic Filtering Setting: 16x
Plenty of other incorrect/do nothing settings...

But AA will kill the FPS and VR needs all the fps it can get.

[BenganJ]

@JHTrucker & @AfxTwn

Well, isn't it like a dual monitor setup when it comes to GPU/CPU load or is it becoming
even worse due to the job of creating stereo images as well? When I used the phone based
HMD I used a ReShade shader pack, aimed at the job to generate the SBS images, called
SuperDepth3D digging up the 3D out of the game rendered depth map. It was damn fast
and I then transferred the images over WiFi to the phone using Nvidia Gamestream, which
was controlled by a phone app called Moonlight! That was during the DX9 era, but as far
as I can recall, the AA worked as usual!

[AfxTwn]

@AfxTwn
That guy isn't using our AA, just our AA bit.
Antialising Compatibility: 0x80000A7F
Antialiasing - Gamma Correction: On
Antialiasing - Lime Gamme: Enabled
Antialiasing - Mode: Application-Controlled
Antialiasing - Setting: Application-Controlled / Off
Antialiasing - Transparency Multisampling: Disabled
Antialiasing - Transparency Supersampling: Off / Multisampling
Also, x16 does nothing when set like this:
Anisotropic Filtering Mode: Application Controlled
Anisotropic Filtering Setting: 16x
Plenty of other incorrect/do nothing settings...

But AA will kill the FPS and VR needs all the fps it can get.

So what settings would you recommend? I did wonder why he was using AA seeing as that's generally suggested to turn off for VR.

[alonzam99]

Is there a good solution for the g cam window block for trackir users ?

@BenganJ I already calmed down I just ask because I want this feature for trackir and JHTrucker solution is not so good.
can be just a temporary solution but we still need to find a normal solution for this.

[clear F1]

@BenganJ

About using DSR x1.78.
There is one thing I understand. The fps drops to 20 fps in the suburbs where there is a lot of trees, not in the urban areas.
It happens in places with similar vegetation on any map such as RoEx, Promods, Rus areas. It is the same even if NextGen2.0 and Fael Environment are removed. Is it a LOD-related setting?

[BenganJ]

@clear F1

If it was a LOD related issue I would have it too, as I have ALL LOD settings at maximum
specified in first post! And I use Grimes, Next-Gen AND Fael in my profile. I assume you
are setting both the desktop AND in game resolution that that DSR one and then record
also at that resolution, 2560x1440p60 using r_vsync "2"?

[clear F1]

＠BenganJ

Even now I confirmed without returning the setting, Vsync of Cofig.cfg is 2, it is 2560x1440p60 in NCP, and it is set to 2560x1440 in the game.
I tried setting the vegetation in the game to Low, but it doesn't change.
I can't think of anything else, but I think it's safe to say that the road that has a lot of grass and trees will drop to 20fps.

[BenganJ]

@clear F1

You say that "it is 2560x1440p60 in NCP", available as a resolution or
is it in fact configured as the resolution of your monitor? I have driven
on roads with VERY many trees and vegetation at the sides, but I do not
get any FPS drop there.

[clear F1]

＠BenganJ

I don't understand the meaning. NCP setting is 2560x1440p60 and desktop resolution is 2560x1440.
A reference video will be posted in a few minutes.

[BenganJ]

@clear F1

Okay, that was what I wanted to be confirmed. Thank you! To me this
problem of yours is VERY odd, as the card you have got is at least slightly
more competent than mine and I do not have this problem. Maybe JHTrucker
or someone else have an idea what it can be. We will see!