LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   Annoyances with nvidia 390.25 / tearing issues (https://www.linuxquestions.org/questions/linux-software-2/annoyances-with-nvidia-390-25-tearing-issues-4175622917/)

coralfang 02-02-2018 02:14 AM

Annoyances with nvidia 390.25 / tearing issues
 
Nvidia driver has ALWAYS suffered from tearing, it's actually quite bad considering how long this has been present over the years.

I've been able to eliminate this by adding;
/etc/X11/xorg.conf.d/10-nvidia.conf
Code:

Section "Screen"
    Identifier    "Screen0"
    Device        "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
  Option        "metamodes" "nvidia-auto-select +0+0 { ForceFullCompositionPipeline = On }"
  SubSection    "Display"
      Depth      24
  EndSubSection
EndSection

I believe that forcing the full composition pipeline polls the GPU to forcibly update the entire screen where a redraw isn't needed, so that tearing becomes eliminated.

This has worked without any noticable performance loss in frames per second for at least a year or two. However, since upgrading to 390.25, enabling theForceFullCompositionPipeline setting produces stuttering in every game i have tried. Despite the fps being vsynced at 60, there is still stuttering.

Disabling the setting brings back the horrific tearing present across both desktop and fullscreen vsynced applications.

Does anyone know if this is a regression in nvidias driver, or whether there are some other setting i can fiddle about with. I would really just like to look at my screen without the 24/7 tearing.

Brains 02-02-2018 01:01 PM

Code:

for at least a year or two. However, since upgrading to 390.25
If you were happy with the performance of the driver that was designed for your card 2 years ago, you should use that driver. Unless you have purchased the most recent Nvidia device, you will not get anything out of the latest driver. The latest driver may support your graphics device, it may not support your device.

Nvidia is a corporation with investors, investors need to see a return on their investment, and it has to be more than what the bank pays or they pull their money out. As such, they cannot make a rock solid product that will only sell once, they need to sell, sell, sell in order to stay afloat, just like any other large corporation.

The driver designed for your graphics device is the best driver for your graphics device. There is a driver search tool at Nvidia web site, if your graphics device is two years old, according to the search, you are likely to find you are using the wrong driver. Rarely if never, does a newer driver version give your graphics device features that were not built into your graphics device.

I mean seriously, if you were happy with performance of a past driver, why do you stab yourself like this?

RadicalDreamer 02-03-2018 03:21 AM

Which game?

Maybe try just "Force Composition Pipeline" instead of Full Force Composition Pipeline.
Code:

ForceCompositionPipeline=On
Also vsync creates input lag.

coralfang 02-03-2018 03:43 AM

Quote:

Originally Posted by Brains (Post 5814903)
Code:

for at least a year or two. However, since upgrading to 390.25
If you were happy with the performance of the driver that was designed for your card 2 years ago, you should use that driver. Unless you have purchased the most recent Nvidia device, you will not get anything out of the latest driver. The latest driver may support your graphics device, it may not support your device.

Nvidia is a corporation with investors, investors need to see a return on their investment, and it has to be more than what the bank pays or they pull their money out. As such, they cannot make a rock solid product that will only sell once, they need to sell, sell, sell in order to stay afloat, just like any other large corporation.

The driver designed for your graphics device is the best driver for your graphics device. There is a driver search tool at Nvidia web site, if your graphics device is two years old, according to the search, you are likely to find you are using the wrong driver. Rarely if never, does a newer driver version give your graphics device features that were not built into your graphics device.

I mean seriously, if you were happy with performance of a past driver, why do you stab yourself like this?

I have a GTX 1060 which is only a few months old. But this setting worked fine on a GTX650ti previously. Only in 390.25 does this happen.
The card is recent enough to be using any new release of the driver, and some games on steam typically require the latest driver at release.

Brains 02-03-2018 03:46 AM

Post #2 has a quote from Post #1 that says you are trying to hide behind a rock.

coralfang 02-03-2018 10:03 AM

Quote:

Originally Posted by Brains (Post 5815110)
Post #2 has a quote from Post #1 that says you are trying to hide behind a rock.

I think you are misunderstanding. I posted in software, because i get this issue with all Nvidia cards for the past 2 years or more. If i use nouveau, the tearing is not present, but this opensource driver just isn't good enough for GPU intensive games.

The tearing issue exists across all GPU's as far as i know, and the only way to previously fix it was to enable ForceFullCompositionPipeline. However, since 390.25 driver, enabling this mode causing what might be sync issues, despite vsyanc being turned on or off.

It's either a choice between visible shearing/tearing, or noticable stuttering. I'm really wondering if anyone else is having this issue, and knows what other settings i can try to fiddle about with.

RadicalDreamer 02-03-2018 12:24 PM

Since the stuttering started in the new driver you should go tell NVIDIA: https://devtalk.nvidia.com/default/board/98/


All times are GMT -5. The time now is 05:08 PM.