Wine Vulkan Preps For v1.1 Support With Licensing Issues Resolved

[Snaipersky]

Maybe you should get off your high horse. If you can do better than the guy developing winevulkan, or me developing DXVK, go ahead, make it better, but stop bitching around on the forums if all you have to show is a big mouth.

You sir, are shaping up to be a mini Torvalds. Sharp mind and tongue. If you wouldn't mind my asking, what specifically in the transition to Vulkan 1.1 is beneficial to DXVK?

[sdack]

Maybe you should get off your high horse. If you can do better than the guy developing winevulkan, or me developing DXVK, go ahead, make it better, but stop bitching around on the forums if all you have to show is a big mouth.

Dude, you can cry a river all you want, but it's not my attitude that's lacking here. Shut your mouth and keep coding, or be man enough to admit the performance of WINE is lacking back to front. Until then are just you the bitch who is unable to see the problems we have. Get your shit together.

[sdack]

You sir, are shaping up to be a mini Torvalds. Sharp mind and tongue.

No. Torvalds would have written DXVK in C using winegcc and made it a part of WINE from the start and not have written it in C++ and mingw. Nobody needs a DLL on Windows to translate DirectX into Vulkan when you have DirectX.

Now the code first need to be rewritten in C before it can become a part of WINE and none of the divas like this idiot VikingGe here is going to do it of course. He'll be too busy basking in the 3 months of glory he's been mentioned on Phoronix - if he actually is the author. He thinks of others being on a high horse, but then writes C++ code with lambdas while everyone else is writing it in plain C. That's only funny.

[VikingGe]

If you wouldn't mind my asking, what specifically in the transition to Vulkan 1.1 is beneficial to DXVK?

It's not so much about Vulkan 1.1 but some of the extensions that wine doesn't currently support, such as VK_EXT_vertex_attribute_divisor which is required to implement D3D11 input fetch rates properly. Wine has been limited to Vulkan 1.0.51 and thus doesn't support any of the new extensions that have been added since then.

Transitioning to 1.1 would be nice to reduce the number of extensions that I have to use and use core functionality instead, but it's not strictly required.

You sir, are shaping up to be a mini Torvalds

This guy is shitting on not one but two projects, without having contributed to either of them and nothing do back himself up, but acting like he knows it all. Can't be arsed to put a polite mask on.

or be man enough to admit the performance of WINE is lacking back to front

So, if you're so confident about winevulkan having a substantial impact on DXVK performance, where are your numbers to prove it?

Why aren't you ranting about wine's implementation of synchronization primitives instead which actually kills performance in certain games?

Nobody needs a DLL on Windows to translate DirectX into Vulkan when you have DirectX.

Nobody is forcing you to use it.

[sdack]

So, if you're so confident about winevulkan having a substantial impact on DXVK performance, where are your numbers to prove it?

Why aren't you ranting about wine's implementation of synchronization primitives instead which actually kills performance in certain games?

You need numbers first? Seriously? It's obvious nonsense to implement DXVK as a Windows DLL instead of a WINE DLL. You really don't get this? That's so sad.

To point to WINE as a defense when somebody points out a flaw in your code design just shows how petty you are. Nothing great about you after all. Just another solo artist, a one-trick-pony.

Nobody is forcing you to use it.

*lol* Let's start with the question of who is using it under Windows. Maybe then perhaps we can ask why they would feel forced to use it, but you're definitely an idiot when this is your answer.

[aksdb]

You need numbers first? Seriously? It's obvious nonsense to implement DXVK as a Windows DLL instead of a WINE DLL. You really don't get this? That's so sad.

If you pay someone to do work, you can enforce policies and rules all you want. As long as you don't put VikingGe under contract, just let him do what he does, the way he likes to do it. Nobody works on anything in his free time if he doesn't get anything out of it. I wouldn't use C either, simply because I would have close to zero fun in doing so.

So if you think you can do better: GO AHEAD! Otherwise don't tell other people how to do their own projects.

@VikingGe: thanks for your work. DXVK is really a big step forward and makes me pretty hopeful that I can (finally) ditch the dual boot Windows much sooner than I feared.

[notaz]

You need numbers first? Seriously? It's obvious nonsense to implement DXVK as a Windows DLL instead of a WINE DLL. You really don't get this? That's so sad.

How is this obvious for an API designed to reduce number or calls? The cycles wasted in occasional calls is unlikely to have measurable perf impact, so please enlighten us with some proof with some testcase at least. Talk is cheap, show us the numbers.

[sdack]

Otherwise don't tell other people how to do their own projects.

Well, that's the thing, isn't it? I never told him how to do it. He came to the forum and made a fool of himself all on his own. And now that it's been said does he not know how to deal with it. He could have just agreed and not cared for it any further. Yet he is quite upset about it. Funny.

And yes, DXVK is a step forward. But lets not act like it was the greatest step ever or that it was perfect. People will drop it like a turd the moment someone puts something similar directly into WINE. So you might want to keep it real. Or go nuts and go angry, whatever keeps you happy.

At the same time are people getting paranoid when Microsoft buys GitHub, while projects such as DXVK produce Windows DLLs and distributes these as binaries over GitHub as a solution for Linux.

Best part is, after I've been helping out at GitHub with DXVK on some issues has he banned me from it now. I haven't said a single bad word about him or his project there, only been helping others with it, and because he got baited and trigger here on Phoronix has he banned me from making further comments on issues. Hilarious. What a petty character he turns out to be. Goes mad on criticism.

VikingGe Did I make you sad? I'm so sorry...

[VikingGe]

Except that you're not criticizing anything. You haven't made any constructive suggestions on how to make anything better. The only thing you did is make claims that are blatantly false (the thing about winevulkan causing performance issues). I'm working with this code every day, you aren't, yet you're acting like you know it better that I do.

You're just shittalking, literally calling people "stupid" right at the start of the discussion, and have no idea what you're even talking about.

That said, banning you from my github is no loss. You haven't really contributed much besides a bug report that is lacking essential info so I can't even work on it. I don't need people like you.

[sdack]

Except that you're not criticizing anything. ... I don't need people like you.

Yes, I am and you hate it. And who cares if you can work on your DXVK? People don't care for you, they care for their games. That's why they're using it, and not because of you. And that's also why I made the report and gathered more info so those who use it can have a better time. Nobody cares who you are or who you need, VikingGe. If your code has bugs and you cannot work on it then that's your fault and nobody else's.

Regarding me calling others stupid, and I'll quote myself:

And how would it make a project more sensitive to a specific wine version than they already are when you remove a layer? Only if you're stupid really.

Feel free to explain to me how it's not stupid.

And while you're at it, say if you had to wait for the license dispute to settle before you could hope to use Vulkan 1.1, or if you could have used 1.1 (or parts of it) if you had directly implemented it as a WINE component and not used wine-vulkan.

Seems to me wine-vulkan has created an additional dependency, but maybe you're right and I'm the one being stupid for thinking it.