Wine Begins Preparations For Reorganizing & Cleaning Up Its Direct3D Code

[phoronix]

Phoronix: Wine Begins Preparations For Reorganizing & Cleaning Up Its Direct3D Code

CodeWeavers developer Zebediah Figura opened up the initial merge request yesterday that is the first step of a multi-part effort for reorganizing and cleaning up the Wine Direct3D "WineD3D" code...

https://www.phoronix.com/news/WineD3D-Cleanup-MR-1

[rmfx]

Great move.

Now, it would be time to work with Valve a bit so that efforts are merged.

[DMJC]

I'd love it if they could fix up some of the old DirectX 1/2/3/4/5 issues. Still got a few games with problems there (which have never worked properly). WINE has for the most part been quite stable with few regressions over the years.

[mos87]

Yay! Better gaming!




For windoze...

[mos87]

I'd love it if they could fix up some of the old DirectX 1/2/3/4/5 issues. Still got a few games with problems there (which have never worked properly). WINE has for the most part been quite stable with few regressions over the years.

It's not granted that the cleaned up code would necessarily fix the issues. The bugs might need individual approach whether now or in the future.
And with the D3D versions this old, it might not be the optimal API to play those games anyway...

[Setif]

This will benefit developers as it makes code more comprehensible and easier to deal with.

[avis]

Yay! Better gaming!

For windoze...

I don't understand this comment. Are you trying to insult/mock Microsoft or Windows users? Why? Microsoft gives us stable APIs developers love to use. The Linux community rejects everything that's stable or compatible sans RHEL which barely anyone uses on the desktop, thus Wine was born. Win32 under Linux has proven to be a much better programming API than native Linux/POSIX API itself.

What exactly have you contributed to the world of Open Source or programming in general to act so haughty? Maybe you wrote the Vulkan spec?

[avis]

I'd love it if they could fix up some of the old DirectX 1/2/3/4/5 issues. Still got a few games with problems there (which have never worked properly). WINE has for the most part been quite stable with few regressions over the years.

AFAIK Wine's own D3D -> OpenGL translator has been stagnant for years while most of their efforts have been directed at VKD3D which only deals with D3D12 -> Vulkan.

Whether it's good or bad, I don't know. We have DXVK which is leaps and bounds better than OpenGL based WineD3D but depends on a working Vulkan implementation.

[WizardGed]

I don't understand this comment. Are you trying to insult/mock Microsoft or Windows users? Why? Microsoft gives us stable APIs developers love to use. The Linux community rejects everything that's stable or compatible sans RHEL which barely anyone uses on the desktop, thus Wine was born. Win32 under Linux has proven to be a much better programming API than native Linux/POSIX API itself.

What exactly have you contributed to the world of Open Source or programming in general to act so haughty? Maybe you wrote the Vulkan spec?

Quit putting words in their mouth. They said none of those things and you are once again being intentionally antagonistic. it is a fact that these kinds of improvements can and most likely will improve windows games more than native linux games. maybe try not to blow up just because of a simple disagreement on where value lies, there is almost no more inane argument then that.

[YCbCr]

AFAIK Wine's own D3D -> OpenGL translator has been stagnant for years while most of their efforts have been directed at VKD3D which only deals with D3D12 -> Vulkan.

Whether it's good or bad, I don't know. We have DXVK which is leaps and bounds better than OpenGL based WineD3D but depends on a working Vulkan implementation.

Not quite. There has been a Vulkan backend for WineD3D (Direct3D ≤ 11) for a few years now.

From the Wine 6.0 release notes:

An experimental Vulkan renderer for WineD3D is implemented. This
requires the vkd3d-shader library in order to translate Direct3D
shaders to SPIR-V shaders. In this release, shader support in the
Vulkan renderer is limited to shader model 4 and 5 shaders. In
practice, that limits its usefulness to Direct3D 10 and 11
applications. The Vulkan renderer can be enabled by setting the
Direct3D "renderer" registry setting to "vulkan".

The changes covered in this article are in fact about properly separating the OpenGL and Vulkan backends.