Package Details: wine-nine 3.0.2-2

Git Clone URL: (read-only)
Package Base: wine-nine
Description: Wine nine libraries to be used with Wine 3.x
Upstream URL:
Keywords: gallium nine wine
Licenses: LGPL
Submitter: gee
Maintainer: gee
Last Packager: gee
Votes: 6
Popularity: 1.633841
First Submitted: 2018-02-17 12:06
Last Updated: 2018-02-18 10:46

Dependencies (132)

Required by (0)

Sources (1)

Latest Comments

SR_team commented on 2018-02-24 15:18

@gee, I start game from Steam :)

gee commented on 2018-02-24 09:15

I have no idea if that is feasible sorry in any built in stuff sorry.

Now, I believe ninewinecfg enable/disable box only creates/removes a symlink. If that's the case, you could override that behavior in a script yourself when starting your apps.

SR_team commented on 2018-02-23 18:23

How I can disable nine for some apps (not bottles)?

lpr1 commented on 2018-02-22 05:45


Change your d3d dll overrides (if any), I had same problem with Split/Second, removing some libs would solve the problem, do it with clean prefix.

gee commented on 2018-02-18 14:37

I've just ran a few tests with Ultra Street Fighter IV (I'm not sure what other game installed has a benchmark).


wine-staging-nine 2.21: 202FPS

wine-staging-nine 2.21 + CSMT: 292FPS

wine-staging-nine 2.21 + nine (bundled in): 298FPS

wine-staging 2.21 + CSMT: 292FPS

wine-staging 2.21 + nine (mine): 298FPS

wine 3.2: 292FPS

wine 3.2 + nine (mine): 298FPS

In my case it seems about even between the 2 nine packages, though it does not seem like a great case as the difference between CSMT and nine is minimal. This makes me think the package is ok but there might be a difference with some games using different stuff, if you agree let's ask the nine guys.

gee commented on 2018-02-18 14:16


someone said something similar on phoronix so we may indeed have a problem.

When you say it is slower than regular GL wined3d, do you mean with the same Wine 3.x version you tried nine with?

In this package I'm using more recent nine stuff than wine-staging-nine I believe, so maybe something got messed up in recent nine patches.

I would assume that my package outcome would be either work or break not in between but I am not sure. If you want to root out any packaging issue feel free to grab the release yourself and build it using similar commands as in the official wine's PKGBUILD. You'll get a full wine build unlike here.

Another option would be to install standard staging 2.21, then switch this package's versions a bit: winever=3.0 => winever=2.0 ninever=2 => ninever=4 and build/install it. This may be more similar to wine-staging-nine, though I still think the nine part will be more recent, but the rest would be the same.

With some better idea of where the blame lies we can then involve the nine guys and ask for help.

I have not used Wine much lately myself so I don't have any good idea of performance.

I'm happy to get on irc to talk more about this if needed.

Vaporeon commented on 2018-02-18 12:51

Thanks for packaging this, seems this is the best way to go as upstream nine has essentially reached NEVER EVER status and wine-staging is dead.

however performance here seems much worse than nine patched wine-staging in some games, notably the PC port of halo. It's slower then even regular GL wine3d and even though it's an old game it still has issues with performance, especially with recent mods. Nine is helpful here when working, do you know what could be up?