Wine Staging 2.17 Released With More Direct3D 11 Functionality

[VikingGe]

Even though Doom is programmed to use compat profiles, it doesn't actually. You can use an override and it will work.

How? If I do the usual MESA_GL_VERSION_OVERRIDE=4.3COMPAT, the game doesn't even start. It sort of works with Vulkan, but the textures are messed up (both on RADV and AMDGPU-PRO).

Probably the only reason why DOOM requires a compatibility profile context is that it uses GLEW, which at the time was probably the worst and most horribly outdated OpenGL loader available. AFAIK it relies on glGetString(GL_EXTENSIONS), which isn't part of the core profile.

[duby229]

How? If I do the usual MESA_GL_VERSION_OVERRIDE=4.3COMPAT, the game doesn't even start. It sort of works with Vulkan, but the textures are messed up (both on RADV and AMDGPU-PRO).

Probably the only reason why DOOM requires a compatibility profile context is that it uses GLEW, which at the time was probably the worst and most horribly outdated OpenGL loader available. AFAIK it relies on glGetString(GL_EXTENSIONS), which isn't part of the core profile.

What version of wine-staging are you using? You do need at least wine-staging 2.12. They patched it at that version so that it would work with the override.

[VikingGe]

What version of wine-staging are you using?

I've tested that already with several versions, including the current wine-staging 2.17. All I get is the usual window complaining that wglCreateContextAttribsARB failed.

Remember what I told you? Test this with a AMD graphics card using Padoka PPA, cause I guarantee it won't work.

Runs fine on my RX 480, not sure what you're talking about.

[Dukenukemx]

Hi-Angel point you in the right direction: try wine-staging

Who doesn't use Wine-Staging? Everyone uses Wine-Staging. I use Wine-Staging.

[Dukenukemx]

Also just bought Dying Light and it won't even start on my machine. And yea, it's the same problem.

https://steamcommunity.com/app/239140/discussions/0/1326718197205660517/?ctp=2

[timofonic]

It's okay they implement newer DirectX versions, they are lagging one version behind and need to catch up to the latest one. They need to accelerate development.

But what about applications? Sincerely, their appdb is a complete disaster and their bugtracker is full of outdated and duplicated issues.

What about making Wine Staging an official branch?

What about a more transparent development process?

What about switching to GitHub? It's okay it's becoming a monopoly, but there's lots more possibilities there for people to submit bugs and make pull requests. These days Wine seems too corporativized by Codeweavers, despite I appreciate the company managed to get profit and hire Wine developers.

[Hi-Angel]

What about making Wine Staging an official branch?

What do you mean? They use a single bugtracker. I don't know what else could be done.

What about a more transparent development process?

They're using mailing list, writing down the changes each release. How is that not being transparent?

[timofonic]

What do you mean? They use a single bugtracker. I don't know what else could be done.

The bugtracker is a trash can, lots of repeated issues and total lack of testing and following them on newer versions. I'm sure they have a private bugtracker at CodeWeavers, that's why it's so unmaintained.

I wrote about certain bugs and nobody from the team replied them. I don't see an organized team of testers or at least they aren't so organized or focused on very specific kind of software like videogames.

I'm more interested in "productivity" software, including CAD and CAE but not excluding others. My list is big.

I also will need to use Visual Studio for Windows, I wonder if it can be made to run in Wine and not need a VM for it.

I'm sure they need to follow the priorities marked by the planning their employers, but I guess most of them work for CodeWeavers.

They're using mailing list, writing down the changes each release. How is that not being transparent?

It's okay they use a mailing list, despite it's becoming an obsolete communication way.

I would prefer they adopt GitHub or GitLab+GitHub, it's a lot more user friendly and integrated. Their issues trackers are far less sophisticated and would be nice to include more features, but it's a lot more usable in a very considerable way due to it's simplicity and design (I agree it should be more powerful while having good design, but I found other issue trackers a lot more messy to use it (for users reporting issues) and that includes Bugzilla and MantisDB. An automated or half-automated issue reporting system would be interesting to have, but the reports being able to be viewed in the bugtracker and give more info if necessary.

[Hi-Angel]

I wrote about certain bugs and nobody from the team replied them. I don't see an organized team of testers or at least they aren't so organized or focused on very specific kind of software like videogames.

To me it rather looks like a lack of developers. Upon new Wine (not staging though) releases I often, out of curiosity, read the changelog. And in particular I do often follow links to some of fixed bugreports (their titles sometimes make me curious what was broken, what did they find). And, when bugs wasn't closed by accident, like "hey, it works in the newer version! — nice, closing as fixed", the developer's side of discussions is pretty active. However I do always see the same 1-2 names of them. And, by looking list of commits you can't say devs ain't do anything — half the commits is a fix to potential bug.

So I am inclined to think it's a lack of developers.

[timofonic]

To me it rather looks like a lack of developers. Upon new Wine (not staging though) releases I often, out of curiosity, read the changelog. And in particular I do often follow links to some of fixed bugreports (their titles sometimes make me curious what was broken, what did they find). And, when bugs wasn't closed by accident, like "hey, it works in the newer version! — nice, closing as fixed", the developer's side of discussions is pretty active. However I do always see the same 1-2 names of them. And, by looking list of commits you can't say devs ain't do anything — half the commits is a fix to potential bug.

So I am inclined to think it's a lack of developers.

That's sad if it's true, really. I also see their bugtracker is awful. What about migrating to GitLab?

• GNOME is going to switch to GitLab and they also have a testing GitLab instance.
• There are plans to make GitLab suitable for very big projects like the Linux kernel (see here, here and here).
• VLC uses GitLab too.
• Drupal has been discussing Gitlab migration and there has been a Technical Advisory Committee Update at 11 April 2017.
• Debian's Alioth is getting deprecated and there's an ongoing migration to GitLab. They said to migrate to Pagure and was some drama about GitLab, but that changed as you can also read on this mailing list message by Wirt. Their GitLab CE server is salsa.debian.org and it seems to be in testing phase.