Degraded performance in WarThunder after latest nvidia driver update

FPS is ok but graphics is jerky. Is it please possible to fix it ?

With that much information you only have the chance to report this upstream.

Hi
Can you provide some hardware info…


inxi -Gxxz

Hi,

# inxi -Gxxz
Graphics:  Device-1: Intel 3rd Gen Core processor Graphics vendor: Micro-Star MSI driver: i915
           v: kernel bus-ID: 00:02.0 chip-ID: 
           Device-2: NVIDIA GK107M [GeForce GTX 660M] vendor: Micro-Star MSI driver: nvidia
           v: 470.161.03 bus-ID: 01:00.0 chip-ID: 
           Display: x11 server: X.Org 1.20.3 driver: loaded: intel,nvidia unloaded: modesetting
           resolution: 1920x1080~60Hz s-dpi: 96
           OpenGL: renderer: NVIDIA GeForce GTX 660M/PCIe/SSE2 v: 4.6.0 NVIDIA 470.161.03
           direct render: Yes
#


Hi
So it’s an older optimus setup, can you show the output from;


xrandr --listproviders

I’m assuming suse-prime, bbswitch (and it’s kmp?).

Hi,

maketopsite@maketopsite:~> xrandr --listprovidersProviders: number : 2
Provider 0: id: 0x2e8; cap: 0x1 (Source Output); crtcs: 0; outputs: 0; associated providers: 1; name: NVIDIA-0
Provider 1: id: 0x48; cap: 0xb (Source Output, Sink Output, Sink Offload); crtcs: 4; outputs: 5; associated providers: 1; name: Intel
    output LVDS1
    output DP1
    output HDMI1
    output VGA1
    output VIRTUAL1

# zypper se -i nvidiaS  | Name                      | Summary                                                               | Type
---+---------------------------+-----------------------------------------------------------------------+-------
i  | kernel-firmware-nvidia    | Kernel firmware files for Nvidia Tegra and graphics drivers           | package
i+ | nvidia-computeG05         | NVIDIA driver for computing with GPGPU                                | package
i  | nvidia-computeG05-32bit   | 32bit NVIDIA driver for computing with GPGPU                          | package
i+ | nvidia-gfxG05-kmp-default | NVIDIA graphics driver kernel module for GeForce 600 series and newer | package
i+ | nvidia-glG05              | NVIDIA OpenGL libraries for OpenGL acceleration                       | package
i  | nvidia-glG05-32bit        | 32bit NVIDIA OpenGL libraries for OpenGL acceleration                 | package
i+ | x11-video-nvidiaG05       | NVIDIA graphics driver for GeForce 600 series and newer               | package
i  | x11-video-nvidiaG05-32bit | 32bit NVIDIA graphics driver for GeForce 600 series and newer         | package
# 
# zypper se -i bbswitch
S  | Name                 | Summary                      | Type
---+----------------------+------------------------------+-------
i+ | bbswitch             | Bumblebee ACPI kernel module | package
i+ | bbswitch-kmp-default | Bumblebee ACPI kernel module | package
# 
# prime-select  get-current
Driver configured: nvidia
NVIDIA modules are loaded
# 



I’ve been reading in several places that the latest Nvidia drivers are bugged:
Nvidia drm errors on nvidia driver 520.56.06
Nvidia_drv sometime segfaultsIn Fedora 37 nvidia-driver 520.56.06 is buged and crash Apex legend [drm:nv_drm_fence_context_create_ioctl [nvidia_drm]]

I realize this is not the same driver version, but something may have hit upstream to the 05 as the 06 ver got hit. Check your journal logs for nvidia_drm errors, and if they’re there, you’re likely encountering the same issue. So far the only solution I have found is to roll back your drivers, but that may not be a solution for everyone as they can’t obtain older drivers.

Hi
That’s probably why that version was skipped and straight to the 523.53 version… The segfault link is not related (2019?)

I’ve not see issues here, but only a casual minecraft player here, likewise not an optimus system, just a desktop with a T400 and P4 (manual install of 523.53) and the OP is on a Legacy system…

No nvidia_drm errors in journal logs.

There is another new release yesterday Nov.28, version 525.60.11
I installed it a while ago. Something wrong after the installer is finish, it boot to text like init 3, but after doing the mkinitrd and reboot it reach the gui.
Second time it happened here the other one was with 515.86.01.

Hi
Not here upgraded an hour or so ago… (I’m on Tumbleweed)…


nvidia-smi 

Tue Nov 29 11:41:00 2022       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 525.60.11    Driver Version: 525.60.11    CUDA Version: 12.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA T400         Off  | 00000000:02:00.0  On |                  N/A |
| 38%   37C    P8    N/A /  31W |    590MiB /  2048MiB |      2%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   1  Tesla P4            Off  | 00000000:03:00.0 Off |                    0 |
| N/A   31C    P8     6W /  75W |     46MiB /  7680MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      2039      G   /usr/bin/Xorg.bin                 255MiB |
|    0   N/A  N/A      2344      G   /usr/bin/gnome-shell              107MiB |
|    0   N/A  N/A      6920    C+G   ...573730349847292684,131072       77MiB |
|    0   N/A  N/A      8103      G   ...veSuggestionsOnlyOnDemand       74MiB |
|    1   N/A  N/A      2039      G   /usr/bin/Xorg.bin                  46MiB |
+-----------------------------------------------------------------------------+

Solved probably after regenerating of shader cache (done by playing WT).