tech
/
worldspawn
2
0
Fork 0
Code Issues 16 Pull Requests Projects Releases Wiki Activity
69 Commits 2 Branches 0 Tags 5.7 MiB
C++ 53.6%
C 45.7%
Makefile 0.6%
GLSL 0.1%
Go to file
Marco Cawthorne 53992b8ed2 If LastFolder isn't set, pick enginePath, not userGamePath 2021-08-04 16:23:22 +02:00
docs Updated screen.jpg 2021-06-10 09:42:41 +02:00
include Change back some of the behaviour, because it'd break usability with 2021-08-04 12:09:49 +02:00
libs vmap: Allow non underscore versions of light key/value pairs 2021-06-29 21:11:40 +02:00
plugins Use pkg-config for gtkglext and some others 2021-06-07 08:20:34 +02:00
resources If LastFolder isn't set, pick enginePath, not userGamePath 2021-08-04 16:23:22 +02:00
src If LastFolder isn't set, pick enginePath, not userGamePath 2021-08-04 16:23:22 +02:00
tools Change back some of the behaviour, because it'd break usability with 2021-08-04 12:09:49 +02:00
Makefile rename radiant/ to src/, remove some redundant files, update paths, move 2021-06-05 19:11:38 +02:00
README.md Clarify build output 2021-06-07 08:45:47 +02:00
icon.png Initial commit 2020-11-17 12:16:16 +01:00
worldspawn.desktop If LastFolder isn't set, pick enginePath, not userGamePath 2021-08-04 16:23:22 +02:00

README.md

WorldSpawn Logo WorldSpawn

The worlds most opinionated fork of QER.

The editor we use at Vera Visions to create BSP levels. It was forked from NetRadiant in 2018 and was a result of necessity.

We wanted to move away from a proprietary toolchain that had technical issues the developer would not ever get back to us about, so we ended up here.

Use it if you actually want to use the features listed below - note that they require a modified engine as our BSP format is different from standard idTech 3 BSP. You will not be able to make levels compatible with other games and engines.

There's plenty of other editors for the first-party id Tech games.

Screenshot

Editor Changes

  • Valve 220 format is used top to bottom, imported & exported, with texture coords handled internally the same way
  • Integration with our material system (no more .shader files)
  • Support for vertex-color/alpha editing of patches using our new fixed patch format, allowing technologies such as 4-way texture blending and whatever your designers can imagine
  • Gracefully deals with duplicate entity attribute key/value pairs, to support features like Source Engine style Input/Output system for triggers
  • Simplified build system that doesn't suddenly break on its own, also less dependencies
  • Support for VVM/IQM model format in the BSP compiler
  • Support for internal and external High-Dynamic-Range lightmaps in the BSP compiler
  • Support for cubemap aware surfaces in the BSP compiler
  • Support for our patchDef2WS and patchDef3WS curved surfaces in the BSP compiler
  • More bug-fixes than you could possibly imagine

Compiling

To compile on a standard GNU/Linux system: LDFLAGS=-ldl make -j $(nproc)

On BSD you should probably use GNU make right now. The Makefiles are simple enough however. Clang should also be supported, pass CC=clang and CXX=clang++ if you want to use it.

On NT you'll probably have a build command-line likes this: CC=x86_64-w64-mingw32-gcc CXX=x86_64-w64-mingw32-g++ PKG_CONFIG_PATH=/usr/x86_64-w64-mingw32/sys-root/mingw/lib/pkgconfig make -j 4 Not all works yet, but stay tuned.

It'll compile everything into a subdirectory 'build'. At the end it'll copy files from ./resources into it too.

In the Nuclide SDK, build_engine.sh will call make with the appropriate flags for Linux/BSD automatically and move it into Nuclide's ./bin directory.

Dependencies

  • GNU make
  • gcc-core
  • gcc-c++ (or clang++)
  • gtk2-devel
  • gtkglext-devel
  • libxml2-devel
  • libjpeg8-devel
  • minizip-devel

Support

If you need help with this, you're better off using an alternative editor. Compatibility is not a priority here.