Skip to content
Build Gallium Nine support on top of an existing WINE installation
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
common ninewinecfg: Add debug tab Feb 25, 2019
d3d9-nine d3d9-nine: print dri3 warning in red Mar 12, 2019
ninewinecfg ninewinecfg: Add debug tab Feb 25, 2019
packaging/SPECS dri2: Drop dead Xext code Mar 12, 2019
tools Use 'wine64 winepath' to determine whether to skip 64bit Feb 24, 2019
.travis.yml
LICENSE
README.rst Update README with backends and D3D_BACKEND Feb 25, 2019
bootstrap.sh bootstrap.sh: Some clean up. Feb 26, 2019
meson.build
meson_options.txt
release.sh release.sh: use 'gallium-nine-standalone' as name Feb 2, 2019

README.rst

Gallium Nine Standalone buildstate

https://wiki.ixit.cz/_media/gallium-nine.png

About

Gallium Nine allows to run any Direct3D 9 application with nearly no CPU overhead, which provides a smoother gaming experience and increased FPS.

Gallium Nine Standalone, as the name implies, is a standalone version of the WINE parts of Gallium Nine.

This decouples Gallium Nine from the WINE tree, so that it can be used with any WINE version. There is no need for any WINE patches. A stable, development, or staging WINE release is sufficient.

Gallium Nine Standalone consists of two parts:

  • d3d9-nine.dll: Gallium Nine Direct3D 9 library
  • ninewinecfg.exe: GUI to enable/disable Gallium Nine with some additional info about the current state

Objective

  • Official distro packages

    Gallium Nine is a fork of the WINE tree, without any chances to be merged upstream. The decoupling of the WINE tree makes it its own upstream.

  • Ease updates for the user

    WINE can be updated independently of Gallium Nine Standalone. Users can mix releases of both projects to their liking. Switching between staging and non-staging does not require a rebuild.

Requirements

  • A Gallium based graphics driver (Mesa 3D)
  • Mesa's Gallium Nine state tracker (d3dadapter9.so)

Packages

Your distribution may provide a package, avoiding the need to compile the code yourself. The exact usage instructions may vary in this case so check your distribution for the details. The currently known packages are:

We also provide distro independent release binaries, available as GitHub releases. You can either download these yourself (see Usage below), or install them via Winetricks.

Usage

This part assumes that you downloaded a release binary or compiled using release.sh yourself.

  • Extract the tarball in e.g. your home directory
  • run the nine-install.sh script from the directory you extracted the tarball in

The latter symlinks the extracted binaries to your WINE prefix and enables Gallium Nine Standalone. To target another WINE prefix than the standard ~/.wine, just set WINEPREFIX accordingly before you run nine-install.sh.

Gallium Nine Standalone comes with a GUI.

For the 32bit version run wine ninewinecfg and for 64bit wine64 ninewinecfg.

Compiling

Please see our wiki, which also includes distro specific help.

Backends

The DRI3 backend is the preferred one and has the lowest CPU and memory overhead.

As fallback for legacy platforms the DRI2 backend can be used, which has more CPU overhead and a bigger memory footprint. The DRI2 fallback relies on mesa's EGL which provides EGLImages.

Debugging

You can use the environment variable D3D_BACKEND to force one of the supported backends:

  • dri3
  • dri2

If not specified it prefers DRI3 over DRI2 if available.

You can’t perform that action at this time.