Ok will do. Wanted to record a longer video of the gameplay in Starfield with the beta driver and then will post there. I can surely tell that there is an improvement since the heavy lagging I had on the 525 driver is gone and its well playable with 30 fps. Yesterday I have played a dungeon at 45 fps in QHD@Ultra preset that was really good. On the old 525 driver I could experience a cpu bound scenario very well, having the fps dipping even more when I played with a 2k screen recording on. On the new beta driver the screen recording does not affect the fps at all.
Last idea I have is maybe kernel, I am on 6.2, if you are on Arch Linux, you could give it a quick test. I am on a maintained distro this is the almost actual packagelist: https://os.tuxedocomputers.com/TUXEDO-OS-2-202309251410.packagelist
System is a Ryzen 9 6900HX, 32 GB RAM and externally watercooled.
Prolly way easier to test all this on Arch, on this Ubuntu it costed me 3 hours to manually install the beta driver as well as several chroots. :)
Thanks! Just to be clear, as I wrote here, I do see somewhat improved performance myself on 535.43.10 compared to 530.x, particularly in terms of input lag. It is noticeable, yes, and it does make the game quite more playable. It’s just nowhere near the Windows performance, including the buttery smoothness of the input there.
I’ve been thinking about the kernel too. My knowledge in the graphics area is pretty humble, but my understanding is that, except in very specific cases, the kernel isn’t very likely to affect the performance with the Nvidia proprietary blobs (the open source AMD driver is obviously a totally different kettle of fish). For the record, I’m using the CachyOS modified kernel on Arch Linux, 6.5.5-2-cachyos (building it myself from AUR). Might try a different kernel if I find the time.
At best, on 13600KF and 3070 Ti I’m netting around 28-30 FPS (the same machine on Windows churns out 50 to 75 FPS depending on the environment)
Exactly what I’m seeing too: at least 50% lower performance compared to Windows.
With driver version 535.43.10 and the VKD3D commit linked below, all prior crashing has been fixed. The framerate is a bit higher than that of patched driver version 525, but it’s not performant by any means. On high settings with FSR2 at 50% resolution, open-world planet locations run at a solid 20-30fps. Indoor areas can jump as high as 70fps, which was impossible prior to this version.
The game crashes when loading the game or starting a new game. It happens exactly that with the previous drivers that failed, only .10 loads the game although it runs at low fps.
System specs:
Información del ordenador:
Fabricante: ASUSTeK COMPUTER INC.
Modelo: ROG STRIX X570-E GAMING
Información del procesador:
Fabricante de la CPU: AuthenticAMD
Marca de la CPU: AMD Ryzen 7 5800X 8-Core Processor
Familia de la CPU: 0x19
Modelo de la CPU: 0x21
Stepping de la CPU: 0x0
Tipo de CPU: 0x0
Velocidad: 4746 MHz
16 procesadores lógicos
8 procesadores físicos
Versión del sistema operativo:
"Manjaro Linux" (64 bits)
Nombre de kernel: Linux
Versión de kernel: 6.5.5-1-MANJARO
Editor de X Server: The X.Org Foundation
Versión de X Server: 12101008
Gestor X Window: KWin
Versión del runtime de Steam: steam-runtime_0.20230801.56012
Tarjeta de vídeo:
Controlador: NVIDIA Corporation NVIDIA GeForce RTX 3070/PCIe/SSE2
Versión del controlador: 4.6.0 NVIDIA 535.43.11
Versión de OpenGL: 4.6
Profundidad de color del escritorio: 24 bits por píxel
Frecuencia de actualización del monitor: 164 Hz
Identificador del fabricante: 0x10de
Identificador del dispositivo: 0x2488
Revisión no detectada
Número de monitores: 1
Número de tarjetas de vídeo lógicas: 1
Resolución de pantalla principal: 2560 x 1440
Resolución de escritorio: 2560 x 1440
Tamaño de la pantalla principal: 27.56" x 15.35" (31.54" diag), 70.0cm x 39.0cm (80.1cm diag)
Bus principal: PCI Express 16x
Memoria VRAM principal: 8192 MB
Modos MSAA compatibles: 2x 4x 8x 16x
Tarjeta de sonido:
Dispositivo de sonido: Nvidia GPU 9e HDMI/DP
Memoria:
RAM: 32002 MB
Latest nvidia vulkan drivers 535.43.11 and proton bleeding edge
Confirm this once again. Hangs immediately when I try to load a save or start a new game. (535.43.11, RTX 3070 Ti, bleeding edge everything else). Was working, albeit with horrible performance, with 535.43.10 and the same everything.
With driver version 535.43.11 and the VKD3D commit linked below, the game is now fully playable. No more crashing and the framerate indoors and outdoors is considerably higher, with indoor areas exceeding 90fps and outdoor areas now balancing between a very stable 50-60+fps with the same graphics configuration as my previous post. Med-high settings and FSR2 @ 50% render scale at a resolution of 2560x1440. The only issue is some new graphical artifacting with some textures, but this has an almost negligible impact on the overall experience.
The rocks on the horizon in the attached image have a tendency to flicker in and out as the player moves the camera around.
For those interested in testing this, ensure that you are on kernel version 5.15.121+, 6.1.40+ or 6.4.5+ as these have patches in them that affect Starfield.
Just compiled it from scratch and I don’t see any difference regarding performance but it can be my old GPU as it’s utilized at 98%. The game is starting fine.
535.43.10 and 535.43.11 drivers (built and installed via Frogging-Family set of scripts)
RTX 3070 Ti
Kernel 6.5.5-1 (Manjaro)
bleeding-edge vkd3d and nv-enable-dgcc branch build (were forcefully installed to game’s prefix with override to native, with prefix removal before switching the versions – so no chance of a mix-up)
Game version of 1.7.33
Numerous different versions of Proton, ranging from stable down to bleeding edge builds
The situation is the same: game runs on 535.43.10, save for performance issues, and hangs immediately when trying to load a save or start a new game on 535.43.11.
On 535.43.10 the only difference between bleeding edge vkd3d and dlls built from nv-enable-dgcc is that the latter performs even worse (FPS in single digits), whereas with build straight out of master branch I’m seeing the same 28-30 FPS in New Atlantis and 40 to 50 FPS elsewhere (interiors, barren planets with little to none vegetation and small details).
Can somebody with access both to Turing and Ampere cards cross-check the behavior?
This is true. I figured it was worth a mention just to ensure that anybody who stumbles into this thread has their kernel sufficiently up to date to avoid any additional undefined driver behavior.
Have you had any success with the 535.43.11 driver?
