0
Заходи на платформу и получай AGold!
AGold – это бонусные монеты игровой платформы AG.ruЗарегистрированные пользователи получают AGold за вход на сайт и тратят их на покупки в любых играх на платформе.
Присоединяйся!
Приглашай друзей – получай награду!
Зарегистрированные пользователи получают AGold за вход на сайт и тратят их на покупки в любых играх на платформе.
Присоединяйся!
Зарегистрированные пользователи получают AGold за вход на сайт и тратят их на покупки в любых играх на платформе.
Присоединяйся!
- Главная/
- Игры/
- Duke Nukem 3D/
- Читы
<=-------------------------------------=>
| THE DUKE NUKEM 3D TROUBLESHOOTER v1.7 |
<=-------------------------------------=>
This document is supposed to help people with the most common problems
concerning Duke Nukem 3D in addition to DN3DHELP.EXE. Before posting questions
concerning Duke3D be sure you've read this document and DN3DHELP.EXE in your
Duke Nukem 3D directory. This way we can concentrate on the more serious
problems and can respond quicker. If these documents don't answer your
questions feel free to ask your questions publicly in this forum.
This document will be constantly updated, so if you have anything to add or
correct please leave me a message.
-Steffen "Duke Addict" Itterheim [Apogee Forum Staff] 100606,2141
[Excerpts taken from DN3DHELP.EXE written by Joe Siegler [SysOp] 74200,553 with
help from Lee Jackson.]
COVERED TOPICS/PROBLEMS ARE:
============================
I) FILES OF IMPORTANCE
II) GENERAL HELP
III) VIDEO
IV) SOUND
V) NETWORK & MODEM
VI) CRASHES
VII) PERFORMANCE
VIII) MEMORY
IX) UPGRADING/PATCHING
X) CHEATING
XI) CONTROLLERS
XII) EDITING TOOLS ISSUES
XIII) ADD ON LEVELS
============================
I) FILES OF IMPORTANCE (GO APOGEE)
==================================
In Lib 1 - Useful Files:
UNIVBE51.ZIP - UNIVBE v5.1a universal VESA 2.0 driver (Shareware)
SDD52.EXE - Display Doctor (UNIVBE v5.2) VESA 2.0 driver (Shareware)
WAVEPTCH.ZIP - SB16 Wavetable Daughterboard fix for Duke3D and other games
PKZ204G.ZIP - PKZIP/PKUNZIP v2.04g (de-)compression utilities
IPXODI.ZIP - IPX protocol network drivers
ORDERNFO.ZIP - Apogee/3D Realms Ordering Information
DEALERS.EXE - Apogee Overseas Dealers
WINGAM15.TXT - Win95 Gaming Guide & Win95 specific troubleshooting
WINGAM15.ZIP - same as above but compressed in ZIP format
In Lib 3 - 3D Realms Games:
3DDUKE13.ZIP - Duke Nukem 3D Shareware v1.3D
11CONS.ZIP - Default .CON files for Duke Nukem 3D Shareware v1.1
In Lib 5 - 3D Realms Patches:
DN3D11PT.ZIP - Duke Nukem 3D Shareware v1.0 to v1.1 patch
DNSW13PT.ZIP - Duke Nukem 3D Shareware v1.1 to v1.3D patch
In Lib 7 - Hints & Cheats:
DUKE3D.TXT - Duke Nukem 3D cheat codes
In Lib 14 - Duke3D User Files:
DUKEBENC.TXT - Duke Nukem 3D Benchmark chart
D3DHELP.TXT - The complete "Duke Nukem 3D Troubleshooter" document
D3DHELP.ZIP - same as above but compressed in ZIP format
ADDICT*.ZIP - Demos from Duke 3D which show how to solve a specific level.
BUILDFAQ.ZIP - The Official BUILD FAQ, help file for level editing
Important Directories on the Duke Nukem 3D *Registered* CD
-------------
\GOODIES\BUILD (the level editor for Duke3D, see section XII)
\GOODIES\RTSMAKER (Utility to create your own RTS files)
\GOODIES\UNIVBE (UNIVBE 5.1a - Universal VESA 2.0 driver)
\GOODIES\WAD2MAP (WAD to MAP conversion utility)
II) GENERAL HELP
================
-=> The actual game version of Duke Nukem 3D Shareware is v1.3D (3DDUKE13.ZIP)
-=> The latest patch is Duke Nukem 3D Shareware v1.1 to v1.3D (DNSW13PT.ZIP)
-=> The registered version is v1.3D (CD-ROM only).
-=> Duke Nukem 3D can't be registered online, you'll have to fill out the
ORDER.FRM in your Duke3D directory and send or fax it to Apogee, or refer to
DEALERS.EXE for a local Apogee dealer (Note: Only few Apogee dealers also carry
3D Realms games).
-=> There will NEVER be an editor for shareware Duke Nukem 3D (see
LICENSE.DOC), but the registered version will come along with the developers
editing tools to allow you to create new levels, monsters, graphics, etc.
-=> The Shareware version of Duke3D won't load new levels/add-ons (except for
CONs and demos).
-=> It is recommended to load Duke3D from plain DOS (not a DOS box from within
Windows 3.x/95) which will result in better performance and less problems.
-=> It is always a good idea to keep the original ZIP files of Duke3D and other
games as well as their patches, so that you always have a "fresh" and
untempered version of Duke3D respectively other games.
-=> There will be a port of Duke Nukem 3D to the Macintosh. No date yet, but
I wouldn't look for it until 1997.
-=> There will ports of Duke 3D to the Sony Playstation, Sega Saturn, and the
Nintendo 64. "When they're done".
-=> There will be a level pack for Duke Nukem 3D at some time, but we have no
date yet.
-=> There is no save game in Co-Op play, but this _might_ be added in v1.4.
-=> A patch to v1.4 is already in development but there's no date yet. And no
list of changes either.
-=> The game does not support any of the 3D video accelerator cards, like the
"3D Blaster", etc..., nor are there any plans to add it.
-=> The DukeMatch RemoteRidicule uses the same RTS file format that Rise of the
Triad did, so you can use your favourite ROTT RTS files with Duke Nukem 3D!
III) VIDEO
==========
-=> VESA 2.0 support is needed for 320x200 (VESA 2.0) and 320x400 modes. UNIVBE
5.1/5.2 adds support of these modes to nearly all types of video cards (download
UNIVBE51.ZIP or SDD52.EXE). There are known problems with Matrox Millenium video
cards which should be fixed in UNIVBE/SDD 5.2 (Note: UNIVBE is not a product of
Apogee/3D Realms). Instead of downloading you can get UNIVBE v5.1 from the
registered CD-ROM located in the \GOODIES\UNIVBE directory.
-=> ATI MACH64 video card users reported problems concerning SVGA modes in
Duke3D. A patch available directly from ATI has helped a lot of users to get
Duke3D to run properly in SVGA with an ATI MACH64 video card. Try to load
M64VBE.COM in your ATI directory before running Duke3D and see if that helps.
ATI may already have a newer version of M64VBE.COM if you still have problems.
-=> If you had the VESA 2.0 modes working before but now they don't work any
longer it may be because you're using UNIVBE *shareware* which disables VESA
2.0 support exactly 21 days after installation (21 days evaluation period). If
this is the case it's time to register. ;)
-=> The RED BOX which appears in SETUP while choosing one of the VESA 2.0 modes
is just a reminder and does not necessarily imply that these modes won't work
on your system.
-=> If you have a Matrox Millenium card don't play in 800x600. The Matrox cards
don't seem to get along with Duke3D in this mode. Also be sure to have at least
BIOS version v1.9. Matrox recently released v2.0 of the Millenium bios. By
upgrading to this version you should be able to run Duke3D in 800x600 mode. It
appears that the lockups (savegame problem) with bios v1.9 are no longer a
problem. There still seem to be some minor glitches though. On the other hand
some people still have the same problems as before.
IV) SOUND
=========
-=> If you have a Creative Labs Soundblaster 16 (ASP) and a wavetable
daughterboard attached to it and you can't get Duke3D to work with General Midi
music download WAVEPTCH.ZIP and load it before running Duke3D. This should
help.
-=> Pro Audio Spectrum users need to load MVSOUND.SYS to make the PAS work.
Please consult your PAS manual if you don't know how to install this driver.
-=> If you can't get your soundcard to work with Duke3D at all check your SET
BLASTER= line. Look into DN3DHELP.EXE for more information about this and
configuring soundcards in general (page 11)!
-=> For troubleshooting try to use the lowest sound quality settings: 8 bit,
mono, 11 khz. I've heard that some soundcards do not support all mixing rates,
so try playing around with the "bit" and "kHz" settings.
-=> When using a soundblaster clone try setting it to MONO.
V) NETWORK & MODEM
==================
-=> If you continously get "out of sync" or "invalid game packet" errors or if
you experience connection losses please make sure that all players are using
the same .CON files. If you're using modified CONs then try to use the default
CONs instead. If you're playing via modem try to use 9600 as your baud rate
and/or turn OFF data compression and error correction (consult your modem's
manual). It is recommended though to use this Init String: ATZ&F&K0
If you are playing over a network try a different socket number. If this doesn't
help see the Troubleshooting section of DN3DHELP.EXE (page 14).
-=> If your modem neither dials nor answers nor responds to the init string
(you have to press ESC to go on that is) you probably don't have the proper
COM,IRQ,PORT ADDRESS values set in SETUP. Especially check for the right PORT
ADDRESS (possible values would be 2E8, 2F8, 3E8, 3F8)! (The same goes for serial
connections.) If you modem still doesn't respond see the Init String suggestions
in the Troubleshooting section of DN3DHELP.EXE (page 15). You can also try to
put an additional AT in front of your Init String, or a ~ or a simple blank
space.
-=> To get around the invalid packet problem, launch totally from the command
line (after trying to connect once the regular way). Use COMMIT.EXE instead of
SETUP, this should work. Command line parameters are documented in the
DN3DHELP.EXE file. An example would be:
SETUP /v2 /l03 /s2 /name whatever
This will let you change whatever you want in the setup program, and then go
directly to Episode 2, Level 3, Skill 2. Change this for whichever level/skill
you wish to play. This applies to both shareware and registered v1.3d. Replace
the
word "whatever" with the name you wish to be (it all must be one word).
-=> If the modem doesn't answer calls try to add S0=1 to your Init String.
-----------------------------
Info on Plug And Play Modems:
-----------------------------
If you are having problems using your Plug & Play Modem in DOS with our Duke
Nukem 3D (or any other of our modem games), the problem is this. Plug & Play
modems were designed for environments (ex: Win95) where the environment does
the initialization of the card.
The problem here is that if you are playing in MS-DOS mode, and bypassing the
Win95 GUI, your card is never being initialized, and as such, there's nothing
for our game to find.
What you will need to do is to find some way of initializing your PnP modem in
DOS. Info on this would be in the manual for the modem that you have. Quite
often modems with the brand name of "Winmodem" fall under this category, too.
Also, when you DO get the card configured in MS-DOS, make sure to take note of
the port address and IRQ number as well as the port number that the card is
initialized with. These WILL BE IMPORTANT when you setup the Duke3D game.
Once you have all this info from a properly initted PnP modem, go into the
Duke3D setup program, and:
0) DO NOT PICK DEFAULT FOR ANY OF THESE. ENTER INFO!
1) Select Modem Game
2) Select "Setup COM Port"
3) Select "Change Com Port" (If Necessary). Enter the Com port Number here.
4) Select "Change IRQ" (If Necessary). Enter the Com Port's IRQ # here.
5) Select "Change UART" (If Necessary). *THIS IS NOT 8250 or 16550*. This
is the hex address where your port resides at. For example, a value to
put here would be 02e8.
6) Put the port speed at 9600, and leave it there.
(This info is also useful if you don't have a PnP modem and are having
problems with your modem not being recognized.)
-=> If you can't resolve your modem connection problems try to establish
a connection via any telecommunication program (TELEMATE, TELIX, etc.), then
go into SETUP and choose "Already Connected" from the Modem Games menu.
VI) CRASHES
===========
-=> If you experience crashes try the following:
(refer to DN3DHELP.EXE for further help on these suggestions)
1) try a "clean boot" (no memory managers and no disk caching software
loaded)
2) temporarily disable sound & music via SETUP, if it stops
crashing you might experiencing a DMA conflict or something similar.
3) try the normal 320x200 video mode, if it stops crashing you might
experiencing problems with your video card and/or VESA driver.
4) push the "TURBO" button (if your system has one) and see if that helps.
5) Go edit your duke3d.cfg file with an ascii file editor, and look for the
line:
BlasterDMA16 = 5
Make it say this:
BlasterDMA16 = 1
-=> NEXGEN users reported slowdowns and crashes. There's a file IDON.COM from
NexGen which reportedly helped to solve some problems concerning NexGen CPU's.
-=> One word about DNCLIP: This cheat code is dangerous since it can cause
crashes long after its use. We don't recommend its use.
-=> If you have a Matrox Millenium card don't play in 800x600. The Matrox cards
don't seem to get along with Duke3D in this mode. Also be sure to have at least
BIOS version v1.9. Matrox recently released v2.0 of the Millenium bios. By
upgrading to this version you should be able to run Duke3D in 800x600 mode. It
appears that the lockups (savegame problem) with bios v1.9 are no longer a
problem. There still seem to be some minor glitches though. On the other hand
some people still have the same problems as before.
-=> If SETUP crashes with a "Spawn error: error 0" you have an incomplete
DUKE3D.GRP file, please re-install.
-=> From my own experience I learned that there is a BIOS option in AWARD BIOSes
which will cause the SETUP "Spawn error: error 0" and the Duke3D "Could not
initialize LINEEXE_LOADER" error. This option in the "Chipset Configuration" of
the BIOS is called "Memory Hole At 15-16M" or similar. You must disable this
option! It doesn't hurt to do so, only thing it does is to provide a memory hole
for those few cards who support a linear frame address as I understand. The
manual says it can speed up those cards but I doubt that this will be noticeable
anyway.
-=> Saving crashes when you run out of disk space, so please check if you have
enough free space on the drive you installed Duke3D.
-=> If you experience DIVIDE OVERFLOW errors and other crashes make sure that
"IDE HDD BLOCK MODE" is ENABLED in your BIOS Setup. Consult your motherboard
manual for information on the BIOS Setup Utility.
-=> "Cache Size of zero error"
If you go to start the game, and get an error that says CACHE SIZE IS ZERO, it
usually means that your game data is corrupt. Run Scandisk, or some other disk
repair program, and then delete the game totally. Reinstall. If that doesn't
work, check the size of the DUKE3D.GRP file, it should be 26,524,524.
VII) PERFORMANCE
================
-=> There are lots of reasons why Duke3D won't perform on some systems as
people think it should. This is mostly due to the different opinions of what
players call a "fluid" gameplay. Another point are the many components in a PC
(CPU, video, RAM) which all count into a game's overall performance.
A Pentium 100 with an ISA video card for example won't perform much better than
a medium fast 486. See the Duke Nukem 3D Benchmark chart (DUKEBENC.ZIP) for an
overview of several systems listed with their most important components and how
they perform in Duke3D.
-=> The system requirements are the minimum requirements to "enjoy" Duke. Of
course, there are people who claim that it runs smooth on their DX2-66 while
others with the same CPU say it's unplayable. There are two reasons, for one no
PC is the same as another. I've seen Pentiums running at 386 speed because
someone forgot to turn on internal cache. Especially slow graphic cards (all ISA
cards) won't be able to display decent framerates. And even PCs with the same
speed, processor and video card sometimes highly differ, performance wise. This
could be due to a slow motherboard, unoptimized BIOS settings and so on. So, if
we mention a DX2-66 with a VL card we mean a PC wich does not have serious
setbacks. However, many PCs have such setbacks (because vendors want to sell
their
PCs for the cheapest price possible), even those with faster CPUs sometimes run
about as fast as a well-optimized DX2-66.
-=> Using UNIVBE 5.1 for SVGA modes instead of the card's built in VESA BIOS
results in better performance in most cases.
-=> The same goes for running Duke3D directly from DOS rather than a Win'95 DOS
box, especially if your PC does have only 8 MB memory.
-=> Upgrading from 8 MB memory to 12 or 16 MB also helps to increase Duke3D's
performance (as well as nearly all other applications). It does have another
advantage as well, you don't necessarily have to remove disk caching software
like SMARTDRV from memory (Note: disk caches can cause certain problems in
certain circumstances...).
-=> NEXGEN users reported slowdowns and crashes. There's a file IDON.COM from
NexGen which reportedly helped to solve some problems concerning NexGen CPU's.
-=> Make sure your TURBO button (if your system has one) is turned on. ;)
-=> Contact someone who can have a look for your PC (local dealer/friend/etc.)
and who has the profession to tweak your PC's BIOS settings (Note: we can't do
this for you since it needs someone actually sitting in front of your PC due to
the wide variety of BIOSes and PCs; BIOS optimizing is *not* recommended if
you're not familiar with such things, there are certain options which may be
harmful to your system (and therefore your nerves ) - consult your
motherboard's manual if you want to have details about your PC's BIOS Setup
options. Tweaking the BIOS settings also sometimes helps to avoid crashes, but
it can as well cause new ones!
-=> If you have an ISA video card the game will play very sluggish (even on
Pentiums when compared to VESA Local or PCI bus video cards). Consult your
motherboard's manual to see whether it has VL or PCI slots. If not, you have an
(E)ISA video card in any case. If it supports VL and/or PCI cards but you want
to be sure about it contact your local dealer or someone who might be able to
tell you.
-=> Playing some of the higher levels causes the game to slow down, eventually
to a stop! This is a problem with the game engine in v1.3d. What's happening is
that the game is spawning an almost infinite number of game enemies in memory
(you can't actually see them), and because of this, it's slowing the game to a
crawl. We're looking into this for v1.4. No, there's no date on v1.4 yet.
VIII) MEMORY
============
-=> Please follow the guideline in DN3DHELP.EXE on how to "boot clean" and/or
create a bootable floppy disk if you get any "out of memory" errors. It's
always a good idea to do so if you experience severe slowdowns or unexpected
crashes. Also, this might also be necessary if you only have 8 megabytes of
memory.
IX) UPGRADING/PATCHING
======================
-=> If upgrading/patching is unsuccessful for some reason try to re-install
Duke3D into an empty directory and apply the patch again. Clean booting (see
DN3DHELP.EXE) may also help. All the patches won't work correctly if your
version is tempered in some way. So always keep a clean backup of the
Installation files.
X) CHEATING
===========
-=> One word about DNCLIP: This cheat code is dangerous since it can cause
crashes long after its use. We don't recommend its use.
XI) CONTROLLERS
===============
-=> If the mouse sensitivity is too high, you can fix this by deleting
DUKE3D.CFG and re-running SETUP.EXE. You can also try this if you have
problems with a joystick.
-=> Don't forget to check out the "Advanced Controller Setup" SETUP.EXE,
there you can configure your throttle and turn mouse aiming on/off and lots
of other things.
-=> Flip the switch on the bottom of the thing to "One", and make sure you pick
Thrustmaster in the Duke setup program. I heard that the MS Sidewinder 3D Pro
sometimes doesn't work as it should if the game is loaded from within a Win95
DOS box. Be sure to quit to DOS if you're having problems.
XII) EDITING TOOLS ISSUES
=========================
Please note that Build and Editart are not supported.
-=> The Level Editor BUILD and the other editing tools are by default
installed in the subdir \goodies and won't work correctly in that (the 3D view
is messed up in BUILD). You'll have to copy all files from the BUILD directory
into your Duke3D directory and it'll work just fine.
Oh, and don't copy it under Windows, use plain DOS. For some strange reason
this can cause the copy to behave erratically.
-=> Check out _SE.MAP and _ST.MAP for help on the Sector Effectors and Tags.
-=> If you can't find !SE.TXT: you already have this file! It's also in
BUILDHLP.EXE as the Sector Effector Reference section. You may also want to
check out SEHELP.HLP and STHELP.HLP, I think they're the same as !SE.TXT and
!ST.TXT.
-=> If BSETUP fails to save your settings remove the read-only flag from
SETUP.DAT, this can be done by typing "ATTRIB -R" in the directory containing
BUILD and Duke.
-=> Although it looks like it is possible to Setup BUILD to play Sounds&Music
and to run it in "multi-editing" mode via network, it isn't. I believe BSETUP
was Duke's former Setup program until it has been replaced by the one which
now comes along with Duke. Because of this there are still sound, music,
controller and networking options in there. However BSETUP does not save them,
only the video mode settings for BUILD's 3D mode. This is because BUILD does
not embody any network or sound/music code.
-=> If EDITART won't load and you get a black screen you have to extract all
TILES*.ART files from DUKE3D.GRP. Type
KEXTRACT TILES*.ART
in the directory containing KEXTRAC, EDITART and DUKE3D.GRP.
XIII) ADD ON LEVELS
===================
-=> They have to be in the same directory as Duke. You can run them by going
into SETUP and "Select User Level", then launch. From the command line you can
use the MAP parameter as follows:
DUKE3D MAP _ZOO[.MAP]
_ZOO[.MAP] being one of the levels shipped together with BUILD, this would be
the name of the desired add-on MAP file. The extension .MAP can be omitted.
--------------------------------
The Duke Nukem 3D Troubleshooter
--------------------------------
Copyright (C) 1996 by Steffen "Duke Addict" Itterheim
[Apogee Forum Staff] 100606,2141 All rights reserved.
Excerpts taken from DN3DHELP.EXE written by Joe Siegler [SysOp] 74200,553 with
help from Lee Jackson.
| THE DUKE NUKEM 3D TROUBLESHOOTER v1.7 |
<=-------------------------------------=>
This document is supposed to help people with the most common problems
concerning Duke Nukem 3D in addition to DN3DHELP.EXE. Before posting questions
concerning Duke3D be sure you've read this document and DN3DHELP.EXE in your
Duke Nukem 3D directory. This way we can concentrate on the more serious
problems and can respond quicker. If these documents don't answer your
questions feel free to ask your questions publicly in this forum.
This document will be constantly updated, so if you have anything to add or
correct please leave me a message.
-Steffen "Duke Addict" Itterheim [Apogee Forum Staff] 100606,2141
[Excerpts taken from DN3DHELP.EXE written by Joe Siegler [SysOp] 74200,553 with
help from Lee Jackson.]
COVERED TOPICS/PROBLEMS ARE:
============================
I) FILES OF IMPORTANCE
II) GENERAL HELP
III) VIDEO
IV) SOUND
V) NETWORK & MODEM
VI) CRASHES
VII) PERFORMANCE
VIII) MEMORY
IX) UPGRADING/PATCHING
X) CHEATING
XI) CONTROLLERS
XII) EDITING TOOLS ISSUES
XIII) ADD ON LEVELS
============================
I) FILES OF IMPORTANCE (GO APOGEE)
==================================
In Lib 1 - Useful Files:
UNIVBE51.ZIP - UNIVBE v5.1a universal VESA 2.0 driver (Shareware)
SDD52.EXE - Display Doctor (UNIVBE v5.2) VESA 2.0 driver (Shareware)
WAVEPTCH.ZIP - SB16 Wavetable Daughterboard fix for Duke3D and other games
PKZ204G.ZIP - PKZIP/PKUNZIP v2.04g (de-)compression utilities
IPXODI.ZIP - IPX protocol network drivers
ORDERNFO.ZIP - Apogee/3D Realms Ordering Information
DEALERS.EXE - Apogee Overseas Dealers
WINGAM15.TXT - Win95 Gaming Guide & Win95 specific troubleshooting
WINGAM15.ZIP - same as above but compressed in ZIP format
In Lib 3 - 3D Realms Games:
3DDUKE13.ZIP - Duke Nukem 3D Shareware v1.3D
11CONS.ZIP - Default .CON files for Duke Nukem 3D Shareware v1.1
In Lib 5 - 3D Realms Patches:
DN3D11PT.ZIP - Duke Nukem 3D Shareware v1.0 to v1.1 patch
DNSW13PT.ZIP - Duke Nukem 3D Shareware v1.1 to v1.3D patch
In Lib 7 - Hints & Cheats:
DUKE3D.TXT - Duke Nukem 3D cheat codes
In Lib 14 - Duke3D User Files:
DUKEBENC.TXT - Duke Nukem 3D Benchmark chart
D3DHELP.TXT - The complete "Duke Nukem 3D Troubleshooter" document
D3DHELP.ZIP - same as above but compressed in ZIP format
ADDICT*.ZIP - Demos from Duke 3D which show how to solve a specific level.
BUILDFAQ.ZIP - The Official BUILD FAQ, help file for level editing
Important Directories on the Duke Nukem 3D *Registered* CD
-------------
\GOODIES\BUILD (the level editor for Duke3D, see section XII)
\GOODIES\RTSMAKER (Utility to create your own RTS files)
\GOODIES\UNIVBE (UNIVBE 5.1a - Universal VESA 2.0 driver)
\GOODIES\WAD2MAP (WAD to MAP conversion utility)
II) GENERAL HELP
================
-=> The actual game version of Duke Nukem 3D Shareware is v1.3D (3DDUKE13.ZIP)
-=> The latest patch is Duke Nukem 3D Shareware v1.1 to v1.3D (DNSW13PT.ZIP)
-=> The registered version is v1.3D (CD-ROM only).
-=> Duke Nukem 3D can't be registered online, you'll have to fill out the
ORDER.FRM in your Duke3D directory and send or fax it to Apogee, or refer to
DEALERS.EXE for a local Apogee dealer (Note: Only few Apogee dealers also carry
3D Realms games).
-=> There will NEVER be an editor for shareware Duke Nukem 3D (see
LICENSE.DOC), but the registered version will come along with the developers
editing tools to allow you to create new levels, monsters, graphics, etc.
-=> The Shareware version of Duke3D won't load new levels/add-ons (except for
CONs and demos).
-=> It is recommended to load Duke3D from plain DOS (not a DOS box from within
Windows 3.x/95) which will result in better performance and less problems.
-=> It is always a good idea to keep the original ZIP files of Duke3D and other
games as well as their patches, so that you always have a "fresh" and
untempered version of Duke3D respectively other games.
-=> There will be a port of Duke Nukem 3D to the Macintosh. No date yet, but
I wouldn't look for it until 1997.
-=> There will ports of Duke 3D to the Sony Playstation, Sega Saturn, and the
Nintendo 64. "When they're done".
-=> There will be a level pack for Duke Nukem 3D at some time, but we have no
date yet.
-=> There is no save game in Co-Op play, but this _might_ be added in v1.4.
-=> A patch to v1.4 is already in development but there's no date yet. And no
list of changes either.
-=> The game does not support any of the 3D video accelerator cards, like the
"3D Blaster", etc..., nor are there any plans to add it.
-=> The DukeMatch RemoteRidicule uses the same RTS file format that Rise of the
Triad did, so you can use your favourite ROTT RTS files with Duke Nukem 3D!
III) VIDEO
==========
-=> VESA 2.0 support is needed for 320x200 (VESA 2.0) and 320x400 modes. UNIVBE
5.1/5.2 adds support of these modes to nearly all types of video cards (download
UNIVBE51.ZIP or SDD52.EXE). There are known problems with Matrox Millenium video
cards which should be fixed in UNIVBE/SDD 5.2 (Note: UNIVBE is not a product of
Apogee/3D Realms). Instead of downloading you can get UNIVBE v5.1 from the
registered CD-ROM located in the \GOODIES\UNIVBE directory.
-=> ATI MACH64 video card users reported problems concerning SVGA modes in
Duke3D. A patch available directly from ATI has helped a lot of users to get
Duke3D to run properly in SVGA with an ATI MACH64 video card. Try to load
M64VBE.COM in your ATI directory before running Duke3D and see if that helps.
ATI may already have a newer version of M64VBE.COM if you still have problems.
-=> If you had the VESA 2.0 modes working before but now they don't work any
longer it may be because you're using UNIVBE *shareware* which disables VESA
2.0 support exactly 21 days after installation (21 days evaluation period). If
this is the case it's time to register. ;)
-=> The RED BOX which appears in SETUP while choosing one of the VESA 2.0 modes
is just a reminder and does not necessarily imply that these modes won't work
on your system.
-=> If you have a Matrox Millenium card don't play in 800x600. The Matrox cards
don't seem to get along with Duke3D in this mode. Also be sure to have at least
BIOS version v1.9. Matrox recently released v2.0 of the Millenium bios. By
upgrading to this version you should be able to run Duke3D in 800x600 mode. It
appears that the lockups (savegame problem) with bios v1.9 are no longer a
problem. There still seem to be some minor glitches though. On the other hand
some people still have the same problems as before.
IV) SOUND
=========
-=> If you have a Creative Labs Soundblaster 16 (ASP) and a wavetable
daughterboard attached to it and you can't get Duke3D to work with General Midi
music download WAVEPTCH.ZIP and load it before running Duke3D. This should
help.
-=> Pro Audio Spectrum users need to load MVSOUND.SYS to make the PAS work.
Please consult your PAS manual if you don't know how to install this driver.
-=> If you can't get your soundcard to work with Duke3D at all check your SET
BLASTER= line. Look into DN3DHELP.EXE for more information about this and
configuring soundcards in general (page 11)!
-=> For troubleshooting try to use the lowest sound quality settings: 8 bit,
mono, 11 khz. I've heard that some soundcards do not support all mixing rates,
so try playing around with the "bit" and "kHz" settings.
-=> When using a soundblaster clone try setting it to MONO.
V) NETWORK & MODEM
==================
-=> If you continously get "out of sync" or "invalid game packet" errors or if
you experience connection losses please make sure that all players are using
the same .CON files. If you're using modified CONs then try to use the default
CONs instead. If you're playing via modem try to use 9600 as your baud rate
and/or turn OFF data compression and error correction (consult your modem's
manual). It is recommended though to use this Init String: ATZ&F&K0
If you are playing over a network try a different socket number. If this doesn't
help see the Troubleshooting section of DN3DHELP.EXE (page 14).
-=> If your modem neither dials nor answers nor responds to the init string
(you have to press ESC to go on that is) you probably don't have the proper
COM,IRQ,PORT ADDRESS values set in SETUP. Especially check for the right PORT
ADDRESS (possible values would be 2E8, 2F8, 3E8, 3F8)! (The same goes for serial
connections.) If you modem still doesn't respond see the Init String suggestions
in the Troubleshooting section of DN3DHELP.EXE (page 15). You can also try to
put an additional AT in front of your Init String, or a ~ or a simple blank
space.
-=> To get around the invalid packet problem, launch totally from the command
line (after trying to connect once the regular way). Use COMMIT.EXE instead of
SETUP, this should work. Command line parameters are documented in the
DN3DHELP.EXE file. An example would be:
SETUP /v2 /l03 /s2 /name whatever
This will let you change whatever you want in the setup program, and then go
directly to Episode 2, Level 3, Skill 2. Change this for whichever level/skill
you wish to play. This applies to both shareware and registered v1.3d. Replace
the
word "whatever" with the name you wish to be (it all must be one word).
-=> If the modem doesn't answer calls try to add S0=1 to your Init String.
-----------------------------
Info on Plug And Play Modems:
-----------------------------
If you are having problems using your Plug & Play Modem in DOS with our Duke
Nukem 3D (or any other of our modem games), the problem is this. Plug & Play
modems were designed for environments (ex: Win95) where the environment does
the initialization of the card.
The problem here is that if you are playing in MS-DOS mode, and bypassing the
Win95 GUI, your card is never being initialized, and as such, there's nothing
for our game to find.
What you will need to do is to find some way of initializing your PnP modem in
DOS. Info on this would be in the manual for the modem that you have. Quite
often modems with the brand name of "Winmodem" fall under this category, too.
Also, when you DO get the card configured in MS-DOS, make sure to take note of
the port address and IRQ number as well as the port number that the card is
initialized with. These WILL BE IMPORTANT when you setup the Duke3D game.
Once you have all this info from a properly initted PnP modem, go into the
Duke3D setup program, and:
0) DO NOT PICK DEFAULT FOR ANY OF THESE. ENTER INFO!
1) Select Modem Game
2) Select "Setup COM Port"
3) Select "Change Com Port" (If Necessary). Enter the Com port Number here.
4) Select "Change IRQ" (If Necessary). Enter the Com Port's IRQ # here.
5) Select "Change UART" (If Necessary). *THIS IS NOT 8250 or 16550*. This
is the hex address where your port resides at. For example, a value to
put here would be 02e8.
6) Put the port speed at 9600, and leave it there.
(This info is also useful if you don't have a PnP modem and are having
problems with your modem not being recognized.)
-=> If you can't resolve your modem connection problems try to establish
a connection via any telecommunication program (TELEMATE, TELIX, etc.), then
go into SETUP and choose "Already Connected" from the Modem Games menu.
VI) CRASHES
===========
-=> If you experience crashes try the following:
(refer to DN3DHELP.EXE for further help on these suggestions)
1) try a "clean boot" (no memory managers and no disk caching software
loaded)
2) temporarily disable sound & music via SETUP, if it stops
crashing you might experiencing a DMA conflict or something similar.
3) try the normal 320x200 video mode, if it stops crashing you might
experiencing problems with your video card and/or VESA driver.
4) push the "TURBO" button (if your system has one) and see if that helps.
5) Go edit your duke3d.cfg file with an ascii file editor, and look for the
line:
BlasterDMA16 = 5
Make it say this:
BlasterDMA16 = 1
-=> NEXGEN users reported slowdowns and crashes. There's a file IDON.COM from
NexGen which reportedly helped to solve some problems concerning NexGen CPU's.
-=> One word about DNCLIP: This cheat code is dangerous since it can cause
crashes long after its use. We don't recommend its use.
-=> If you have a Matrox Millenium card don't play in 800x600. The Matrox cards
don't seem to get along with Duke3D in this mode. Also be sure to have at least
BIOS version v1.9. Matrox recently released v2.0 of the Millenium bios. By
upgrading to this version you should be able to run Duke3D in 800x600 mode. It
appears that the lockups (savegame problem) with bios v1.9 are no longer a
problem. There still seem to be some minor glitches though. On the other hand
some people still have the same problems as before.
-=> If SETUP crashes with a "Spawn error: error 0" you have an incomplete
DUKE3D.GRP file, please re-install.
-=> From my own experience I learned that there is a BIOS option in AWARD BIOSes
which will cause the SETUP "Spawn error: error 0" and the Duke3D "Could not
initialize LINEEXE_LOADER" error. This option in the "Chipset Configuration" of
the BIOS is called "Memory Hole At 15-16M" or similar. You must disable this
option! It doesn't hurt to do so, only thing it does is to provide a memory hole
for those few cards who support a linear frame address as I understand. The
manual says it can speed up those cards but I doubt that this will be noticeable
anyway.
-=> Saving crashes when you run out of disk space, so please check if you have
enough free space on the drive you installed Duke3D.
-=> If you experience DIVIDE OVERFLOW errors and other crashes make sure that
"IDE HDD BLOCK MODE" is ENABLED in your BIOS Setup. Consult your motherboard
manual for information on the BIOS Setup Utility.
-=> "Cache Size of zero error"
If you go to start the game, and get an error that says CACHE SIZE IS ZERO, it
usually means that your game data is corrupt. Run Scandisk, or some other disk
repair program, and then delete the game totally. Reinstall. If that doesn't
work, check the size of the DUKE3D.GRP file, it should be 26,524,524.
VII) PERFORMANCE
================
-=> There are lots of reasons why Duke3D won't perform on some systems as
people think it should. This is mostly due to the different opinions of what
players call a "fluid" gameplay. Another point are the many components in a PC
(CPU, video, RAM) which all count into a game's overall performance.
A Pentium 100 with an ISA video card for example won't perform much better than
a medium fast 486. See the Duke Nukem 3D Benchmark chart (DUKEBENC.ZIP) for an
overview of several systems listed with their most important components and how
they perform in Duke3D.
-=> The system requirements are the minimum requirements to "enjoy" Duke. Of
course, there are people who claim that it runs smooth on their DX2-66 while
others with the same CPU say it's unplayable. There are two reasons, for one no
PC is the same as another. I've seen Pentiums running at 386 speed because
someone forgot to turn on internal cache. Especially slow graphic cards (all ISA
cards) won't be able to display decent framerates. And even PCs with the same
speed, processor and video card sometimes highly differ, performance wise. This
could be due to a slow motherboard, unoptimized BIOS settings and so on. So, if
we mention a DX2-66 with a VL card we mean a PC wich does not have serious
setbacks. However, many PCs have such setbacks (because vendors want to sell
their
PCs for the cheapest price possible), even those with faster CPUs sometimes run
about as fast as a well-optimized DX2-66.
-=> Using UNIVBE 5.1 for SVGA modes instead of the card's built in VESA BIOS
results in better performance in most cases.
-=> The same goes for running Duke3D directly from DOS rather than a Win'95 DOS
box, especially if your PC does have only 8 MB memory.
-=> Upgrading from 8 MB memory to 12 or 16 MB also helps to increase Duke3D's
performance (as well as nearly all other applications). It does have another
advantage as well, you don't necessarily have to remove disk caching software
like SMARTDRV from memory (Note: disk caches can cause certain problems in
certain circumstances...).
-=> NEXGEN users reported slowdowns and crashes. There's a file IDON.COM from
NexGen which reportedly helped to solve some problems concerning NexGen CPU's.
-=> Make sure your TURBO button (if your system has one) is turned on. ;)
-=> Contact someone who can have a look for your PC (local dealer/friend/etc.)
and who has the profession to tweak your PC's BIOS settings (Note: we can't do
this for you since it needs someone actually sitting in front of your PC due to
the wide variety of BIOSes and PCs; BIOS optimizing is *not* recommended if
you're not familiar with such things, there are certain options which may be
harmful to your system (and therefore your nerves ) - consult your
motherboard's manual if you want to have details about your PC's BIOS Setup
options. Tweaking the BIOS settings also sometimes helps to avoid crashes, but
it can as well cause new ones!
-=> If you have an ISA video card the game will play very sluggish (even on
Pentiums when compared to VESA Local or PCI bus video cards). Consult your
motherboard's manual to see whether it has VL or PCI slots. If not, you have an
(E)ISA video card in any case. If it supports VL and/or PCI cards but you want
to be sure about it contact your local dealer or someone who might be able to
tell you.
-=> Playing some of the higher levels causes the game to slow down, eventually
to a stop! This is a problem with the game engine in v1.3d. What's happening is
that the game is spawning an almost infinite number of game enemies in memory
(you can't actually see them), and because of this, it's slowing the game to a
crawl. We're looking into this for v1.4. No, there's no date on v1.4 yet.
VIII) MEMORY
============
-=> Please follow the guideline in DN3DHELP.EXE on how to "boot clean" and/or
create a bootable floppy disk if you get any "out of memory" errors. It's
always a good idea to do so if you experience severe slowdowns or unexpected
crashes. Also, this might also be necessary if you only have 8 megabytes of
memory.
IX) UPGRADING/PATCHING
======================
-=> If upgrading/patching is unsuccessful for some reason try to re-install
Duke3D into an empty directory and apply the patch again. Clean booting (see
DN3DHELP.EXE) may also help. All the patches won't work correctly if your
version is tempered in some way. So always keep a clean backup of the
Installation files.
X) CHEATING
===========
-=> One word about DNCLIP: This cheat code is dangerous since it can cause
crashes long after its use. We don't recommend its use.
XI) CONTROLLERS
===============
-=> If the mouse sensitivity is too high, you can fix this by deleting
DUKE3D.CFG and re-running SETUP.EXE. You can also try this if you have
problems with a joystick.
-=> Don't forget to check out the "Advanced Controller Setup" SETUP.EXE,
there you can configure your throttle and turn mouse aiming on/off and lots
of other things.
-=> Flip the switch on the bottom of the thing to "One", and make sure you pick
Thrustmaster in the Duke setup program. I heard that the MS Sidewinder 3D Pro
sometimes doesn't work as it should if the game is loaded from within a Win95
DOS box. Be sure to quit to DOS if you're having problems.
XII) EDITING TOOLS ISSUES
=========================
Please note that Build and Editart are not supported.
-=> The Level Editor BUILD and the other editing tools are by default
installed in the subdir \goodies and won't work correctly in that (the 3D view
is messed up in BUILD). You'll have to copy all files from the BUILD directory
into your Duke3D directory and it'll work just fine.
Oh, and don't copy it under Windows, use plain DOS. For some strange reason
this can cause the copy to behave erratically.
-=> Check out _SE.MAP and _ST.MAP for help on the Sector Effectors and Tags.
-=> If you can't find !SE.TXT: you already have this file! It's also in
BUILDHLP.EXE as the Sector Effector Reference section. You may also want to
check out SEHELP.HLP and STHELP.HLP, I think they're the same as !SE.TXT and
!ST.TXT.
-=> If BSETUP fails to save your settings remove the read-only flag from
SETUP.DAT, this can be done by typing "ATTRIB -R" in the directory containing
BUILD and Duke.
-=> Although it looks like it is possible to Setup BUILD to play Sounds&Music
and to run it in "multi-editing" mode via network, it isn't. I believe BSETUP
was Duke's former Setup program until it has been replaced by the one which
now comes along with Duke. Because of this there are still sound, music,
controller and networking options in there. However BSETUP does not save them,
only the video mode settings for BUILD's 3D mode. This is because BUILD does
not embody any network or sound/music code.
-=> If EDITART won't load and you get a black screen you have to extract all
TILES*.ART files from DUKE3D.GRP. Type
KEXTRACT TILES*.ART
in the directory containing KEXTRAC, EDITART and DUKE3D.GRP.
XIII) ADD ON LEVELS
===================
-=> They have to be in the same directory as Duke. You can run them by going
into SETUP and "Select User Level", then launch. From the command line you can
use the MAP parameter as follows:
DUKE3D MAP _ZOO[.MAP]
_ZOO[.MAP] being one of the levels shipped together with BUILD, this would be
the name of the desired add-on MAP file. The extension .MAP can be omitted.
--------------------------------
The Duke Nukem 3D Troubleshooter
--------------------------------
Copyright (C) 1996 by Steffen "Duke Addict" Itterheim
[Apogee Forum Staff] 100606,2141 All rights reserved.
Excerpts taken from DN3DHELP.EXE written by Joe Siegler [SysOp] 74200,553 with
help from Lee Jackson.