Frequently Asked Questions
EDuke32
Q: Where can I get a copy of Duke Nukem 3D to run EDuke32?
- A: Just click the gog.com banner to the left, where you can download the full, registered version of Duke Nukem 3D: Atomic Edition for the low price of $5.99! Alternatively, you can use the one episode shareware version which is available from 3D Realms for free. While the source code to Duke Nukem 3D has been released to the public under the GNU General Public License, the game's content (artwork, sounds, maps, et cetera) remains a commercial product. DO NOT post anywhere or ask anybody at all about where to acquire this game illegally. Support 3D Realms for making the most awesome game ever and don't be a pirate, yarrr!
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 theglinfo
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: How can I play multiplayer on the Internet or my LAN using EDuke32?
- A: See the Multiplayer page.
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.
- What is the log used for?
- Helping the EDuke32 developers and other helpful community members locate problems with a users EDuke32 if he or she is having trouble getting it to run, as the log file will 99% of the time indicate what is not working correctly plus many other various things that help developers and modders all around.
- Where should I paste my log or URL?
- Follow the instructions in the Troubleshooting EDuke32 page.
- Note: If you are having problems with Mapster32 you should do the same as above but replace "eduke32.log" with "mapster32.log"
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: What the heck are these new-fangled '.7z' files?
- A: Introduced in 1999, the 7-zip format offers better compression ratios than traditional .zip files, saving us space in storing our builds and saving you time in downloading them. Thanks, 7-zip! See the 7-zip site [1] for a great, free tool to extract them.
Q: What are the CRC/MD5/SHA1 for the various versions of Duke Nukem 3D?
A:
v1.5 DUKE3D.GRP (Atomic Edition):
CRC32: FD3DCFF1
MD5: 22B6938FE767E5CC57D1FE13080CD522
SHA-1: 4FDEF8559E2D35B1727FE92F021DF9C148CF696C
v1.3D DUKE3D.GRP:
CRC32: BBC9CE44
MD5: 981125CB9237C19AA0237109958D2B50
SHA-1: 3D508EAF3360605B0204301C259BD898717CF468
DUKE.RTS:
CRC32: 504086C1
MD5: 9D29F9673BBDB56068ACF7645C13749C
SHA-1: 738C7F5FD0C8B57EE2E87AE7A97BF8E21A821D07
---
VACA15.SSI (v1.5)
CRC32: B62B42FD
MD5: 22C8CD6235FC2B7ECEFEFC2442570D68
SHA-1: 84945D64E246E91840A872F332494D8509B66DD9
VACAPP.SSI (v1.4)
CRC32: 2F4FCCEE
MD5: 540AFD010435450D73FA3463437FCFC9
SHA-1: 58FD872BE376957D63D9F5C3BD169D5FCDF28664
VACA13.SSI (v1.3D)
CRC32: 4A2DBB62
MD5: 974616FC968D188C984E4F9A60F3C4BE
SHA-1: 2B7779AB211FB21CD2D7DEF93E2B9BBF948E406F
VACATION has 3 SSI files, one for v1.3D, one for the Plutonium Pack (v1.4) and one for Atomic Edition (v1.5).
---
NWINTER.GRP
CRC32: F1CAE8E4
MD5: 1250F83DCC3588293F0CE5C6FC701B43
SHA-1: A6728F621F121F9DB02EE67C39EFDBB5EEA95711
Nuclear Winter has a single GRP file, as it was not developed by Sunstorm Interactive like the above two, but rather Simply Silly Software (SSI is a Sunstorm Interactive format.)
---
DUKEDCPP.SSI (v1.4)
CRC32: B79D997F
MD5: F0BFA5B956C8E3DBCBA1042118C1F456
SHA-1: 30D6AA2A44E936D09D6B423CFAB7C0595E2376F9
DUKEDC13.SSI (v1.3D)
CRC32: A9242158
MD5: D085D538A6BF40EBB041D964787A5D20
SHA-1: 66A96327EC514710D3526D87259CF5C0ABBBB841
DUKEDC has 2 SSI files, one for v1.3D of the game and one for the Plutonium Pack (v1.4).
---
DUKEDC.GRP (CD version for Atomic Edition converted from SSI to GRP):
CRC32: A8CF80DA
MD5: 8AB2E7328DB4153E4158C850DE82D7C0
SHA-1: 1B66C3AD9A65556044946DD1CA97A839FCFEDC3B
VACATION.GRP (CD version for Atomic Edition converted from SSI to GRP):
CRC32: 18F01C5B
MD5: 1C105CED73B776C172593764E9D0D93E
SHA-1: 65B8B787616ED637F86CFCAA90DE24C8E65B3DCC
NWINTER.GRP (Atomic Edition):
CRC32: F1CAE8E4
MD5: 1250F83DCC3588293F0CE5C6FC701B43
SHA-1: A6728F621F121F9DB02EE67C39EFDBB5EEA95711
---
NAM.GRP:
CRC32: 75C1F07B
MD5: 6C910A5438E230F85804353AC54D77B9
SHA-1: 2FD12F94246FBD3014223B76301B812EE8341D05
NAPALM.GRP:
CRC32: 3DE1589A
MD5: D926E362839949AA6EBA5BDF35A5F2D6
SHA-1: 9C42E7268A45D57E4B7961E6F1D3414D9DE12323
NAPALM.RTS:
CRC32: 12505172
MD5: D571897B4E3D43B3757A98C856869ED7
SHA-1: C90B050192030FFBD0137C03A4181CB1705B95D3
NAM.CON and NAPALM.CON:
CRC32: 75EF92BD
MD5: CCBBB146C094F490242FD922293DD5F9
SHA-1: 46F3AE2B37983660835F220AECEEA6060C89F2A7
WW2GI.GRP:
CRC32: 907B82BF
MD5: 27E927BEBA43447DB3951EAADEDB4709
SHA-1: FD0208A55EAEF3937C126E1FFF474FB4DFBDA6F5
---
The link below also provides all other known CRCs for Duke Nukem 3D GRP files:
Mapster32
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 [2] for an overview and [3] 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.