As you know Stunts is a DOS game, and its natural environment is a native dos system, like DOS,Win95, Win98,winMe
On any other system than these you might meet some difficulties running Stunts.
In the case of WinXP you can try playing from the internal DOS emulation shipped with XP -many do succeed to run the game on a reasonable speed, many don't.
If you choose using this method, you need to set your sound to PC Speaker in the Stunts setup.
If you want higher quality sounds, you need a program called VDMSound, grab it at http://vdmsound.sourceforge.net
Since I have no experience setting up VDMSound (I'm a Linux user) I'll leave this up to you.
The other alternative is DosBox. You can find it at http://www.dosbox.sourceforge.net
DosBox emulates a Dos window rich in features, and I was able to run stunts on my 850Mhz Celeron under gentoo linux (probably for windows you need somewhat stronger) just as it runs on my 486PC, so it's perfect for racing.
The key for DosBox is its config file, called dosbox.conf (or in windows probably dosbox.cfg, i dunno. There are many programs to edit the settings of the config file,but we'll use a simple text editor, which is the easiest wax imho.
If you cant find the config file, start dosbox and write:
config -writeconf [pathtoconfigfile
it'll create a default config file for you.
Ok, now open up that nice config file and change the following settings after me:
1. Core Emulation[/u]
You might want to set
[cpu]
core=dynamic
but for me it brings the same speed as core=simple, so I didnt do this.
2. Scaling[/u]
Scaling is a way to resize the graphic output the game uses. It can eat much from your HW.
I supoose you wnat to play Stunts on fullscreen.
in this case search for these options and set them to the following:
[sdl]
fulldouble=false
fullfixed=false
fullresolution=0x0
output=surface
[render]
aspect=false
scaler=none
this will turn of scaling, and so if you are playing in a window it'll be very slow, but in fullscreen it's the fastest choice. You have to press ALT+ENTER to switch to fullscreen while DosBox runs, or set
[sdl]
fullscreen=true
If you prefer to play in a window change:
output=overlay
this will give ugly fonts, but great gamespeed.
3. Frameskip and CPU Cycles[/u]
this is also essential, and perfect settings mighr vary a lot depending on your system.
you wont even notice a frameskip of 1, but try to avoid higher numbers, since this is a simulation game. However for best racing performance you should set frameskip to 0. If the game runs to slow, change it to 1, or in the worst case 2. You can also change frameskip within dosbox CTRL+F8 raises one, and CTRL+F7 reduces one.
[render]
frameskip=0
CPU cycles is, basically said the speed of your emulated CPU. You'll need at least 3500 for enjoyable gameplay, I recommend 5000. Whil running DosBox you can raise it with CTRL+F12 (note this will make CPU usage higher, while framsekip on the contrary!), and reduce it with CTRL+F11
[cpu]
cycles=5000
Ok now you should try running stunts. Open up DosBox, and write the following things:
mount c /path/to/your/stunts
c:
stunts_k
this will start up stunts.
of course you might want to setup first - you can either choose sound blaster/roland/speaker - each of them is emulated perfectly.
Try to play a game, and watch your CPU usage if it reaches 100% or not (it's easy under linux, under windows you can notice it easily by the sound - if it chops/stops for a while then it's at 100%)
Ok, we have two possibilities now:
A. The CPU usage is nowhere near 100%, the game runs perfectly.
Congratulations! Happy racing! You might want to set a better quality scaler, increase CPU Cycles, or something like this to make gameplay more enjoyable. I'll leave finding out these up to you.
B. The CPU usage reaches 100%, the game movement is jerky, control is bad.
Ok, let's see what we can do in this case:
1. Set your screen spolor depth to 256 colors
2. In the dosbox config file set
[mixer]
rate=11025
this makes sound quality worse. You could also try setting your sound in setup to Roland/P Speaker - it's faster.
3. raise frameskip value, 2 maximally
4. reduce cpu cycles, 3500 minimally.
5. reduce graphic quality within Stunts
If you did all of this and still the game is too slow, then probabyl your CPU has not enough processing power to run a correct emulation for Stunts. Buy a faster one, or a used 486/Pentium to play. But hopefully you'll find yourself playing Stunts, and enjoying it :)
If you have any questions write it here.
This FAQ was based on Joekaos's DosBox FAQ found at http://dosbox.sourceforge.net/wiki/index.php?page=RunningResourceDemandingGames and my own experiences.
last mofiied: 20050128
I dont get it!! To hard for an average gamer!. Iv downloaded Dosbox, and thats it, i get stuck there. Thx
On my system, I lowered the cycles all the way to 1000, and that was still playable. Above that, sound sucked.
Things WERE quite playable running in NTVDM on Windows 2000, but the sound was PC Speaker, of course.
Pentium III 700, 384MB RAM, Win2K SP4.
where is your config file zak?
Quote from: "Anonymous"Oh, how nice.
Another spam robot, please delete this "Guest" post Zak.
Hi, I'm looking for a copy of the manual to get by the password protect!
Please read the "HOWTO: Disable security system" thread.
Hi all, I'm new to the forum.
My problem: I cannot hear the engine or "slipping" sound. Music is fine, as is everything else. Driving is pretty much impossible without the sound. :(
I'm using WinXP. The problem is the same using command prompt, DOSbox, or directly clicking on st.com. All Stunts versions give the same result. My sound setting is "Roland", others give no sound. My computer doesn't seem to have a PC speaker. My sound card is probably some cheap thing integrated to the motherboard.
Any help on the matter? I'm dying to play Stunts again!
Hi Ville.
I can't help much as I don't have Win XP, but there may be 2 solutions :
1/ use DOSBox, configure SoundBlaster sound in Stunts settings. It should work as DOSBox emulates SB in your own sound system.
2/ Use Zapper's pack of sound, available at ZakStunts website (http://stunts.mine.nu/zakstunts/ into "Downloads" section, "Add-ons and mods" category. Maybe this sound pack may work properly with your sound card...
Thanks Krys, I tried it again with DOSbox and finally managed to get it work perfectly! Yeeeeeha!
some great news:
Quote
As posted on Abandoneer, I got great news for the community. The DOSBox crew is planning on releasing long-awaited version 0.66 of their popular MS-DOS emulator by the end of this week!
I had the opportunity of playtesting one of the release candidates and, being a config rat as I am, the first and most important changes I've noticed is that it now supposedly detects and dynamically applies the best possible cycles and core definitions on the fly. Manual settings are still available, so it's just win-win!
Good news! Last week when I was playing Stunts at a friend's computer (current state of the art), I was not able to get it run properly, even playing with the Frameskip and CPU Cycles settings... :-\
Maybe I am just too stupid :D
There is at least two us, then. ;D
Excellent news. I hope it works on my computer (PIII), so I can finally play Stunts with sound on Windows XP.
Felt like providing a couple coments DOS-on-XP emulation... First of all, I'd advise people to avoid VDMSound altoegether. I used it to play under XP since I can remember, and only tried DOSBox around yesterday (for attempting NoRH-SDR). I never considered any performance issues for never having tried anything else. My initial runs unde DOSBox, however, induced me to some testing - I compared Stunts replay clock to my pulse watch results. Thing is, on my Athlon XP 2000+ with 256MB RAM, DOSBox runs on realtime and with reasonable CPU usage (setup at 12000 cycles), whereas VDM was about 9% slower! I feel cheated now... at least now its possible to race ZakStunts (non-Indy) properly! And BTW, if any newbie chooses to try DOSBox, get (from the official site) the D.O.G forntend (or anything similar). It makes the configuration process trivial...
I use DOSBox only for noRH racing at SDR competition. Else, pure DOS or Win 9x operating systems remain the best for full Stunts enjoyement.
I tryed with XP-SP2 without DOSBox : games runs much less smoothly, keypress have a delay to impact in the game (and even more delay for gear changes than for driving keys). Horrible.
DOSBox works perfectly for me. I use it in every stunts sesion. Cycles up to 10000, it's like pure DOS (I even find it better to drive in window mode instead of full screen mode)
Tested and confirmed : under Vista it's the same as Win XP with one more addition : if you want to capture video (as proof of noRH race for SDR noRH competition), you need to run Vista as administrator to get rid of the "read only" default option for your directory where Stunts is installed (stupid Vista feature IMO).
I have a problem: since I changed the setup.exe of Stunts in DOSBox, it runs only in 640*480 size in the middle of black screen both under pure XP and under DOSBox too (and many other applications, like Need for Speed Porsche Unleashed). I couldn't change it back... I think XP's own emulation files were overwritten somehow. Any ideas how to change it back to full screen?
Maybe it has no connection with DOSBox but things happened just after that.
Check your dosboc.conf file and look at line "scaler=XXXXX"'
What is the XXXX for you ? I suggest normal2x to have a DOSBox window correct. With other parameters it happens that DOSBox crashes or have some graphic bugs.
Still in the same file, there are some other parameters :
fullscreen=XXXXX
fulldouble=XXXXX
fullresolution=XXXXX
How your PC looks, it seems you selected :
fullscreen=true
fulldouble=false
fullresolution=original
Change either fulldouble parameter to true, or fullresolution to your screen resolution. This would make DOSBox run Stunts in full screen.
Else, write fullscreen=false and run the game in a window. ;)
Just reminding: if all else fails, you should consider System Restore... often it works wonders ;).
Thanks!
Krys: this pic was taken under XP-SP2 without DOSBox. NFS PU looked the same so it wasn't the DOSBox fault.
Solution: increasing number of cycles and a graphical setup command of my notebook seems to be the same. When I pressed it, system changed the application's running mode (with frame) independently from DOSBox. It was hard to find out but worked!
Krys, you recently had a forced upgrade to a dual core... as I'm going towards the same route within a month, is there anything in terms of Stunt-ing I should be wary of? (I'm moving to a Core 2 Duo, but will keep good ol' WinXP)
I don't know if it's due to DOSBox 0.7 instead of 0.65, or due to dual core processor, or due to Vista, or due to all of them, but DOSBox settings (cycles to 10000, no frameskip) that were very good on my old computer are just like hell in new one.
I found an average setting (cycles to 13500, frameskip set to 1) but it's far from perfect...
Virtual PC with pure DOS installed in virtual machine not tested yet, so I can't tell so far if it's a good alternative.
0.70 works almost without problems (in my current machine). Anyway, I won't quite enjoy racing in pure DOS (multitasking maniac ;)), so some setting battles lie ahead... thanks!
For me too. I guess Vista can be blamed for everything.
I tried to uninstall and reinstall DOSBox, change manually the property of capture subdirectory => always the same : this directory remains read only.
BUT I finally found where the videos are stored : in a hidden directory (quite stupid, best way for people to get a hard drive full of unuseful files without knowing why) !!!
This directory is (usernameprofile)/AppData/Roaming/DosBox-0.7/capture.
I don't think it's a decision of DOSBox team, it really seems that Vista works this way with all programs installed into Program Files directory as there are also numerous other files from other programs I installed.
So I tried to install DOSBox into another directory than default one (that is, install it not into Program Files folder) and then the program works normally : videos are into the capture subdirectory of DOSBox. Normal and easier to manage.
I'll keep this new installation, so I can keep hidden all system files as my children and my wife also use the computer and I don't want to take the risk to see them delete system files accidentally.
Regarding DOSBox parameters, I finally found a correct setting for playing Stunts with DOSBox under Vista (at last !) : set scaler to true and choose normal3x size (with normal2x I have same problems as with original resolution I used so far, 1 hour of tests proved it...).
Then, cycles at 16000 (this depends of your processor speed) and frameskip kept to zero.
Of course, scaler3x requires that your screen resolution is high (mine is 1440x900) as with scaler3x window size is 1024x768 !
This way, Stunts is correct. Not as perfect as pure DOS (nothing is I think), but as good as I had before with DOSBox on my previous (RIP) computer.
So, I won't have to always change to the very old computer in my daughter's bedroom to play Stunts. Finally !
Too bad for AbuRaf and for your future opponents... ;D
*Duplode's usability report of Stunts under Linux*
- Distribution: Fedora Core 8
- Machine: Core 2 Duo E6600 with 2GB RAM, good enough to run DOSBox-Stunts on XP very nearly flawlessy.
- DOSBox setup: The original intention was to get the DBGL package, create a new profile and run Stunts from my "old" folder on the secondary NTFS partition. Problem is, the DOSBox on DBGL package needs some SDL libraries to run in Linux. Since I couldn't work out how to get them with 3-minute Google-ing, I opted for an easier solution: grab the "bare" DOSBox 0.72 from Fedora repositories, create the profile at DBGL and then add this to ~/.bashrc :
alias stunts_k="dosbox -conf <path to Stunts *.conf file at DBGL profiles folder>"
Now I launch Stunts instantly by typing "stunts_k" on the terminal 8)
- Emulation speed: With scaler3x and 20000 cycles (similar to what I had under XP), I get perfect smoothness.
- Graphics: As good as ever :D Only thing is that, as Krys described for Vista above, window size under normal3x scaler is limited to 1024x768 even when fullscreen - same settings under XP allowed me to use 1280x960, which is as close to fullscreen as I can get with correct aspect ratio. But to me that's a minor issue.
- Sound: Slightly different. Music sounds clearer, crispier; on the other hand sometimes I notice quiet clacks when pausing/restarting replays. Overall, it's about as good as XP.
- Gameplay: At least, it's as good as XP.
- Overall impression: Very positive :)
To BJ and the other folks having trouble trying to race under DOSBox for FTT on slowish computers: Googling casually I came across this config file (http://wiki.gp2x.org/index.php?title=DosBox:Stunts&redirect=no) for DOSBox. It was written for use in GP2X, which seems to be a sort of handheld game console/media player (thus, pretty low specs). According to the page, the game is "Semi-Playable" on 200MHz (!) and FAST graphics settings (eyecandy disbaled in Stunts). I can't really test it to tell you what it plays like, but some of you guys might eventually find it useful... To try it, just copy the dosbox.conf part of the page, save as a text file and launch DOSBox from a command line like this:
dosbox -conf <path to the .conf you just saved>
Mmh, Dosbox used to work just fine, and it still does, except it doesn't load stunts anymore. I already reinstalled both Dosbox and stunts. When I start the program it only shows a blue square with info and then dosbox asks for a new command, it doesn't start the game. Anyone knows what I'm doing wrong?
did you mount the stunts directory?
Quote from: zaqrack on February 17, 2009, 12:39:55 PM
did you mount the stunts directory?
Yes, I mounted it. I added a picture of what I got when I called the program. At this point it should start, but it doesn't...
I can still play under windows, but my windows doesn't have a build in video capture function.
Protection crack (the blue page) is loaded and then program stops, so I think one file is missing in your Stunts directory, or one game parameter is badly adjusted. Try to run setup.exe first and put it to PC speaker sound. Maybe the default is on Adlib sound card and program stops because there's no sound parameters defined.
Quote from: OverdrijfI can still play under windows, but my windows doesn't have a build in video capture function.
So it means you want to give a try to noRH racing at FTT competition. Good news. :)
You are already enlisted in the website because you raced SDR noRH race(s) before so I added you for stats purpose. Send me by PM the password you want and I'll add it to your profile so you'll be able to publish your time on FTT website. ;)
Quote from: Krys TOFF on February 17, 2009, 04:24:42 PM
Protection crack (the blue page) is loaded and then program stops, so I think one file is missing in your Stunts directory, or one game parameter is badly adjusted. Try to run setup.exe first and put it to PC speaker sound. Maybe the default is on Adlib sound card and program stops because there's no sound parameters defined.
You're on to something. When closing setup in Dosbox it tells me that "setup.dat cannot be created". It might be a problem tha started out by moving from one harddisk to another one time to many, but I doubt it, since reinstalling didn't help either. O, and the file setup.dat does in fact exist, it's not missing. What's it supposed to read when you open it with notepad? Mine reads:
rem 4 1 -1 -1 -1 -1
load.exe /u MCGA /spc
Stunts
disk 'B'
disk 'B'
tdy.cod
QuoteQuote from: OverdrijfI can still play under windows, but my windows doesn't have a build in video capture function.
So it means you want to give a try to noRH racing at FTT competition. Good news. :)
You are already enlisted in the website because you raced SDR noRH race(s) before so I added you for stats purpose. Send me by PM the password you want and I'll add it to your profile so you'll be able to publish your time on FTT website. ;)
That was one of the things I was thinking about, the other was messing arround with the video, trying to fit more than two cars on a track or something like that...
Quote from: Overdrijf on February 17, 2009, 05:03:05 PM
You're on to something. When closing setup in Dosbox it tells me that "setup.dat cannot be created". It might be a problem tha started out by moving from one harddisk to another one time to many, but I doubt it, since reinstalling didn't help either. O, and the file setup.dat does in fact exist, it's not missing. What's it supposed to read when you open it with notepad? Mine reads:
rem 4 1 -1 -1 -1 -1
load.exe /u MCGA /spc
Stunts
disk 'B'
disk 'B'
tdy.cod
My SETUP.DAT says:
rem 4 4 -1 -1 -1 -1
load.exe /u MCGA /ssb
Stunts
disk 'B'
disk 'B'
tdy.cod
(I'm under Linux, but to DOSBox/Stunts the files should look the same). The only notable difference (ignoring the /ssb and /spc sound settings) is "rem 4 4" instead of "rem 4 1"; I have no idea on what it does but you could try changing it. If that doesn't do it, I suggest you to delete SETUP.DAT and run the Setup again.
Quote from: Duplode on February 17, 2009, 07:54:18 PM
Quote from: Overdrijf on February 17, 2009, 05:03:05 PM
You're on to something. When closing setup in Dosbox it tells me that "setup.dat cannot be created". It might be a problem tha started out by moving from one harddisk to another one time to many, but I doubt it, since reinstalling didn't help either. O, and the file setup.dat does in fact exist, it's not missing. What's it supposed to read when you open it with notepad? Mine reads:
rem 4 1 -1 -1 -1 -1
load.exe /u MCGA /spc
Stunts
disk 'B'
disk 'B'
tdy.cod
My SETUP.DAT says:
rem 4 4 -1 -1 -1 -1
load.exe /u MCGA /ssb
Stunts
disk 'B'
disk 'B'
tdy.cod
(I'm under Linux, but to DOSBox/Stunts the files should look the same). The only notable difference (ignoring the /ssb and /spc sound settings) is "rem 4 4" instead of "rem 4 1"; I have no idea on what it does but you could try changing it. If that doesn't do it, I suggest you to delete SETUP.DAT and run the Setup again.
Mmh, nope, doesn't work. Found out the folder had declared itself read only, so I changed that, didn't work either...
Weird thing...
My setup.dat says "rem 4 0 -1 -1 -1 -1"', following is same as you have Overdrijf.
I guess you should reinstall stunts. Take the package from my site, it worked at everyone by far.
Quote from: zaqrack on February 18, 2009, 10:18:45 AM
I guess you should reinstall stunts. Take the package from my site, it worked at everyone by far.
I already got the package of your site and unpacked it, didn't work on dosbox I'm affraid. Nor does un- and reinstalling Dosbox. What the beep have I done to this computer?
Remove Read-only, delete setup.dat and run setup again. Maybe it didn't work last time because it was read-only when you tried running setup...
The folder still says it's read only, all folders do, apparently, but the files themself say they're not. Installing a newer version of DOSbox yielded no results, making dosbox an exeption for the virus shield and firewall didn't do anything either. I'm starting to dislike XP over this...
Anyway, thanks for all the tips guys, but I'm taking this straight to the top: the dosbox forum... *insert some kind of really evil smiley here*
It works, for some reason. I have to mount the folder, then type in C: (or however I called the mount) enter, and then I can open the files, but not the normal way. Yeah sure...
when I try to run it in DOSBox, I get to the blue screen, then it says insert disk b
I tried it like 5 times
then I rebooted DOSBox and tried again, this time typing the entire 'stunts_k.exe' instead of just 'stunts_k' and it worked
strange
That's quite weird. Personally, I don't remember having this particular issue, but it's a fact that these emulated systems can be quite unpredictable for sure...
And welcome chapel :)
There is a easy way to play on a Win Seven installed on a 64-bit PC?
Quote from: Shoegazing Leo on November 21, 2014, 04:57:32 PM
There is a easy way to play on a Win Seven installed on a 64-bit PC?
DOSBox. Proper settings are depending on your computer. I use it with 12000 cycles, 0 frameskip under 64-bit Windows 8.1.
how I can configure? With 3000 cycles looked so slow (and the tile is very small)
Quote from: Shoegazing Leo on November 21, 2014, 05:59:12 PM
how I can configure? With 3000 cycles looked so slow (and the tile is very small)
CTRL-F11 and CTRL-F12.
Btw here is my config file.
# This is the configurationfile for DOSBox 0.74. (Please use the latest version of DOSBox)
# Lines starting with a # are commentlines and are ignored by DOSBox.
# They are used to (briefly) document the effect of each option.
[sdl]
# fullscreen: Start dosbox directly in fullscreen. (Press ALT-Enter to go back)
# fulldouble: Use double buffering in fullscreen. It can reduce screen flickering, but it can also result in a slow DOSBox.
# fullresolution: What resolution to use for fullscreen: original or fixed size (e.g. 1024x768).
# Using your monitor's native resolution with aspect=true might give the best results.
# If you end up with small window on a large screen, try an output different from surface.
# windowresolution: Scale the window to this size IF the output device supports hardware scaling.
# (output=surface does not!)
# 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. (Press CTRL-F10 to unlock)
# 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. Resetmapper only works with the defaul value.
# usescancodes: Avoid usage of symkeys, might not work on all operating systems.
fullscreen=false
fulldouble=false
fullresolution=original
windowresolution=original
output=surface
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper-0.74.map
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, then 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 decrease/increase with keycombo.(CTRL-F11/CTRL-F12)
# cycledown: Setting it lower than 100 will be a percentage.
core=auto
cputype=auto
cycles=12000
cycleup=10
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: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
# blocksize: Mixer block size, larger blocks might help sound stuttering but sound will also be more lagged.
# Possible values: 1024, 2048, 4096, 8192, 512, 256.
# prebuffer: How many milliseconds of data to keep on top of the blocksize.
nosound=false
rate=44100
blocksize=1024
prebuffer=20
[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 the README/Manual for more details.
mpu401=intelligent
mididevice=default
midiconfig=
[sblaster]
# sbtype: Type of Soundblaster to emulate. gb is Gameblaster.
# Possible values: sb1, sb2, sbpro1, sbpro2, sb16, gb, 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 might provide better quality (see oplrate as well).
# Possible values: default, compat, fast.
# oplrate: Sample rate of OPL music emulation. Use 49716 for highest quality (set the mixer rate accordingly).
# Possible values: 44100, 49716, 48000, 32000, 22050, 16000, 11025, 8000.
sbtype=sb16
sbbase=220
irq=7
dma=1
hdma=5
sbmixer=true
oplmode=auto
oplemu=default
oplrate=44100
[gus]
# gus: Enable the Gravis Ultrasound emulation.
# gusrate: Sample rate of Ultrasound emulation.
# Possible values: 44100, 48000, 32000, 22050, 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=44100
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: 44100, 48000, 32000, 22050, 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: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
# disney: Enable Disney Sound Source emulation. (Covox Voice Master and Speech Thing compatible).
pcspeaker=true
pcrate=44100
tandy=auto
tandyrate=44100
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).
# (Remember to reset dosbox's mapperfile if you saved it earlier)
# Possible values: auto, 2axis, 4axis, 4axis_2, fcs, ch, none.
# timed: enable timed intervals for axis. Experiment with this option, if your joystick drifts (away).
# 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=false
[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 (optional).
# 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.
# You can put your MOUNT lines here.
mount C D:\Games\Stunts
C:
I used the same cycles and copy your config file, but the video is not good (the images disappears) and I can't use full tile.
Quote from: Shoegazing Leo on January 07, 2015, 08:39:13 PM
I used the same cycles and copy your config file, but the video is not good (the images disappears) and I can't use full tile.
It depends on the computer parameters and the maybe on the OS, too.
Intel Core i7 is
OFF: I just realized that Windows 8.1 does not contain Experience Index function (the original Win8 did)... ::)
An i7 should blaze through any DosBox game, definitely configuration related. I have a much older machine (2007 called, they want it back...) but Stunts has no trouble.
I use the plain configuration, with just a few changes:
[sdl]
# fullscreen: Start dosbox directly in fullscreen. (Press ALT-Enter to go back)
fullscreen=false
# output: What video system to use for output.
# Possible values: surface, overlay, opengl, openglnb, ddraw.
output=openglnb
# 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.
priority=higher,pause
[render]
# scaler: Scaler used to enlarge/enhance low resolution modes.
# If 'forced' is appended, then 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.
scaler=normal2x
[mixer]
# prebuffer: How many milliseconds of data to keep on top of the blocksize.
prebuffer=100
[cpu]
# 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.
cycles=20000
# cycleup: Amount of cycles to decrease/increase with keycombo.(CTRL-F11/CTRL-F12)
cycleup=1000
# cycledown: Setting it lower than 100 will be a percentage.
cycledown=1000
In short: opengl for faster graphics, pause the game when I leave the window, larger buffer makes the sound nicer, and 20000 cycles so it runs smooth :)
Worked well about 20000 cycles
I forgot how to record as video. What is the shortcut?
Quote from: Shoegazing Leo on August 27, 2016, 12:02:45 AM
I forgot how to record as video. What is the shortcut?
CTRL + ALT + F5.
I'm taking a moment to appreciate that this is a thread about how to run an old game on this newfangled Windows XP thing.
I'm taking another moment to appreciate that the solution from back in those days still works.
I'm taking a third moment to appreciate how much smoother everything runs now that most of our current computers can handle Dosbox at 20.000 cpu cycles per second, rather than the "at least 3.500" (with an optional maximum frameskip of 2) that the opening post recommends.
I would like to take a fourth moment to appreciate even my phone runs it smoother than that, but that's not quite true yet (http://forum.stunts.hu/index.php?topic=3477.msg73393#msg73393). Maybe if you have a fancier phone than I have. But I will appreciate that in another decade or so.