Wine Staging 2.15 released with more Direct3D 11 improvements

Wine development is rapid, so hopefully it won't be long before more titles keeping people on Windows will work nicely under Wine on Linux.

Actually , until they work out of the box people will stay on Windows or will emulate Windows on Linux via vfio at best.

Personally i've tried Wine many (staging , devel and stable ) times but it is not attractive for people who are simply seeking their favorite Windows apps on Linux. There are so many workarounds to apply for app to app , you must create seperate prefixes. That is not attractive actually.

Even PlayOnLinux or Lutris like solutions are not working correctly most of the time.

Why should you run Windows in VM if Wine can run something? Amount of effort in setting up VMs is way more than setting up Wine, let alone if you need to set up PCI pass through and what not. And it's a major plus - not dealing with Windows at all.


Last edited by Shmerl on 23 Aug 2017 at 9:26 pm UTC

Why should you run Windows in VM if Wine can run something? Amount of effort in setting up VMs is barely smaller than setting up Wine, let alone if you need to set up PCI pass through and what not. Plus, it's a major plus not to deal with Windows at all.

Because Wine can run something with X version and it can be broken on with upcoming Y version.

Various hacks used successfully on X version might not work on Y version.

That's why.

Because Wine can run something with X version and it can be broken on with upcoming Y version.

Various hacks used successfully on X version might not work on Y version.

That's why.

I wouldn't touch Windows with a ten foot pole. And it's also the reason many use Wine if they can. If anyone can set up VMs, they surely can set up Wine. So out of the box argument is pointless if you compare that.


Last edited by Shmerl on 23 Aug 2017 at 9:29 pm UTC

Actually , until they work out of the box people will stay on Windows or will emulate Windows on Linux via vfio at best.

Implying anyone who can't/won't configure Wine would setup passthroughs for Windows?

Perhaps people who got bored of Wine or the ones that really wish to play the latest and greatest d3dX titles on release, but I highly doubt this is average Joe's main choice and only alternative when it comes to transitioning to a linux desktop.

Because Wine can run something with X version and it can be broken on with upcoming Y version.

Various hacks used successfully on X version might not work on Y version.

That's why.

I wouldn't touch Windows with a ten foot pole. And it's also the reason many use Wine if they can. If anyone can set up VMs, they surely can set up Wine. So out of the box argument is pointless if you compare that.

When you set up VM succesfully one time , no further fixes needed. It is basically Windows , much more effective than dual booting or using Wine.

I understand your Windows hate but sometimes Windows is a must.


Last edited by Leopard on 23 Aug 2017 at 9:39 pm UTC

Actually , until they work out of the box people will stay on Windows or will emulate Windows on Linux via vfio at best.

Implying anyone who can't/won't configure Wine would setup passthroughs for Windows?

Perhaps people who got bored of Wine or the ones that really wish to play the latest and greatest d3dX titles on release, but I highly doubt this is average Joe's main choice and only alternative when it comes to transitioning to a linux desktop.

Both Wine and VM are beyond the level of average Joe. Average Joe should stick with dual booting.

But for a person capable of setting up Wine through different hacks in order to run something , setting up a VM shouldn't be that hard.

Also it is a one time pain , once you set it correctly you are ready to go.

Wine is pain every time.

When you set up VM succesfully one time , no further fixes needed. It is basically Windows , much more effective than dual booting or using Wine.

Games configured in Wine for me very rarely need any tweaks with Wine versions bumps. Regressions can happen, but they are uncommon. Plus, I'd rather report bugs to Wine, than pay anything to MS.

I understand your Windows hate but sometimes Windows is a must.

Not for gaming.


Last edited by Shmerl on 23 Aug 2017 at 9:41 pm UTC

When I was testing 2.14 I filed a bug against Wine and Arch. It seems it's still present with 2.15.

Gave up on wine quite a while ago. I have enough to play in Linux, and last time I tried wine was more of a hassle to get a game working at all than it was worth it. I even had to create several steam-wine-prefixes because games were getting in each others way.

The VM option is feasable - but nah, seriously.

Both Wine and VM are beyond the level of average Joe. Average Joe should stick with dual booting.

But for a person capable of setting up Wine through different hacks in order to run something , setting up a VM shouldn't be that hard.

Also it is a one time pain , once you set it correctly you are ready to go.

Wine is pain every time.

While I wouldn't put Wine gaming in the same boat as accelerated vms, both cause it doesn't have to be hw supported and cause when it does work well with something it's really easy to setup even by first day migrants using PoL/Lutris and pleb-tier youtube guides, I agree it's not without a fair share of other drawbacks.

However your quote was in regards to Wine enabling and facilitating mainstream proselytism of users gaming on Windows out of necessity and as such I replied in accordance to this.

Most of the users being on the edge of switching to Linux for gaming are probably either linux users who still consider windows a better choice for their needs or half-techy windows users (ie /r/pcmasterrace) who have previously checked out linux but couldn't live without their games.

Regarding the ones that are somewhat tech-savvy, I'd expect most of them to hove already given it a chance. If it didn't change much then why would it now? It's not getting too much easier soon at this point.

To everyone commenting on the "Wine is a pain every time" part, Leo is most likely talking about configuring different prefixes for new games, not mointaining them.

Can't say I agree or disagree wholy with any school of thought on this.

Gave up on wine quite a while ago. I have enough to play in Linux, and last time I tried wine was more of a hassle to get a game working at all than it was worth it. I even had to create several steam-wine-prefixes because games were getting in each others way.

It's much easier to use without Steam (DRM-free games). And I indeed make a separate prefix for each game, it makes things easier to manage, not harder. Something went wrong and you messed up your settings irreparably? Just blow away the whole prefix and reinstall. Which would be too painful, if you piled up all games into one prefix. Steam makes it complicated and too bloated, since you'd need to replicate it in each prefix I suppose.


Last edited by Shmerl on 24 Aug 2017 at 12:30 am UTC

What exactly is so hard about using WINE? It seems to me that, not too long ago I had to disable stuff in services.msc to for halfway decent performance without Windows getting in the way of itself.
That said, it would be nice to make wrappers instead of prefixes, like WINE on Mac does, so we can be sure a version upgrade won't break configuration.

That said, it would be nice to make wrappers instead of prefixes, like WINE on Mac does, so we can be sure a version upgrade won't break configuration.

Developers can use Winelib already that way. It has a downside, you won't benefit from any performance improvements in newer Wine versions.

That said, it would be nice to make wrappers instead of prefixes, like WINE on Mac does, so we can be sure a version upgrade won't break configuration.

Developers can use Winelib already that way. It has a downside, you won't benefit from any performance improvements in newer Wine versions.

Yeah, there's always a trade-off. I wouldn't use it myself. So far, I don't know that I've truly seen a WINE regression, just a couple of instances where something else broke and it was easy to assume WINE was at fault... Much like people do Linux in general.

i use lutris mainly because it seems to work for me the best.playonlinux is a hit or miss and codeweavers which i paid for you will be lucky if you get games working right with that.apps im sure work great but that's not what i bought it for.so i just stick to mostly native linux games no headaches no issues.

I use Codeweavers' Crossover Linux myself and I am very happy with it, it is quite stable with new features enabled and a very good GUI. Been playing many games with it without problems.

I understand your Windows hate but sometimes Windows is a must.

It's a must when you want to have a look outside, but it's nowhere as useful as doors when you want to get out.

Dual booting, installing Linux, pretty much everything is beyond Average Joe.
So we need to talk about other people, with at least some technical expertese or willingness to read and try stuff.
And then wine or VM doesn't make a whole lot of difference in how hard it is.

Wine is very smooth for most games and a major pain with some. Not sure how much steam complicates things. I'm talking about GOG with a simple exe installer and with that it usually just works.

Here's one way to look at it. Dosbox allows me to play DOS era games. Wine allows me to play Windows XP era games. For that it works even better than modern Windows. It even allows me to play some newer Windows games!

Thanks to DOSBox I haven't needed DOS in the last 20 years. Thanks to Wine I haven't needed Windows in the last 10 years.

I'm running a Windows VM at work and it's a painful experience every time I must work with it. It takes too many resources to just run, that running anything inside it is really annoying. But because most of the customers of our company are using software, that can't be run in the wine, the VM is a necessary evil.

At home I'm playing mostly native games and testing some games on wine to fill AppDB data for the once I maintain.

Since there are several comments about the difficulties in setting up Wine prefixes, I'll just do a quick plug for my own little Wine management tool, Vineyard. With that installed, you can just double click a Windows executable, select which existing prefix to use or select "New prefix" (and if needed, select the Windows version to emulate, the virtual desktop size to use and which Winetricks packages to install) and click run; easy-peasy. It also comes with an indicator showing the running Wine applications (if they're launched through Vineyard) so you can check their output and it'll automatically suggest which Winetricks packages you might need to install based on the error messages.