[Installation] [Command line] [Console Commands] [Performance] [Known Issues]

VHexen II

VQuake2, or Vérité-accelerated Hexen2, is native port of Hexen2 that takes advantage of hardware features in the v1000 chips, but will also work on v2x00 chips. It provides many of the features found in GLHexen2 such as bilinear filtering, which eliminates the appearance of square pixels, especially up close. VHexen2, like VQuake, contains at least one feature not available anywhere else -- anti-aliasing, which sharpens (straightens) otherwise jagged lines and blends particles.

Installation

[Command Line] [Console Commands] [Performance] [Known Issues]

1) Get vh2b5r2.zip.
2) Unzip the vh2.exe file into your \Hexen II folder. Unless you are running older graphics drivers, you should not need the other files contained in the the zip. Except the readme, of course.
3) Make sure you are running version 1.11 of Hexen II. The update is available from Activision here and here.
4) Run vqh2.exe to play.

Command Line

[Installation] [Console Commands] [Performance] [Known Issues]

Some configuration options for Hexen II can be activated only from the command line. In other words, they will have to be executed from a DOS prompt (in a DOS box), a batch file, or in a shortcut. Virtually all command-line options that apply to WinQuake and GLQuake apply here as well.

-heapsize
This command reserves memory for Hexen II's use. It must be followed by a number equal to the megs of RAM you want followed by 3 zeros. 24megs would be -heapsize 24000. In general, you do not want to reserve more than half your system memory. So if you have 32megs of RAM, don't exceed a value higher than 16000. In any case, Win95 will insist on using about 12-14megs for itself, so if you use too high a value, you may decrease performance by increasing the use of your swapfile.

-nojoy
This setting prevents Hexen II from polling the joystick port, which can unnecessarily consume CPU cycles if you are not playing with a joystick.

-nocdaudio
This setting prevents Hexen II from playing CD music and polling CD drive, which also can unnecessarily consume CPU cycles, especially if busmastering drivers are not installed.

-primarysound
Hexen II will use the DirectSound primary sound buffer instead of the secondary one. This can increase performance, but will not work on all systems.

-dinput
Enables DirectInput for your mouse or joystick, which can enhance control if you have the proper drivers installed.

-noipx
Disables IPX networking. -noudp disables TCP/IP and -nolan disables both. You might as well disable whatever you are not using as it does have an effect on performance. -nonet is an additional option that should just disable your network card (if any), allowing you to still use dial-up networking.

For example, let's say you wanted Hexen II to have 32 megs of memory dedicated to it. Your shortcut might end up looking like this

    "C:\Hexen II\VH2.exe" -heapsize 32000

(The quotes are necessary only because the naming of the "Hexen II" violates standard DOS naming convention. The real directory name under Win95 is "HexenI~1", which can be seen at the DOS prompt. "Hexen II" is actually a long-filename alias for "HexenI~1" in this case.)

Console Commands

[Installation] [Command Line] [Performance] [Known Issues]

Hit the "~" key to pull down the console and type one of the following commands, then hit <Enter>.

Alternately, you can put these parameters into a .CFG file where they will automatically be executed each time you run Quake. A basic tutorial for .CFG files is present here.

These are only a few select commands that are directly related to performance. For a more complete console command list, check Farenheit 176 at HexenWorld.

r_antialias (0-7; default 0)
This will antialias (sharpen the definition) for one or more of the following entities:
1 = world
2 = objects
4 = particles

In addition, you may add the values together. For instance, "r_antialias 5" would antialias the world and particles, and "r_antialias 7" would antialias everything. The more antialiasing done, the slower your game will run.

r_nomurk (0 or 1, default 1)
This command enables (1) or disables (0) the warping effect when under water (or lava). This choice is mostly a matter of preference in single-player, but disabling the waterwarp can make you more competitive in multiplayer as it easier to see without the normal haze-effect.  In single-player, I prefer to keep nomurk enabled (1) because it seems more realistic.

r_surfacelookup (0 or 1, default 1)
This parameter determines whether the Vérité (value = 1) or the CPU (value = 0) should translate textures into 16 bit format.  On slower systems (<P200), I think the value should definitely be left at 1 (Vérité).  On faster systems, you may get higher framerates with the CPU. Your results may vary at different resolutions or under different conditions.

r_refreshrate (any number greater than 1.0, default 85)
This determines the refresh rate in Hz for fullscreen modes (windowed play will use the desktop refresh rate).  Invalid values will give the next lowest available refresh rate, with a minimum of 60Hz.  You will need to restart Quake or switch video resolutions before this takes effect. Note: I could not get refresh rates above 85Hz to function.

d_mipscale (0-10?; default 1.0)
It seems that increasing this setting reduces texture detail for distant objects (wall, ceiling, floor textures, and some items only - not players, monsters, and other items). In other words, a setting of 2.0 means that your distance vision is twice as bad. Can you say "near-sighted"? A setting of "0" means that full-resolution textures will always be used, even for very distant objects. Try a setting of "0" and watch how much your system slows down when running through open areas!

d_mipcap (0-3, default 0)
Similar to "d_mipscale". However, the textures are just lower res period. While this setting and its cousin, d_mipscale, do increase performance, I recommend strongly against them. Why? Because Hexen II is such a beautiful game. The colors and textures are wonderful. It seems such a shame to use d_mipscale at any setting above "2", and d_mipcap at all.

Performance

[Installation] [Command Line] [Console Commands] [Known Issues]

For comparison purposes, I conducted benchmarks using my system. VHexen II ran at 30.3 fps at 640x480 (mean of 3 runs) with all the default options and the following command line:

"C:\Hexen II\VH2.EXE" -heapsize 32000

The demo used was ndemo3, created by Nuitari of HexenWorld.

r_antialias 1 28.3 fps (sharpen world)
r_antialias 2 28.6 fps (objects)
r_antialias 3 27.2 fps (world, objects)
r_antialias 4 30.3 fps (particles)
r_antialias 5 28.3 fps (world, particles)
r_antialias 6 28.5 fps (objects, particles)
r_antialias 7 27.2 fps (all three)

320x200 52.6 fps
320x240 49.8 fps
512x384 38.8 fps
640x400 34.6 fps
640x480 30.3 fps (baseline value)
800x600 11.8 fps (one run only)

r_surfacelookup 0 30.7 fps (uses CPU instead of Vérité for texture conversion)

r_refreshrate 60 30.1 fps
r_refreshrate 60 30.3 fps (baseline value)

d_mipscale 0 13.6 fps (one run only)
d_mipscale 1 30.3 fps (default /baseline setting)
d_mipscale 2 35.1 fps
d_mipscale 3 37.3 fps

d_mipcap 1 37.9 fps
d_mipcap 2 39.6 fps
d_mipcap 3 40.2 fps

Running the following command line options produced a 0.8 fps increase:     "C:\Hexen II\VH2.exe" -heapsize 32000 -nojoy -nolan -dinput -primarysound

Disabling "Vsync in Flip" in the Thriller's Advanced Properties produced a 0.3 fps increase because the video card no longer had to wait for the monitor to finish painting a screen before sending an updated image.

Issues

[Installation] [Command Line] [Console Commands] [Performance]

"I just installed VHexen II and it doesn't run."
Make sure you've upgraded Hexen II to version 1.11. Get the patch here or here. Also, make sure you have at least 24 megs of RAM and set you desktop to 16-bit color (that's 65,000 colors).

"VHexen II gives me an error that mentions something about a gfx.wad"
Make sure your shortcut has your Hexen II directory listed as the "Working" directory.

"When I run VHexen II, my graphics and colors are all wacky."
You must use a 16-bit desktop display setting (i.e. 65,000 colors) in order to run VHexen II.

"Particles are missing or messed up."
You probably have a v1000 card running old drivers. Update your drivers.

"Why does my hard drive light stay on?"
Lots of memory is a good thing. You need at least 24megs of RAM to even run Hexen II. Also, various add-on levels, mission packs, mods and conversions may have additional memory requirements. RAM is cheap. RAM is candy. Buy RAM.

Benchmarking System

[Installation] [Command Line] [Console Commands] [Performance] [Known Issues]

Relevant Hardware (latest non-beta drivers as of March 17, 1998)
Intel Pentium 166 MMX overclocked to 200MHz.
Megatrends HX-83 Motherboard
64mb 60ns EDO RAM (Micron)
Hercules Thriller 3D 4meg PCI
Creative Labs 3D Blaster Voodoo2
3.2gig Quantum Fireball EIDE Hard Drive
Soundblaster AWE64 Value
Diamond Monster Sound

Relevant Software and Settings
Win95b (OSR2)
1280x1024x16-bit Desktop Settings