Use DXVK instead of DXVK Native

[szymonj99]

Describe the solution you'd like
In CMakeLists.txt, I think it could be possible to now use https://github.com/doitsujin/dxvk as opposed to https://github.com/Joshua-Ashton/dxvk-native, seeing how DXVK Native has now been included in the former as of this comment.
That would result in being able to now get updates as opposed to an archived repository from November 2022.

Let me know if I am incorrect about this 👍

[q4a]

Main question: what is goal of changing it? we almost don't have problems with it, I'm fine with current perfomance.

But yes, we can switch to original DXVK, but there is few things in DXVK:

• I don't like that DXVK depending on Vulkan 1.3, which is not widely spread. DXVK Native require Vulkan 1.1.
• I didn't test how original DXVK works on Linux - does it have better perfomance?
• I know only one DXVK Native issue, which related to Storm engine: if you use Debug build you wii not see mini-screens in savegames. Release build works fine.

I currenty don't have time to test new DXVK. You can try to replace DXVK Native and compare. If it will works better - we can replace it.

[szymonj99]

Keep in mind, this suggestion is a result of procrastination and not working on my university assignments 😄 .

what is goal of changing it?

I was thinking that the main goal would be to be able to receive updates to DXVK.

I don't like that DXVK depending on Vulkan 1.3, which is not widely spread. DXVK Native require Vulkan 1.1.

This I had no idea about. I can see why sticking with what we have might be a better alternative.

does it have better perfomance?

I have zero clue to be honest 😄

If I had more time and less assignments, I would like to dabble with this. But until then, it's just food for thought. 💯