dcoshea / NewWolfLives

A fork resurrecting NewWolf (Wolfenstein 3D for OpenGL on Windows)
4 stars 1 forks source link

NewWolfLives

A fork resurrecting NewWolf (Wolfenstein 3D for OpenGL on Windows)

NewWolf was last updated in 2006 (version 0.73). As I have not heard back from the author and have some fixes and ideas for improvements, I'm creating this fork for those who want a more modern (although perhaps less "authentic") Wolfenstein 3D experience. With the code on GitHub, it will be easy for anyone else to fork in case I also disappear!

Improvements over NewWolf

Fixes for bugs in NewWolf

Installation

  1. Go to http://newwolf.sourceforge.net/ and install the latest NewWolf version (0.73), plus any model and texture packs you'd like. Quick link to NewWolf itself: http://sourceforge.net/projects/newwolf/files/NewWolf%20GL/0.73/nwgl_73.zip/download That .zip file contains a readme.txt explaining how to run NewWolf. Get this working first. Note that the faq.txt suggests setting the screen resolution on the command line, but you can set it in game via the "Video Options" menu. You'll need to do it this way for the new video mode(s) added in NewWolfLives as I haven't told you what the mode numbers are!
  2. Download NewWolfLives from https://sourceforge.net/projects/newwolflives/files/releases/, unzip the .exe into the same directory as NewWolf.exe, and run it exactly as you would run NewWolf.exe.

How to build the sources

Supported development environments:

NewWolfLives uses CMake to generate its Microsoft Visual Studio solution/project files, which should make it easier to use different versions of Visual Studio and/or other compilers in the future. This means that, compared to NewWolf, there is an extra CMake generation step required before launching Visual Studio. This has been tested with CMake versions 2.6 and 2.8:

  1. Create a directory in which to perform the build. This does not have to be inside the working copy/source tree. For example, for consistency with NewWolf, create "prj_vs80" at the top level of the source tree.
  2. Open a Command Prompt in that directory.
  3. Run cmake.exe -G "<generator>" <path to source directory>, where can be "Visual Studio 8 2005", "Visual Studio 9 2008" or "Visual Studio 10" (i.e. 2010). To follow on from the example above, `cmake.exe -G "Visual Studio 8 2005" ..\src`. Sample output:
-- Check for working C compiler: cl
-- Check for working C compiler: cl -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: cl
-- Check for working CXX compiler: cl -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Configuring done
-- Generating done
-- Build files have been written to: C:/[...]/NewWolfLives/prj_vs80

In Visual Studio, you may wish to right-click on "NewWolfLives" in the Solution Explorer and select Set as StartUp Project so that the Start Debugging toolbar button works without requiring you to select an executable file name.

When you perform a build, output appears in the following sub-directories of the build directory, where CONFIGURATION is e.g. Debug:

Links