It's happened, the D9VK and DXVK projects have officially merged. This means DXVK is now the all-encompassing project to translate D3D 9/10/11 to Vulkan for Wine.
Only a few hours ago the pull request was accepted and so they're now one awesome project, meaning D9VK will now be developed directly in the DXVK project. This does make a lot of things easier and simpler overall, since you only need to keep track of one project and they will now update together.
From the actual pull request, Ashton noted these features still needed to be worked on:
- Fixed function bumpmapping
- Fixed function premodulation
- Software cursor (hardware cursor is currently implemented)
- ComposeRects (from D3D9Ex, however I have no test case for this)
- Custom Border Color (needs ext)
- Depth Bias Fixes (needs ext)
Apart from that, the usual bug fixing.
Congratulations to D9VK developer Joshua Ashton and DXVK developer Philip Rebohle, together they've certainly helped pushed Linux gaming into new territory.
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
Quoting: rkfgDXVK has a "fundamental flaw" and that is the language it's written in. Wine doesn't accept C++ code, unfortunately.
Now I wondered what they're using.
Pure C?!?
Last edited by Eike on 16 December 2019 at 1:08 pm UTC
0 Likes
I'm guessing that means that the days of
PROTON_USE_D9VK=1 %command% are rapidly drawing to a close, yeah? There is a Santa-bot 3000!
1 Likes, Who?
Quoting: GuestNo it's not, they have their own Discord. Don't take comments made out of frustration, as actual plans.Quoting: Liam DaweQuoting: Sir_DiealotIsn't DXVK that project that just went into maintenance mode because it's not feasible to develop it further?No, that was other sites making a mountain out of a little GitHub comment rant. Don't read into it.
Isn't GitHub the only channel the DXVK dev uses to communicate? In those little comment rants he clearly stated that after the merge of D9VK his project is going maintenance mode, because it's a "fragile, unreliable and frustrating maintenance nightmare". AFAIK he did not retract that anywhere. Do you know something we don't know or what?
1 Likes, Who?
Finally!
0 Likes
Quoting: EikeYes, Wine is written in pure C.Quoting: rkfgDXVK has a "fundamental flaw" and that is the language it's written in. Wine doesn't accept C++ code, unfortunately.
Now I wondered what they're using.
Pure C?!?
1 Likes, Who?
Quoting: rkfgYes, Wine is written in pure C.
No wonder it's a maintenance nightmare. ;)
Last edited by Eike on 16 December 2019 at 2:01 pm UTC
3 Likes, Who?
Quoting: GuestSaid nothing about official, I simply answered your question on GitHub not being the only place the DXVK people communicate.Quoting: Liam DaweQuoting: GuestNo it's not, they have their own Discord. Don't take comments made out of frustration, as actual plans.Quoting: Liam DaweQuoting: Sir_DiealotIsn't DXVK that project that just went into maintenance mode because it's not feasible to develop it further?No, that was other sites making a mountain out of a little GitHub comment rant. Don't read into it.
Isn't GitHub the only channel the DXVK dev uses to communicate? In those little comment rants he clearly stated that after the merge of D9VK his project is going maintenance mode, because it's a "fragile, unreliable and frustrating maintenance nightmare". AFAIK he did not retract that anywhere. Do you know something we don't know or what?
TIL Discord is official, GitHub is not.
0 Likes
Quoting: EikeErrrr, wasn't that quote about DXVK itself and not Wine? I'd like to read the whole story.Quoting: rkfgYes, Wine is written in pure C.
No wonder it's a maintenance nightmare. ;)
1 Likes, Who?
Quoting: rkfgGuess that is one way to make sure a project never has too many people working on it.Quoting: EikeYes, Wine is written in pure C.Quoting: rkfgDXVK has a "fundamental flaw" and that is the language it's written in. Wine doesn't accept C++ code, unfortunately.
Now I wondered what they're using.
Pure C?!?
What a waste of potential.
Pure C is fine for smaller projects or concise little libraries.
But big ones purely in C is just nightmare fuel. Go take a look at the FFmpeg sources if you don't believe me.
Alright, merge Wine into DXVK, then ;)
C++ isn't picky about having some pure C code within.
Last edited by TheSHEEEP on 16 December 2019 at 1:45 pm UTC
6 Likes, Who?
Quoting: Liam DaweQuoting: Sir_DiealotIsn't DXVK that project that just went into maintenance mode because it's not feasible to develop it further?No, that was other sites making a mountain out of a little GitHub comment rant. Don't read into it.
@Liam: Might be worth doing an article about it, I was like @Sir_Dialot, thinking DXVK was slowly dying in place of another project.. Although I have been reading mainly Linux news every day.
4 Likes, Who?
Patreon
PayPal
See more from me