VOGONS


First post, by reble1

User metadata
Rank Newbie
Rank
Newbie

Dukem 3d is running slow and the sound cuts in and out. The 1st past is the bat file that starts the game.
--------------------------------
c:\dosbox\dosbox.exe -c "cycles 9000" -c "mount c c:\games" -c "c:" -c "cd dgames" -c "cd duke-n" -c "cd duke3d" -c "duke3d.exe asp"
---------------------------------
The 2nd past is the Dosbox config file.
---------------------------------
# This is the configurationfile for DOSBox 0.73.
# Lines starting with a # are commentlines.
# They are used to (briefly) document the effect of each option.

[sdl]
# fullscreen: Start dosbox directly in fullscreen.
# fulldouble: Use double buffering in fullscreen.
# fullresolution: What resolution to use for fullscreen: original or fixed size (e.g. 1024x768).
# windowresolution: Scale the window to this size IF the output device supports hardware scaling.
# output: What video system to use for output.
# Possible values: surface, overlay, opengl, openglnb, ddraw.
# autolock: Mouse will automatically lock, if you click on the screen.
# sensitivity: Mouse sensitivity.
# waitonerror: Wait before closing the console if dosbox has an error.
# priority: Priority levels for dosbox. Second entry behind the comma is for when dosbox is not focused/minimized. (pause is only valid for the second entry)
# Possible values: lowest, lower, normal, higher, highest, pause.
# mapperfile: File used to load/save the key/event mappings from.
# usescancodes: Avoid usage of symkeys, might not work on all operating systems.

fullscreen=TRUE
fulldouble=false
fullresolution=original
windowresolution=original
output=OVERLAY
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper.txt
usescancodes=true

[dosbox]
# language: Select another language file.
# machine: The type of machine tries to emulate.
# Possible values: hercules, cga, tandy, pcjr, ega, vgaonly, svga_s3, svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe.
# captures: Directory where things like wave, midi, screenshot get captured.
# memsize: Amount of memory DOSBox has in megabytes.
# This value is best left at its default to avoid problems with some games,
# though few games might require a higher value.
# There is generally no speed advantage when raising this value.

language=
machine=svga_s3
captures=capture
memsize=16

[render]
# frameskip: How many frames DOSBox skips before drawing one.
# aspect: Do aspect correction, if your output method doesn't support scaling this can slow things down!.
# scaler: Scaler used to enlarge/enhance low resolution modes. If 'forced' is appended,the scaler will be used even if the result might not be desired.
# Possible values: none, normal2x, normal3x, advmame2x, advmame3x, advinterp2x, advinterp3x, hq2x, hq3x, 2xsai, super2xsai, supereagle, tv2x, tv3x, rgb2x, rgb3x, scan2x, scan3x.

frameskip=0
aspect=false
scaler=normal2x

[cpu]
# core: CPU Core used in emulation. auto will switch to dynamic if available and appropriate.
# Possible values: auto, dynamic, normal, simple.
# cputype: CPU Type used in emulation. auto is the fastest choice.
# Possible values: auto, 386, 386_slow, 486_slow, pentium_slow, 386_prefetch.
# cycles: Amount of instructions DOSBox tries to emulate each millisecond. Setting this value too high results in sound dropouts and lags. Cycles can be set in 3 ways:
# 'auto' tries to guess what a game needs.
# It usually works, but can fail for certain games.
# 'fixed #number' will set a fixed amount of cycles. This is what you usually need if 'auto' fails.
# (Example: fixed 4000)
# 'max' will allocate as much cycles as your computer is able to handle
#
# Possible values: auto, fixed, max.
# cycleup: Amount of cycles to increase/decrease with keycombo.
# cycledown: Setting it lower than 100 will be a percentage.

core=auto
cputype=auto
cycles=auto
cycleup=500
cycledown=20

[mixer]
# nosound: Enable silent mode, sound is still emulated though.
# rate: Mixer sample rate, setting any device's rate higher than this will probably lower their sound quality.
# Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000, 49716.
# blocksize: Mixer block size, larger blocks might help sound stuttering but sound will also be more lagged.
# Possible values: 2048, 4096, 8192, 1024, 512, 256.
# prebuffer: How many milliseconds of data to keep on top of the blocksize.

nosound=false
rate=22050
blocksize=2048
prebuffer=10

[midi]
# mpu401: Type of MPU-401 to emulate.
# Possible values: intelligent, uart, none.
# mididevice: Device that will receive the MIDI data from MPU-401.
# Possible values: default, win32, alsa, oss, coreaudio, coremidi, none.
# midiconfig: Special configuration options for the device driver. This is usually the id of the device you want to use. See README for details.

mpu401=intelligent
mididevice=default
midiconfig=

[sblaster]
# sbtype: Type of sblaster to emulate.
# Possible values: sb1, sb2, sbpro1, sbpro2, sb16, none.
# sbbase: The IO address of the soundblaster.
# Possible values: 220, 240, 260, 280, 2a0, 2c0, 2e0, 300.
# irq: The IRQ number of the soundblaster.
# Possible values: 7, 5, 3, 9, 10, 11, 12.
# dma: The DMA number of the soundblaster.
# Possible values: 1, 5, 0, 3, 6, 7.
# hdma: The High DMA number of the soundblaster.
# Possible values: 1, 5, 0, 3, 6, 7.
# sbmixer: Allow the soundblaster mixer to modify the DOSBox mixer.
# oplmode: Type of OPL emulation. On 'auto' the mode is determined by sblaster type. All OPL modes are Adlib-compatible, except for 'cms'.
# Possible values: auto, cms, opl2, dualopl2, opl3, none.
# oplemu: Provider for the OPL emulation. compat or old might provide better quality (see oplrate as well).
# Possible values: default, compat, fast, old.
# oplrate: Sample rate of OPL music emulation. Use 49716 for highest quality (set the mixer rate accordingly).
# Possible values: 22050, 49716, 44100, 48000, 32000, 16000, 11025, 8000.

sbtype=sb16
sbbase=220
irq=7
dma=1
hdma=5
sbmixer=true
oplmode=auto
oplemu=default
oplrate=22050

[gus]
# gus: Enable the Gravis Ultrasound emulation.
# gusrate: Sample rate of Ultrasound emulation.
# Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000, 49716.
# gusbase: The IO base address of the Gravis Ultrasound.
# Possible values: 240, 220, 260, 280, 2a0, 2c0, 2e0, 300.
# gusirq: The IRQ number of the Gravis Ultrasound.
# Possible values: 5, 3, 7, 9, 10, 11, 12.
# gusdma: The DMA channel of the Gravis Ultrasound.
# Possible values: 3, 0, 1, 5, 6, 7.
# ultradir: Path to Ultrasound directory. In this directory
# there should be a MIDI directory that contains
# the patch files for GUS playback. Patch sets used
# with Timidity should work fine.

gus=false
gusrate=22050
gusbase=240
gusirq=5
gusdma=3
ultradir=C:\ULTRASND

[speaker]
# pcspeaker: Enable PC-Speaker emulation.
# pcrate: Sample rate of the PC-Speaker sound generation.
# Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000, 49716.
# tandy: Enable Tandy Sound System emulation. For 'auto', emulation is present only if machine is set to 'tandy'.
# Possible values: auto, on, off.
# tandyrate: Sample rate of the Tandy 3-Voice generation.
# Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000, 49716.
# disney: Enable Disney Sound Source emulation. (Covox Voice Master and Speech Thing compatible).

pcspeaker=true
pcrate=22050
tandy=auto
tandyrate=22050
disney=true

[joystick]
# joysticktype: Type of joystick to emulate: auto (default), none,
# 2axis (supports two joysticks),
# 4axis (supports one joystick, first joystick used),
# 4axis_2 (supports one joystick, second joystick used),
# fcs (Thrustmaster), ch (CH Flightstick).
# none disables joystick emulation.
# auto chooses emulation depending on real joystick(s).
# Possible values: auto, 2axis, 4axis, 4axis_2, fcs, ch, none.
# timed: enable timed intervals for axis. (false is old style behaviour).
# autofire: continuously fires as long as you keep the button pressed.
# swap34: swap the 3rd and the 4th axis. can be useful for certain joysticks.
# buttonwrap: enable button wrapping at the number of emulated buttons.

joysticktype=auto
timed=true
autofire=false
swap34=false
buttonwrap=true

[serial]
# serial1: set type of device connected to com port.
# Can be disabled, dummy, modem, nullmodem, directserial.
# Additional parameters must be in the same line in the form of
# parameter:value. Parameter for all types is irq.
# for directserial: realport (required), rxdelay (optional).
# (realport:COM1 realport:ttyS0).
# for modem: listenport (optional).
# for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
# transparent, port, inhsocket (all optional).
# Example: serial1=modem listenport:5000
# Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial2: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial3: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial4: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial.

serial1=dummy
serial2=dummy
serial3=disabled
serial4=disabled

[dos]
# xms: Enable XMS support.
# ems: Enable EMS support.
# umb: Enable UMB support.
# keyboardlayout: Language code of the keyboard layout (or none).

xms=true
ems=true
umb=true
keyboardlayout=auto

[ipx]
# ipx: Enable ipx over UDP/IP emulation.

ipx=false

[autoexec]
# Lines in this section will be run at startup.

Reply 2 of 17, by telanus

User metadata
Rank Newbie
Rank
Newbie

Try setting "cycles 9000" to "cycles max".

Reply 3 of 17, by reble1

User metadata
Rank Newbie
Rank
Newbie

Try setting "cycles 9000" to "cycles max".

The way the bat file was posted works just fine for Blake Stone, Cmd Keen, and Crystal cave. With changing the last directory name and the file name for each game. I have run the cycles down to 7000 and up to 27000 with no change in the sound or game speed.

Steve

Reply 4 of 17, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

duke3d is totally different game from those.

Water flows down the stream
How to ask questions the smart way!

Reply 5 of 17, by Zup

User metadata
Rank Oldbie
Rank
Oldbie

Explanation: cycles determines how many instructions per second is executing the virtual CPU. When you use cycles=9000 you're fixing or "capping" the CPU speed. How does it affect games?

If your game is very old (like Freddy Hardest, that was written for 4.77 mHz CPUs) it probably won't control the speed. If cycles is high, the game will too fast.

Most games will throttle with CPU speed, so you won't notice differences if the CPU is faster than needed (most games synchronize with VGA vertical redraw).

But, in every case (older and not so older games), if the CPU is slower than needed, the game will run... well, it will run slow. Also, if you set cycles to a value higher than your real CPU can cope, the game will run sluggerish (and other programs running in your system, also).

You must use cycles=auto (auto throttling of cycles) or cycles=max (max cycles for your CPU) always, unless you really want to fix the virtual CPU speed.

I think you're capping your CPU at a fast 386/slow 486 level, so trying to execute duke3d (with required a FAST 486) will be extremely painful.

I have traveled across the universe and through the years to find Her.
Sometimes going all the way is just a start...

I'm selling some stuff!

Reply 7 of 17, by reble1

User metadata
Rank Newbie
Rank
Newbie

I tryed setting "cycles max" and it made the sound more choppy and control of the game imposable.

Steve

Reply 8 of 17, by reble1

User metadata
Rank Newbie
Rank
Newbie

use 0.74

I tryed 0.74 and the game never finshed loading.

Steve

Reply 9 of 17, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

system?

Reply 10 of 17, by reble1

User metadata
Rank Newbie
Rank
Newbie

os xp pro

Reply 11 of 17, by Zup

User metadata
Rank Oldbie
Rank
Oldbie

They refer to system specs and OS... probably they're specially interested in CPU specs.

I have traveled across the universe and through the years to find Her.
Sometimes going all the way is just a start...

I'm selling some stuff!

Reply 12 of 17, by rfnagel

User metadata
Rank Oldbie
Rank
Oldbie

Dunno (as of yet) what you're PC specs are, but you might try lowering Duke Nukem 3D's video resolution to 640x480 (if you have it set to soemthing higher).

On my PC (Intel P4 2.666GHz/512MB RAM/WinXPProSP3) the game can get choppy at 800x600, but is fluid smooth at 640x480 😀

Also, as others (or at least one) has stated, use DOSBox v0.74... quite a few optimiztions in that newer version.

Lastly, you could try bumping down all of the audio sampling rates from 22,050 to 11,025... doesn't sound as nice, but can result in a little smoother gameplay 😀

Rich ¥Weeds¥ Nagel
http://www.richnagel.net

Reply 13 of 17, by reble1

User metadata
Rank Newbie
Rank
Newbie

laptop system info is.

hard drive capacity 232 gb free space 227 gb
OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 2 Build 2600
OS Manufacturer Microsoft Corporation
System Name LAPTOP
System Manufacturer Dell Computer Corporation
System Model Inspiron 4000
System Type X86-based PC
Processor x86 Family 6 Model 8 Stepping 10 GenuineIntel ~1002 Mhz
BIOS Version/Date Dell Computer Corporation A23, 11/7/2002
SMBIOS Version 2.3
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)"
User Name LAPTOP\steve
Time Zone Pacific Standard Time
Total Physical Memory 512.00 MB
Available Physical Memory 126.20 MB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.96 GB
Page File Space 1.22 GB
Page File C:\pagefile.sys

Reply 14 of 17, by Shagittarius

User metadata
Rank Oldbie
Rank
Oldbie

Looking at your specs I'm almost sure your trying to run it at 800X600 and thats the issue. I have a similar netbook and it can't run in the 800X600 resolution.

Set your cycles to max and rerun the install/setup program and choose 640X480. I think it should run fine that way.

Reply 16 of 17, by rfnagel

User metadata
Rank Oldbie
Rank
Oldbie

Yeah, a 1GHz processor is gonna be miserable with Duke Nukem 3D... even in 640x480 mode. You might try the lowest video resolution (IIRC 320x200), but it still might be choppy on your PC.

Rich ¥Weeds¥ Nagel
http://www.richnagel.net

Reply 17 of 17, by reble1

User metadata
Rank Newbie
Rank
Newbie

This laptop is all i have for now. Were i am living right now there is no room to setup my main tower computer, which is about 5x better in everything.

Steve