You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'll still accept caches. And I wonder, if the cache was no longer needed then why wouldn't DXVK just get rid of it?
I think it's still needed in some of the bigger games, such as Apex so I will accept them, because why not.
Maybe it'll still be useful to someone.
If you don't want to develop your tool anymore, it's absolutely fine.
So DXVK got a new release
And it compiles the shaders now when starting the game and not on-draw.
THIS APPLIES ONLY FOR COMPATIBLE DRIVERS
So since the caches won't be generated while playing a game instead before loading the game, we probably won't need to merge any of them any longer.
(DXVK-Native got up streamed into this as well, not sure if the pre-playing generation applies for this as well, but probably yes)
What do you think?
Additional point to think of:
Custom maps in game may produce shader caches that can't be compiled previously (e.g. CSGO)
As I'm still developing the DXVKoTool and not sure if it's worth to maintain now.
The text was updated successfully, but these errors were encountered: