Run EDuke32! EDuke32 (eduke32.exe) will allow you to play the game, and Mapster32 (mapster32.exe) lets you create custom maps.
NOTE: If you run Windows 8, Windows SmartScreen (Not smart in this case) may pop up and give you a warning about running the application. Click "More info" and then "Run anyway"
Q: When launching EDuke32, I get an error about a missing file called 'GAME.CON' or 'EDUKE.CON'. Help!
A: It would appear that you haven't placed a copy of 'DUKE3D.GRP' from your Duke Nukem 3D or Duke Nukem 3D: Atomic Edition CD into your EDuke32 directory. Once you place 'DUKE3D.GRP' into the same directory as 'eduke32.exe', the game should launch and run fine. You may also use the shareware version's 'DUKE3D.GRP' as well. If you're sure you've put 'DUKE3D.GRP' in the right place but you still get this error, your GRP file is likely corrupt and will need to be re-copied off of your CD.
Q: What is the 'Game' section of the startup screen used for?
A: The 'Game' section is a feature that allows you to select which GRP file you would like to play. The GRP files must exactly match the versions found on their respective CDs, without any modifications. The following games are supported:
Duke Nukem 3D Shareware Version Duke Nukem 3D Mac Shareware Version Duke Nukem 3D Duke Nukem 3D: Atomic Edition NAM (Note: you must rename GAME.CON from NAM to NAM.CON) Napalm (Wal-Mart only version of NAM, some .GRP differences between the two releases) WWII GI (Limited Support using NAM mode as a base)
You can also use the startup window to select a third party mod to play.
Q: When I am playing EDuke32 with 16-, 24-, or 32-bit color, everything has a blue tint! How can I fix this?
A: Unfortunately, most people who run into this error are out of luck, especially those with an Intel or SiS video chipset. There are a few things you can do to try and fix this problem:
Open the console and type "r_redbluemode 0" Download the newest drivers for your graphics card Delete the texture cache Try the most recent build of EDuke32
The following driver vendors have been blacklisted in the newest versions of EDuke32. If you have a video card or driver from one of these companies, OpenGL modes will not be available:
Microsoft (default OpenGL ICD which comes with Windows) SiS 3Dfx
OpenGL can still be enabled for these cards by setting the BUILD_FORCEGL environment variable before running EDuke32, or by using the command line eduke32 -forcegl. It should be noted, however, that the results will probably be less than satisfactory. If you have a blacklisted driver but EDuke32 seems to run fine using BUILD_FORCEGL, please enter the glinfo console command and send us your eduke32.log so that we can add an exception for your video card/driver combination.
Note: Intel video cards are no longer blacklisted. Note2: Some recent (G33 for example) Intel graphics cards work with OpenGL mode if texture compression is disabled (r_texcompr "0", see settings.cfg configuration file).
Q: Where is my "eduke32.log" and what is it used for?
A: The "eduke32.log" file is generated each time you run eduke32.exe. (mapster32.exe has a separate one titled, "mapster32.log") You can find both of these files in the same directory where your "eduke32.exe" and "mapster32.exe" is located. Having "Hide extensions for known file types" (Tools, Folder Options, View) unticked will help you locate it easier.
Q: If in system international properties system language is not English then symbol keys on keyboard is not work (Mac OS X). So I can't play the game. And I don't want to switch system language because I'm living in Russia. [followup Q: is there an OSX API call to set the keyboard layout per-process? If you're knowledgeable in OS X, please let the developers know!]
Q: I can't pan with Shift+KP5+KP<whatever> in 3D mode.
A: This is an issue with modern keyboards and happens because some key combinations are "dead" (See  for an overview and  for a technical explanation). There are various workarounds. One is to alias some key to the KP5 key with the goal of finding one for which all key combinations will be passed to the OS. To do that, you need to edit the remap line at the end of mapster32.cfg. A suggestion is to map the KP0 key to KP5. Another way to solve the issue is by finding a keyboard from circa 1996 (one with a big 5-pin connector). Newer revisions of Mapster32 also let you to use Alt instead of Shift in these situations.
Q: Why is aiming at objects so imprecise?
A: The issue occurs only with the Polymost renderer and has its cause in the way it determines the aimed-at object: based on the mouse position on the screen, it constructs a direction vector and calls hitscan. Both steps are a cause of imprecision. The classic BUILD and the Polymer renderers determine the aimed-at object (roughly) by querying what object was drawn at the mouse position, and thus are pixel-perfect. If you prefer to use Polymost, try avoiding aiming at objects at the border of the screen and looking up or down, since the aiming method is particularly ill-behaved in these cases. *update: actually it's a bug that need to be fixed some time.