We do often include affiliate links to earn us some pennies. See more here.

The big Wine 3.0 release is now officially available

By - | Views: 29,764

Good things come to those who wait, like a fine Wine. Today the Wine team has officially release the next stable version Wine 3.0 [Official Site].

After around a year of development during the 2.x cycle, Wine 3.0 brings in some major changes towards better game and application support for those of you wanting to run Windows-only stuff on Linux. It's nowhere near perfect, but it's a massive advancement for the Wine project and provides a good base for them to continue onwards.

Here's a few highlights from the mailing list announcement sent today:

  • Direct3D 10 and 11 support which includes:
    • Compute shaders
    • Hull and domain (tessellation) shaders
    • A large number of shader model 4 and 5 shader instructions
    • Cube-map arrays
    • Mip-map generation
    • And lots more
  • The Direct3D command stream, which is disabled by default. 
  • Support for OpenGL core contexts in Direct3D is improved. If you're using Mesa, you shouldn't need to set the "MaxVersionGL" registry key to enable Direct3D 10 and 11 support.
  • The Android graphics driver.
  • Improved DirectWrite and Direct2D support.

There's absolutely tons, that's me just cherry-picking random bits that I found quite interesting from this big release. For the next development cycle, we can look forward to things like Direct3D 12 and Vulkan support, OpenGL ES support to enable Direct3D on Android and plenty more.

You can find the brief official announcement here.

Article taken from GamingOnLinux.com.
Tags: Wine
21 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. Find me on Mastodon.
See more from me
The comments on this article are closed.
48 comments
Page: «3/5»
  Go to:

Kimyrielle Jan 18, 2018
Great that it's out now. I am looking forward to see continued improvements to DX11. I really hope they will concentrate on getting DX11 right, and not open another front with DX12. Who needs DX12 at this point anyway? Barely any game is using it, and from what I have heard it may become a fairly big flop. Developers seem to be reluctant to even want to use low-level graphics APIs and rather stick to DX11, which is deemed "good enough".
razing32 Jan 18, 2018
Quoting: coolbober
Quoting: Comandante ÑoñardoI wonder when We gonna see this included in Crossover..
Sometimes I wonder why people pays so much money for a computer game, but not for such a usefull tool like crossover. Crossover 17 is great, I can't wait for next release.

Was curios about that.
Is the support good ?
mrdeathjr Jan 19, 2018
Quoting: KimyrielleGreat that it's out now.

I am looking forward to see continued improvements to DX11.

I really hope they will concentrate on getting DX11 right, and not open another front with DX12.

Who needs DX12 at this point anyway? Barely any game is using it, and from what I have heard it may become a fairly big flop.

Developers seem to be reluctant to even want to use low-level graphics APIs and rather stick to DX11, which is deemed "good enough".

Very good point, for example polish another things case software vertex shaders needed for some old titles)

But now thanks projects like VKDX, wine must be begin transition to vulkan because runs in all os with all driver type: closed and open source

Will be more interesting vulkan

^_^
Shmerl Jan 19, 2018
Quoting: mrdeathjrYeah for wayland most big obstacle is games quantity inertia directly represented in this simple question:

Wayland runs all games runs in X and have support of games developers ?

As far I know, only some older versions of Unity use X directly. Newer ones should be using SDL. Same goes for other engines and games on Linux which either use SDL or GLFW or the like, to abstract the display server and input specifics.

http://www.glfw.org

So basically they don't need to worry about whether it's X or Wayland.
Comandante Ñoñardo Jan 19, 2018
Quoting: razing32
Quoting: coolbober
Quoting: Comandante ÑoñardoI wonder when We gonna see this included in Crossover..
Sometimes I wonder why people pays so much money for a computer game, but not for such a usefull tool like crossover. Crossover 17 is great, I can't wait for next release.

Was curious about that.
Is the support good ?

When you ask questions to the support, they answer..
And most supported games have an install script (like POL)



Quoting: Whitewolfe80Or you could get it free its called Wine and just diy your games and applications

The problem with Wine by itself is that it is difficult to configure...

I installed, with a couple of clicks, Perception




and Shadow Warrior 2







without any problem on codewavers Crossover 17...(well, there is a little choppy audio with both games and Shadow warrior 2 has some little graphical glitches, but the games are playable)
slaapliedje Jan 19, 2018
Quoting: Shmerl
Quoting: mrdeathjrYeah for wayland most big obstacle is games quantity inertia directly represented in this simple question:

Wayland runs all games runs in X and have support of games developers ?

As far I know, only some older versions of Unity use X directly. Newer ones should be using SDL. Same goes for other engines and games on Linux which either use SDL or GLFW or the like, to abstract the display server and input specifics.

http://www.glfw.org

So basically they don't need to worry about whether it's X or Wayland.

Am I missing something? Wayland under nvidia has worked for quite some time. I don't use wayland because they gimped the secondary clipboard, which I use all the time.
14 Jan 19, 2018
View PC info
  • Supporter Plus
Quoting: Shmerl
Quoting: GuestKDE devs don't care about nvidia and nvidia doesn't care about xwayland

Another reason to ditch Nvidia. In a few years, Nvidia will be barely used on Linux. See the trend on the same page you linked to.
Is your Nvidia decline prediction based on any information outside of your own preference and this website? I'm wondering what your sphere of influence is.

Another thought is if GNU desktop usage gets more Windows conversions, the Nvidia stats won't go down. Not everyone is going to feel compelled to use pure OSS right off the bat. Some people just want to get off Windows.

Even if Nvidia does end up declining in the GNU desktop world, I don't predict that happening in the Linux server world where GPU's are used for machine learning and data science tasks.
Shmerl Jan 19, 2018
Quoting: 14Is your Nvidia decline prediction based on any information outside of your own preference and this website?

It's quite simple. Nvidia will never reach the level of AMD integration, because they have no interest in opening and upstreaming their driver, and AMD already caught up to Nvidia in performance. So once they'll also catch up in hardware (Vega 2 and Navi), Nvidia will have only disadvantages on Linux, so there will be an accelerating switching away from it.

In the machine learning and server AMD has advantages over Nvidia as well. Their hardware supports asynchronous compute, while Nvidia one doesn't. Also, Khronos are pushing new converged API for graphics and compute, that will combine Vulkan and OpenCL. That would basically undermine CUDA and the grip that Nvidia has over compute market, because there will be zero benefits in using CUDA vs the new portable API. AMD are on the right track to unseat Nvidia from these markets.


Last edited by Shmerl on 19 January 2018 at 6:17 am UTC
cRaZy-bisCuiT Jan 19, 2018
@1050ti users: If you would have claimed nVidia GPUs and drivers are more competetive like 2 years ago, I'd totally agree.


Nowadays you'll have the Raven Ridge desktop APU right around the corner which should match the TDP of an 1050ti and CPU while still having enough performance. Also, 7 mm will be a thing soon and this time I expect AMD to be quicker than nVidia.


In combination with the fact that AMDs drivers are much better integrated in the Linux world I'd definitely stick with AMD and would go for AMD if I'd be owning an nVidia GPU.

As you can see in Phoronix benchmarks, the AMD driver's performance is now competitive to nVidia and also more and more devs actively support AMD Mesa drivers. As well as Valve does.
beniwtv Jan 19, 2018
Guys, don't forget Nvidia is a corporation - and they make their own driver, on their own. There is no community to help out. Right now, Nvidia has no business case for supporting Wayland or XWayland in their driver.

Their corporate Linux customers are staying on X for still a few years time, consumer Linux distros just have begun shipping usable versions of Wayland and DE's supporting Wayland, and not all consumers have switched or want to switch yet.

(Even though I think Wayland is pretty great myself and I am using it ;)

Once Wayland becomes mainstream, and X gets less and less attention, things will only start to work on Wayland, and eventually, everyone will need to switch (or compile their own old versions of X). I am sure that at that point, Nvidia will support Wayland and XWayland just fine.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.