[DX11] Help regarding Nvidia Profile Inspector (NPI)
Re: [DX11] Help regarding Nvidia Profile Inspector (NPI)
Big enough i think :oops: :ugeek:
Re: [DX11] Help regarding Nvidia Profile Inspector (NPI)
File looks ok.
This fixed it for hasteflex... re-install the Nvidia driver and this time tick the Clean install.
Post by hasteflex » February 27th, 2020, 8:03 am
BenganJ wrote: ↑February 26th, 2020, 11:01 am
Okay then! I wonder if that could be the cause of your problem.
Follow JHTrucker's recommendation to re-install the Nvidia driver
and this time tick the Clean install. See if that gives you a full
Other section in NPI!
Okay, so I did a clean install of the Nvidia drivers again and......
IT WORKED !!!!
This fixed it for hasteflex... re-install the Nvidia driver and this time tick the Clean install.
Post by hasteflex » February 27th, 2020, 8:03 am
BenganJ wrote: ↑February 26th, 2020, 11:01 am
Okay then! I wonder if that could be the cause of your problem.
Follow JHTrucker's recommendation to re-install the Nvidia driver
and this time tick the Clean install. See if that gives you a full
Other section in NPI!
Okay, so I did a clean install of the Nvidia drivers again and......
IT WORKED !!!!
multimon_config.sii files: viewtopic.php?p=17658#p17658
controls.sii edits: viewtopic.php?p=24744#p24744
TrackIR Driving Enhancements: viewtopic.php?p=46613#p46613
Extra Cameras: viewtopic.php?p=46034#p46034
controls.sii edits: viewtopic.php?p=24744#p24744
TrackIR Driving Enhancements: viewtopic.php?p=46613#p46613
Extra Cameras: viewtopic.php?p=46034#p46034
Re: [DX11] Help regarding Nvidia Profile Inspector (NPI)
@Pancreas
I agree with JHTrucker, as I can't find ANYTHING wrong with your settings either!
I agree with JHTrucker, as I can't find ANYTHING wrong with your settings either!
Re: [DX11] Help regarding Nvidia Profile Inspector (NPI)
I was just thinking, could it be a resolution problem? Because i have a NV Surround view of 4320x900. And if i play it on my 4k monitor 3840x2160 i can't remember if i have the same issue or not. Let me check that.
- Road Runner
- PPM
- Posts: 158
- Joined: December 15th, 2018, 1:10 pm
- Location: Stafford UK
Re: [DX11] Help regarding Nvidia Profile Inspector (NPI)
@BenganJ & JHTrucker
Perhaps I should have left out the Ultra Low Latency setting in repect of setting GSync and VSync together. As you are aware Graphics engines queue frames to be rendered by the GPU, the GPU renders them, and then they're displayed on your PC. With Ultra-Low Latency mode, frames are submitted into the render queue just before the GPU needs them. This is just in time frame scheduling and stops the cpu overloading the gpu. Where it becomes relevant is to note that monitoring of frame rates will diplay 3 fps less than the expected VSync setting and thus acts as a frame rate limiter.
The rationale in setting GSync and VSync relates to Frametime. Frametime denotes how long a single frame takes to render. Framerate is the totaled average of each frame’s render time within a one second period.
At 144Hz, a single frame takes 6.9ms to display (the number of which depends on the max refresh rate of the display), so if the framerate is 144 per second, then the average frametime of 144 FPS is 6.9ms per frame.
In reality, however, frametime from frame to frame varies, so just because an average framerate of 144 per second has an average frametime of 6.9ms per frame, doesn’t mean all 144 of those frames in each second amount to an exact 6.9ms per; one frame could render in 10ms, the next could render in 6ms, but at the end of each second, enough will hit the 6.9ms render target to average 144 FPS.
So what happens when just one of those 144 frames renders in, say, 6.8ms (146 FPS average) instead of 6.9ms (144 FPS average) at 144Hz? The affected frame becomes ready too early, and begins to scan itself into the current scanout cycle (the process that physically draws each frame, pixel by pixel, left to right, top to bottom on-screen) before the previous frame has a chance to fully display (ie tearing).
G-SYNC + V-SYNC Off allows these instances to occur, even within the G-SYNC range, whereas G-SYNC + V-SYNC On (with average framerates within the G-SYNC range) to time delivery of the affected frames to the start of the next scanout cycle, which lets the previous frame finish in the existing cycle, and thus prevents tearing in all instances.
You may disagree with this is analysis and conclusion, nonetheless I will contine to use the settings recommended in my earlier post - those that in practical use and operation are working so well! :D
Perhaps I should have left out the Ultra Low Latency setting in repect of setting GSync and VSync together. As you are aware Graphics engines queue frames to be rendered by the GPU, the GPU renders them, and then they're displayed on your PC. With Ultra-Low Latency mode, frames are submitted into the render queue just before the GPU needs them. This is just in time frame scheduling and stops the cpu overloading the gpu. Where it becomes relevant is to note that monitoring of frame rates will diplay 3 fps less than the expected VSync setting and thus acts as a frame rate limiter.
The rationale in setting GSync and VSync relates to Frametime. Frametime denotes how long a single frame takes to render. Framerate is the totaled average of each frame’s render time within a one second period.
At 144Hz, a single frame takes 6.9ms to display (the number of which depends on the max refresh rate of the display), so if the framerate is 144 per second, then the average frametime of 144 FPS is 6.9ms per frame.
In reality, however, frametime from frame to frame varies, so just because an average framerate of 144 per second has an average frametime of 6.9ms per frame, doesn’t mean all 144 of those frames in each second amount to an exact 6.9ms per; one frame could render in 10ms, the next could render in 6ms, but at the end of each second, enough will hit the 6.9ms render target to average 144 FPS.
So what happens when just one of those 144 frames renders in, say, 6.8ms (146 FPS average) instead of 6.9ms (144 FPS average) at 144Hz? The affected frame becomes ready too early, and begins to scan itself into the current scanout cycle (the process that physically draws each frame, pixel by pixel, left to right, top to bottom on-screen) before the previous frame has a chance to fully display (ie tearing).
G-SYNC + V-SYNC Off allows these instances to occur, even within the G-SYNC range, whereas G-SYNC + V-SYNC On (with average framerates within the G-SYNC range) to time delivery of the affected frames to the start of the next scanout cycle, which lets the previous frame finish in the existing cycle, and thus prevents tearing in all instances.
You may disagree with this is analysis and conclusion, nonetheless I will contine to use the settings recommended in my earlier post - those that in practical use and operation are working so well! :D
System: Windows 11
Processor: Intel Core i9-9900K @ 4.80GHz
Motherboard: Gigabyte Z390 Aorus Pro
Memory: 32GB DDR4 3200MHz Dual Channel
Graphics: GeForce RTX 2080 Ti
Drives: Samsung 970 EVO Polaris 1TB & 2TB M.2 2280 PCI-e 3.0 x4 NVMe
Processor: Intel Core i9-9900K @ 4.80GHz
Motherboard: Gigabyte Z390 Aorus Pro
Memory: 32GB DDR4 3200MHz Dual Channel
Graphics: GeForce RTX 2080 Ti
Drives: Samsung 970 EVO Polaris 1TB & 2TB M.2 2280 PCI-e 3.0 x4 NVMe
Re: [DX11] Help regarding Nvidia Profile Inspector (NPI)
@Road Runner
But still, why are you striving for highest possible frame rate, thereby loading CPU and
GPU at the most? Frame Rate Limiting will make it much easier on those resources to
e.g. being able to be used by other applications.
But still, why are you striving for highest possible frame rate, thereby loading CPU and
GPU at the most? Frame Rate Limiting will make it much easier on those resources to
e.g. being able to be used by other applications.
- Road Runner
- PPM
- Posts: 158
- Joined: December 15th, 2018, 1:10 pm
- Location: Stafford UK
Re: [DX11] Help regarding Nvidia Profile Inspector (NPI)
I do not feel at all sorry for both my CPU and GPU. In any case I have resticted fps by capping at the refresh rate. By 33% as a rough calculation. Also most importantly I am preventing potential tearing. In running ets2 both my CPU and GPU are having a holiday! :D
I remain unrepentant!
I remain unrepentant!
System: Windows 11
Processor: Intel Core i9-9900K @ 4.80GHz
Motherboard: Gigabyte Z390 Aorus Pro
Memory: 32GB DDR4 3200MHz Dual Channel
Graphics: GeForce RTX 2080 Ti
Drives: Samsung 970 EVO Polaris 1TB & 2TB M.2 2280 PCI-e 3.0 x4 NVMe
Processor: Intel Core i9-9900K @ 4.80GHz
Motherboard: Gigabyte Z390 Aorus Pro
Memory: 32GB DDR4 3200MHz Dual Channel
Graphics: GeForce RTX 2080 Ti
Drives: Samsung 970 EVO Polaris 1TB & 2TB M.2 2280 PCI-e 3.0 x4 NVMe
Re: [DX11] Help regarding Nvidia Profile Inspector (NPI)
On the other hand you told us you have one comp just for gaming and another for other stuff,
the laptop! So, you're not as many of us, dependent on running BOTH games and other stuff
on the same comp!
Re: [DX11] Help regarding Nvidia Profile Inspector (NPI)
again a new screenshot with my Nvidia freestyle I use.
Ps I can't use antialiasing fix because my graphics card is not enough powerful and I avoid to use it sorry.
If you want it here's again
Color
Tint color 0%
Tint intensity 4%
Temperature 12
Vibrance 100
Brightness/Contrast
Nothing to change here
This made the game more colourful and limit the fps lose, good for lower graphics card pc.
Ps I can't use antialiasing fix because my graphics card is not enough powerful and I avoid to use it sorry.
If you want it here's again
Color
Tint color 0%
Tint intensity 4%
Temperature 12
Vibrance 100
Brightness/Contrast
Nothing to change here
This made the game more colourful and limit the fps lose, good for lower graphics card pc.
My specs
====================================
Motherboard: MSI B450 GAMING PLUS MAX
Memory: Kingston Hyper Fury X 3200 MHz
Graphics card: Palit Geforce RTX 3070 Gamerock OC
Processor: AMD Ryzen 5 3600
Storage: SSD Samsung 860 QVO
====================================
Motherboard: MSI B450 GAMING PLUS MAX
Memory: Kingston Hyper Fury X 3200 MHz
Graphics card: Palit Geforce RTX 3070 Gamerock OC
Processor: AMD Ryzen 5 3600
Storage: SSD Samsung 860 QVO
Re: [DX11] Help regarding Nvidia Profile Inspector (NPI)
@Ticreut29
Thanks, always nice with alternatives to choose from!
Thanks, always nice with alternatives to choose from!