Yamagi Quake II

Yamagi Quake II is an alternative client for id Softwares Quake II. Our goal is to provide the best Quake II experience possible, we strive to preserve the gameplay as it was back in 1997. Thus we aim mostly for bug fixes, stability and gentle enhancements were appropriate.

Features

Yamagi Quake II has a lot of unique features. The most notables ones are:

• A modern OpenGL 3.2 renderer, providing a greatly enhanced look and feel. The original OpenGL 1.4 and even the Software renderers are still supported. Both 3D accelerated renderers support anisotropic filtering and multisampling anti aliasing.
• Full support for widescreen displays and arbitrary resolutions. The HUD can be scaled to be readable on high resolutions.
• Support for surround sound, from stereo up to 7.1 channels and even HRTF. The background music can be played from OGG/Vorbis files, a CD drive is no longer necessary.
• A rewritten savegame system. Yamagi Quake II savegames are completely reliable and backward compatible between releases.
• Highly precise timings. For example, on a flat panel display with a 59.95 hertz refresh rate and vertical synchronisation (VSync) enabled Yamagi Quake II is running at exactly 59.95 frames per second.
• In comparison with the original client over 1.500 bugs were fixed. The Yamagi Quake II client is very well tested and stable. The dedicated server is able to run for weeks without a single restart. Last but not least the code is fully 64 bit clean and highly portable.

Yamagi Quake II supports the following platforms:

• FreeBSD
• Linux
• OpenBSD
• Windows

Some additional platforms are supported by the community. Yamagi Quake II works on them, but there may be bugs. The Yamagi Quake II developers may not be able to fix these bugs due to the lack of required hardware or software:

• Mac OS
• NetBSD
• Solaris

News

On 2018-07-14 Yamagi Quake II version 7.21 was released. Changes are:

• Fix some render glitches in the software renderer. (by Denis Pauk)
• Render the weapon independent of the current field of view, otherwise the weapon distorts with very high FOV settings. The weapons FOV can be set through r_gunfov, it defaults to 90.
• Rework the OGG/Vorbis backend. This fixes several annoying bugs, and adds support for alternative track <=> file mappings. Use this to implement support for the audio tracks supplied by the GOG.com version of Quake II.

On 2017-06-08 Three Wave Capture The Flag version 1.05 was released. Changes are:

• Some bugfixes to monster AI, mostly to keep the source in sync with baseq2 and the other addons.

On 2017-06-08 The Reckoning version 2.05 was released. Changes are:

• Fix a lot of potential crashes. (reported by Maarakate)
• Fix monsters running in place.
• Fix monsters not recognizing the player under some circumstances.
• Fix a rare progress stopper in xsewer1 in coop. (by Maarakate)
• Make Brains work again.

On 2017-06-08 Ground Zero version 2.04 and was released. Changes are:

• Fix a lot of potential crashes. (reported by Maarakate)
• Fix monsters running in place.
• Fix monsters not recognizing the player under some circumstances.
• Fix monsters getting stuck when resurrected by a medic.

Downloads

Source code archives for the official releases. Instructions for compiling the source into binaries are included:

• Yamagi Quake II Client and Dedicated Server: Yamagi Quake II, Version 7.21
• Three Wave Capture the Flag: Three Wave Capture the Flag, Version 1.05
• The Reckoning: The Reckoning, Version 2.05
• Ground Zero: Ground Zero, Version 2.04

Precompiled Windows binaries: Yamagi Quake II for Windows
Precompiled Mac OS binaries (unofficial): Yamagi Quake II for Mac
Archive with all code and binaries ever released: Yamagi Quake II Archive

Contribution and Bugreports

The development of Yamagi Quake II is hosted on Github. If you want to report a bug or send some nice patches please open an issue or a pull request in the appropriate subproject. You can find our organisation at: github.com/yquake2

If you’re planing to work on a bigger feature, please do yourself a favor and ask if we’re interested before spending time onto it. We don’t merge every feature that’s submitted to us just because the code is already there. Maintainability, integration with the existing code and our general focus are of great concern, too.