No description
Find a file
Bill Currie 925797b1d4 [gamecode] Add a new Ruamoko instruction set
When it's finalized (most of the conversion operations will go, probably
the float bit ops, maybe (very undecided) the 3-component vector ops,
and likely the CALLN ops), this will be the actual instruction set for
Ruamoko.

Main features:
 - Significant reduction in redundant instructions: no more multiple
   opcodes to move the one operand size.
 - load, store, push, and pop share unified addressing mode encoding
   (with the exception of mode 0 for load as that is redundant with mode
   0 for store, thus load mode 0 gives quick access to entity.field).
 - Full support for both 32 and 64 bit signed integer, unsigned integer,
   and floating point values.
 - SIMD for 1, 2, (currently) 3, and 4 components. Transfers support up
   to 128-bit wide operations (need two operations to transfer a full
   4-component double/long vector), but all math operations support both
   128-bit (32-bit components) and 256-bit (64-bit components) vectors.
 - "Interpreted" operations for the various vector sizes: complex dot
   and multiplication, 3d vector dot and cross product, quaternion dot
   and multiplication, along with qv and vq shortcuts.
 - 4-component swizzles for both sizes (not yet implemented, but the
   instructions are allocated), with the option to zero or negate (thus
   conjugates for complex and quaternion values) individual components.
 - "Based offsets": all relevant instructions include base register
   indices for all three operands allowing for direct access to any of
   four areas (eg, current entity, current stack frame, Objective-QC
   self, ...) instructions to set a register and push/pop the four
   registers to/from the stack.

Remaining work:
 - Implement swizzle operations and a few other stragglers.
 = Make a decision about conversion operations (if any instructions
   remain, they'll be just single-component (at 14 meaningful pairs,
   that's a lot of instructions to waste on SIMD versions).
 - Decide whether to keep CALL1-CALL8: probably little point in
   supporting two different calling conventions, and it would free up
   another eight instructions.
 - Unit tests for the instructions.
 - Teach qfcc to generate code for the new instruction set (hah, biggest
   job, I'm sure, though hopefully not as crazy as the rewrite eleven
   years ago).
2022-01-03 00:49:49 +09:00
config.d [ruamoko] Replace rua_key with rua_input 2021-12-24 06:45:13 +09:00
debian [build] Move to non-recursive make 2020-06-25 11:35:37 +09:00
desktop [build] Move to non-recursive make 2020-06-25 11:35:37 +09:00
doc [doc] Fix some typos 2021-03-29 19:02:22 +09:00
hw Merge branch 'master' into vulkan 2020-06-25 14:03:52 +09:00
include [gamecode] Add a new Ruamoko instruction set 2022-01-03 00:49:49 +09:00
libs [gamecode] Add a new Ruamoko instruction set 2022-01-03 00:49:49 +09:00
m4 [build] Use AS_HELP_STRING on all the help strings 2021-12-24 06:45:13 +09:00
nq [math] Split out Quat/Vector compare implementations 2022-01-02 01:09:51 +09:00
pkg-config [build] Move to non-recursive make 2020-06-25 11:35:37 +09:00
qtv [qtv] Set worldmodel just after svc_modellist 2021-12-27 22:54:22 +09:00
qw [math] Split out Quat/Vector compare implementations 2022-01-02 01:09:51 +09:00
RPM [build] Move to non-recursive make 2020-06-25 11:35:37 +09:00
ruamoko [gamecode] Remove the wart from def and function names 2021-12-31 15:02:31 +09:00
tools [gamecode] Rename the old opcodes 2022-01-02 21:30:02 +09:00
.gitignore Update .gitignore yet again 2021-07-24 10:12:24 +09:00
bootstrap [build] Relax autoconf version requirement 2021-11-22 07:41:16 +09:00
configure.ac [build] Use AS_HELP_STRING on all the help strings 2021-12-24 06:45:13 +09:00
COPYING initial checkin of most recent newtree and nuq(?) source 2001-02-19 21:15:25 +00:00
INSTALL [build] Update for autoconf 2.71 2021-11-20 12:54:05 +09:00
Makefile.am [build] Move plist rules to root Makefile 2021-11-25 20:23:18 +09:00
NEWS Update for 0.7.2. 2013-01-23 12:01:36 +09:00
README.md Fix a spelling error 2021-12-06 09:10:16 +09:00
TODO Detect the silent death of the jack client thread. 2011-09-07 15:16:27 +09:00

QuakeForge

QuakeForge is descended from the original Quake engine as released by Id Software in December 1999, and can be used to play original Quake and QuakeWorld games and mods (including many modern mods). While this will always be the case, development continues.

However, QuakeForge is not just a Quake engine, but includes a collection of tools for creating Quake mods, and is progressing towards being a more general game engine.

Quake and QuakeWorld

Support for Quake and QuakeWorld is split into two program sets: nq for Quake and qw-client for QuakeWorld, with the target system as an additional suffix: -x11 For the X Window system (Linux, BSD, etc), -win for MS Windows (plus others that are not currently maintained).

Both nq and qw-client support multiple renderers: 8-bit software, 32-bit software, OpenGL 2, EGL (mostly, one non-EGL function is used), and Vulkan (very WIP), all within the one executable.

Dedicated servers for both Quake (nq-server) and QuakeWorld (qw-server) are included, as well as a master server for QuakeWorld (qw-master).

Tool

QuakeForge includes several tools for working with Quake data:

  • bsp2image produces wireframe images from Quake maps (bsp files)
  • io_mesh_qfmdl for importing and exporting Quake mdl files to/from Blender
  • io_qfmap for Quake map source files (WIP Blender addon)
  • pak create, list and extract Quake pak files. There's also zpak which can be used to compress the contents of pak files using gzip (QuakeForge has transparent support for gzip compressed files)
  • qfbsp for compiling map files to bsp files, includes support for vis clusters, and can be used to extract data and information from bsp files.
  • qfcc is QuakeForge's version of qcc, but is significantly more advanced, with support for standard C syntax, including most C types, as well as Objective-C object oriented programming (Ruamoko). Mmost of the advanced features require the QuakeForge engine, but qfcc can produce progs files compatible with the original Quake engine with limited support for some of the advanced featuers (C syntax, reduced global usage, some additional operators (eg, better bit operators, remainder (%)). Includes qfprogs for inspecting progs files.
  • qflight creates lightmaps for Quake maps
  • qfvis for compiling PVS data for Quake maps. One of the faster implementations available.
  • Plus a few others in various stages of usefulness: qflmp, qfmodelgen, qfspritegen, wad, qfwavinfo

Building

For now, please refer to INSTALL for information on building on Linux. Building for windows is done by cross-compiling using MXE. There are scripts in tools/mingw and tools/mingw64 that automate the process of configuring and building both the tools run on the build-host and the windows targets.