#364 Regarding stuttering / performance issues

Geschlossen
vor 1 Jahr geöffnet von Alex72 · 5 Kommentare
Alex72 kommentierte vor 1 Jahr

According to the changelog of DXVK 2.0 published yesterday, it now supports eager compilation of shaders (shaders now are compiled at a load time rather than at a runtime like it was in previous versions).

Potentially this might help reduce stuttering and FPS drops in our game of question.

As of now this feature is only supported in NVidia drivers version 520.56.06 or later, so every NVidia user is welcome to try and test this.

https://github.com/doitsujin/dxvk/releases/tag/v2.0

According to the changelog of DXVK 2.0 published yesterday, it now supports eager compilation of shaders (shaders now are compiled at a load time rather than at a runtime like it was in previous versions). Potentially this might help reduce stuttering and FPS drops in our game of question. As of now this feature is only supported in NVidia drivers version 520.56.06 or later, so every NVidia user is welcome to try and test this. https://github.com/doitsujin/dxvk/releases/tag/v2.0
Cha14ka kommentierte vor 1 Jahr

Tried DXVK 2.0 on AMD, it consumes much more VRAM than with DXVK 1.10.3

Tried DXVK 2.0 on AMD, it consumes much more VRAM than with DXVK 1.10.3
Cha14ka kommentierte vor 1 Jahr

Played a little longer, it's really shaders took up all vram when compiled at startup, if you play a little longer on the old DXVK, it begins to take about the same amount

Played a little longer, it's really shaders took up all vram when compiled at startup, if you play a little longer on the old DXVK, it begins to take about the same amount
rodwood_tide kommentierte vor 1 Jahr

I just saw this thread today.

I have an old NVIDIA GPU (750 Ti) but is still supported by newer drives. I've been using DXVK 2.0 since it came out and stuttering has been reduced most notable in the new region. It is much more playable than before. I am also using async right now but I can't tell if it is better.

edit: My computer has crashed twice with async. It might be a hardware issue. I'll be going back to no async and see if it crashes somehow.

edit 2: My computer has never crashed since. Maybe async was really causing the problem for me.

I just saw this thread today. I have an old NVIDIA GPU (750 Ti) but is still supported by newer drives. I've been using DXVK 2.0 since it came out and stuttering has been reduced most notable in the new region. It is much more playable than before. I am also using async right now but I can't tell if it is better. edit: My computer has crashed twice with async. It might be a hardware issue. I'll be going back to no async and see if it crashes somehow. edit 2: My computer has never crashed since. Maybe async was really causing the problem for me.
Ph42oN kommentierte vor 1 Jahr

Looks like DXVK 2.0 can help on AMD too. I recommend removing old shader cache, even if using AMD. On my laptop with ryzen 2500u+RX 560x, it performed the same as 1.10.3, but then i deleted old shader cache and it reduced stuttering. Using async with both versions. But on my much faster desktop i dont see any performance change.

Looks like DXVK 2.0 can help on AMD too. I recommend removing old shader cache, even if using AMD. On my laptop with ryzen 2500u+RX 560x, it performed the same as 1.10.3, but then i deleted old shader cache and it reduced stuttering. Using async with both versions. But on my much faster desktop i dont see any performance change.
Krock kommentierte vor 1 Jahr
Besitzer

I do not see any need to document this feature.

At least on my AMD GPU there were no noticeable performance differences between DXVK 2.0 and 1.10.3. Users can use either version and get acceptable performance (depending on their hardware) which usually suffices.

I do not see any need to document this feature. At least on my AMD GPU there were no noticeable performance differences between DXVK 2.0 and 1.10.3. Users can use either version and get acceptable performance (depending on their hardware) which usually suffices.
Krock hat vor 1 Jahr geschlossen
Anmelden, um an der Diskussion teilzunehmen.
Kein Meilenstein
Niemand zuständig
5 Beteiligte
Laden…
Abbrechen
Speichern
Hier gibt es bis jetzt noch keinen Inhalt.