Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with shader pre caching on every game #5485

Open
AdamTaylor2867 opened this issue Jan 6, 2022 · 3 comments
Open

Issues with shader pre caching on every game #5485

AdamTaylor2867 opened this issue Jan 6, 2022 · 3 comments

Comments

@AdamTaylor2867
Copy link

So i've been having an issue with the shader pre caching on steam on basically every single game on my library.

Examples of this is on days gone, i would pre load the shaders, load in the game and get huge stutters, the stutters would go down and then when it would move to a new scene it would begin to stutter massively, and this would occur throughout my entire time playing, to the point it becomes unplayable, it would load in the game, and lag so badly for a good minute, then as soon as i'd start playing and move say, 50 meters away from the area it would start again stuttering and freezing so badly, as if I loaded the game for the first time without using pre caching. Checking the cache it says it has loaded pre shaders cache.

Going onto the /shadercache/1259420/nvidiav1/GLCache// it shows the shader cache files to have around 300 mbs, and then in the
shadercache/1259420/swarm it would show the swarm holding 500mbs.

(I have made sure that the shader cache has all finished installing also)

An example of this happening on other games is resident evil 2 remake, i'd load in and it'd lag alot, and then stop, when i'd move to other areas or rooms it would freeze for a second then load everything in. Same with dying light but much less severe.

I am currently using Pop os 21.10, but have had the same issue on Manjaro KDE and also Ubuntu 21.10
I have propriteary recent drivers that are 470.86 and I'm on high power mode.

I have used various different proton versions including GE launch options such as "DXVK_ASYNC=1 %command%" to see if that were to fix the problem, I've tried alot of differen't thing and spoken to alot of different people for soloutions which aren't all here since i've done alot of different things, I would really appreciate any support on this because it seems to all be working but then doesn't actually appear to properly work during gameplay.
Sorry if any parts are confusing, thank you for reading
Screenshot from 2022-01-06 23-20-22
Screenshot from 2022-01-06 23-20-45
.

@SeraphisCain
Copy link

Just want to chime in and say this is happening to me as well. Also on Pop_OS. With Ys IX and now Monster Hunter Rise, I'll load into the game and there will be massive shader cache compiling-esque lag/stutter while I move around or move the camera until everything in the current area is loaded, then it'll stop. But once I move to a new area, it starts again. It's very frustrating and I've tried everything I can think of to fix it to no avail.

@ghost
Copy link

ghost commented Jan 21, 2022

games that use directx11 need to compile a lot of shader, it's normal, now games that use directx12 are much faster and have less problems with compiling shader, too bad most games still use directx11, you can use DXVK_ASYNC=1, but this command doesn't work in all games, Deus Ex: Human Revolution doesn't work, I already tried.

I also tested devil may cry 4 on my notebook (ryzen 5500U, vega 7), and even though it is an inferior hardware to my desktop (ryzen 1600x rtx 2060), it ran better than my desktop, with few lags,
do not know if you know but, the AMD driver has support for the Steam compiler (ACO) that greatly improves the performance of games.

you can try some things to improve a little this lag, for example, exchange the kernel for one that has the fsync patch, use gamemoderun.

@kisak-valve
Copy link
Member

DXVK_ASYNC is not supported by Proton or upstream DXVK. It will cause hard to diagnose rendering issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants