It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
This info is in the forum but I thought it might help someone to consolidate it into one post, with some extra stuff I worked out myself.

This will get Screamer 1 running with a good framerate, stable, and using a 360 or Xbox One joypad (or similar), including being able to change gears on the pad.

(I didn't really try the gears since the automatic black Porsche is enough to beat the game.)

After installing the game, locate dosboxScreamer.conf and load it into a text editor (Notepad will do).

First, something optional, but I like to play these old 4:3 games in a window instead of full-screen, and with mouse-lock off so it's easier to switch between them and other programs. If you want that, find the [sdl] section near the top, and change some of these settings:

[sdl]
fullscreen=false
fulldouble=false
fullresolution=original
windowresolution=2560x1920
output=overlay
autolock=false
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper.txt
usescancodes=true

That is for a 4K screen. If you have 1080p, halve the windowresolution values:

windowresolution=1280x960

In the [render] section, change it to this:

[render]
frameskip=0
aspect=true
scaler=none

Now the important/mandatory stuff. Changing the CPU settings is essnetial to a) be able to run setup.exe without it crashing, and b) get a good framerate. This is what I used:

[cpu]
core=normal
cputype=pentium_slow
cycles=150000
cycleup=1000
cycledown=1000

You'll need to add the cputype line to the default config, at time of writing. I'm not sure how important it is, though. core=normal is the vital part. Using core=auto makes a lot of games unstable. Not sure why gog do that so often; maybe auto uses less CPU but modern CPUs have no problem running DOSBox with it set to normal, which is more compatible.

The cycles setting seems very high compared to normal but is what I found good on an i7-8700k with medium overclock (4800MHz). The game only uses one thread so any CPU with similarly fast single-threaded perf should work well with that setting. If you find the audio stutters as soon as you start the game, try reducing it slightly until things are good. Going higher than that caused stuttering for me, and also did not seem necessary. You may be able to use "max" instead of a number but I didn't think to try that.

Now scroll down the config for the [joystick] section, and change it to this:

[joystick]
joysticktype=4axis
timed=false
autofire=false
swap34=false
buttonwrap=true

timed=false apparently helps with calibration in this and other games.

joysticktype=4axis will allow you to map up to 2 buttons. If you use 2axis then you can only map two buttons, which isn't enough.

Save your changes to that config file, as we're done editing it now.

OK, next, we need to make sure your joypad is the primary one, else DOSBox won't see it. To do this, push the Windows key and type "USB game controllers" (without the quotes) to find the game controllers control panel. It should list your controller, and maybe some others. Click Advanced and make sure the Preferred Device drop-down is set to the controller you want to use.

Now we set up the joypad in the game. To do this, you need to locate dosboxScreamer_single.conf and edit it in a text editor.

Near the end, change the line starth.exe to setup.exe

Now launch Screamer via the shortcut GOG provided. You should see the setup program launch. It can take a few seconds. If you still have a black or corrupt DOSBox window after 15 seconds or so, make sure you changed the CPU settings as described above; they're essential.

Once in the setup program, you can configure it to use your joystick and map the keys and steering axis there. Follow the instructions in the setup program and it's pretty straightforward.

Unfortunately, DOSBox doesn't give you much choice of which buttons you can map. The main A B X Y buttons will be the only four you can really use. You can use the shoulder buttons as well, but they'll be the same as A and B, so you can't for example use A and B for accelerate and brake and shoulder buttons for gears. But you can use A B and X Y for that.

You can't use the analogue triggers at all, unfortunately, at least without 3rd party mapping software. But it's fine for this game, I think. It doesn't have analogue acceleration anyway, only steering.

BTW, the setup program offers a choice of VGA and SVGA. I'm not sure it makes a difference but I'd leave it at the default VGA. Whether you run startH.exe (h = high res) or startL.exe (l = low res) seems to determine the res the game runs at.

After exiting the setup program, DOSBox should exit. Return to the dosboxScreamer_single.conf file and change setup.exe back to starth.exe

Now you're ready to race!

I found this setup completely stable and with a good framerate, and was able to finish the game without any further crashes. If you do still get crashes on the canyon track, try switching to startL.exe instead of startH.exe as people say it's more stable on that track (but looks worse). But, saying that, I think the CPU settings fix that instability as I never had another crash with them.

Have fun!

PS: Pro-tip, drive over the front of cars as you pass them in the pro leagues to make them crash without any harm done to you. They'll do the same thing to you! :-)
Post edited May 06, 2018 by LeoD
Good stuff, I'll try and see if the game doesn't crash so often after tweaking some of these specially the cpu thing.
Thanks
Post edited November 12, 2024 by 8-BitPenguin
avatar
LeoD: You can't use the analogue triggers at all, unfortunately, at least without 3rd party mapping software. But it's fine for this game, I think. It doesn't have analogue acceleration anyway, only steering.
That is incorrect actually. I'm not sure what the deal is, but with joysticktype set to auto my triggers register as BX axis. However with this setup the X axis on the right stick is disabled (which isn't a big deal). With joysticktype set to fcs the right stick is disabled, but the triggers still register as BX axis. I'm using a XB1 controller.
Apologies for reviving a months old discussion, but I thought to start from here, first, instead of posting a new thread.

I'm new to GOG and to PC gaming in general (I've been a console gamer forever though, and I'm still into retrogaming, on there). :)

This is my setup:
- MSI GS63 Stealth 8RE gaming laptop (i7, 16GB, GTX1060 6GB)
- AOC 1080p 144hz 25" monitor
- XBOX One controller
- Windows 10 Home Edition

I tried OP's guide in order to make the game more stable - it ran pretty well out of the box, with default options and SVGA, but of course I got no controller support, and random freezes during the first couple of races.

I thought to recap my current situation on here too:

--- XBOX One controller ---
Success.
Editing the dosboxScreamer.conf file (joysticktype=4axis and timed=false, to prevent calibration issues) and then running the setup.exe as described, worked just fine. I couldn't assign steering inputs to the dpad, and the controller itself only works during actual races (menus still require keyboard commands), but I'm inclined to assume it's all normal.

--- random freezing/crashing during races ---
Fixed (I'll take some more time to test the game, and report if needed).
First, I investigated the issue a bit further and I found out it's the original game to be notoriously unstable in SVGA. Once again, editing the dosboxScreamer.conf file (by setting the CPU core from auto to normal) seemed to help, but then Screamer ran just like it probably did, back then, at higher resolutions... Which means awfully choppy, at a blistering 20 or so fps. Not my cup of tea, tbh. :)
Since I like to play these old DOS/Win95 classics on a 1440x900px window anyway - to keep their original 320x200px resolution at 4.5x, and the wider aspect ratio intact, without scaling artifacts - I went on and edited the dosboxScreamer_single.conf file, changing startH.exe into startL.exe (to launch the game in VGA mode, instead of SVGA). Even though it's much blockier, I still find the standard VGA very pleasing, not to mention both the frame rate and speed are now spot on. Should anyone else want to test my video settings, I also suggest to change scaler=none and aspect=false, to get a sharp, pixel perfect image.
Finally, turning on double buffering (fulldouble=true) got rid of any noticeable screen tearing.

All that said though, I'm still open to suggestions, to further improve my DOSBox experience!
Post edited June 16, 2019 by Galdelico
avatar
Galdelico: Apologies for reviving a months old discussion, but I thought to start from here, first, instead of posting a new thread.

I'm new to GOG and to PC gaming in general (I've been a console gamer forever though, and I'm still into retrogaming, on there). :)

This is my setup:
- MSI GS63 Stealth 8RE gaming laptop (i7, 16GB, GTX1060 6GB)
- AOC 1080p 144hz 25" monitor
- XBOX One controller
- Windows 10 Home Edition

I tried OP's guide in order to make the game more stable - it ran pretty well out of the box, with default options and SVGA, but of course I got no controller support, and random freezes during the first couple of races.

I thought to recap my current situation on here too:

--- XBOX One controller ---
Success.
Editing the dosboxScreamer.conf file (joysticktype=4axis and timed=false, to prevent calibration issues) and then running the setup.exe as described, worked just fine. I couldn't assign steering inputs to the dpad, and the controller itself only works during actual races (menus still require keyboard commands), but I'm inclined to assume it's all normal.

--- random freezing/crashing during races ---
Fixed (I'll take some more time to test the game, and report if needed).
First, I investigated the issue a bit further and I found out it's the original game to be notoriously unstable in SVGA. Once again, editing the dosboxScreamer.conf file (by setting the CPU core from auto to normal) seemed to help, but then Screamer ran just like it probably did, back then, at higher resolutions... Which means awfully choppy, at a blistering 20 or so fps. Not my cup of tea, tbh. :)
Since I like to play these old DOS/Win95 classics on a 1440x900px window anyway - to keep their original 320x200px resolution at 4.5x, and the wider aspect ratio intact, without scaling artifacts - I went on and edited the dosboxScreamer_single.conf file, changing startH.exe into startL.exe (to launch the game in VGA mode, instead of SVGA). Even though it's much blockier, I still find the standard VGA very pleasing, not to mention both the frame rate and speed are now spot on. Should anyone else want to test my video settings, I also suggest to change scaler=none and aspect=false, to get a sharp, pixel perfect image.
Finally, turning on double buffering (fulldouble=true) got rid of any noticeable screen tearing.

All that said though, I'm still open to suggestions, to further improve my DOSBox experience!
Thank you for this! I tried your setup and it worked flawlessly! I also tried another config, changing only fulldouble=true, aspect=false and memsize=32 (it was 16 by default). It runs full speed even with a scaler! No more crashes too!
avatar
PantsuJo: Thank you for this! I tried your setup and it worked flawlessly! I also tried another config, changing only fulldouble=true, aspect=false and memsize=32 (it was 16 by default). It runs full speed even with a scaler! No more crashes too!
Ciao! ^_-

I tweaked the game a bit further - more than I like to admit XD but I love Screamer... - so I'll update my previous post.

[sdl]
fullscreen=true
fulldouble=true
fullresolution=desktop
windowresolution=original
output=ddraw
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper-0.74-2.map
usescancodes=true

[dosbox]
language=
machine=svga_s3
captures=capture
memsize=63

[render]
frameskip=0
aspect=false
scaler=none

[cpu]
core=auto
cputype=auto
cycles=150000
cycleup=1000
cycledown=1000

These are my current settings in the dosboxScreamer.conf file, and they run the game as close to the original as I can possibly remember. Oh, and one last thing, I also created a custom resolution - under NVidia Control Panel - to set my monitor to 1920x1080 at 70hz (actual refresh rate of the majority of DOS games). I'm not even sure it's needed, but I can't see that causing any issue, so for now I swith to that profile every time I want to play some Screamer (I'll be sure to run more tests with the other DOS games I own here on GOG).

Alla prossima! ^_-
avatar
PantsuJo: Thank you for this! I tried your setup and it worked flawlessly! I also tried another config, changing only fulldouble=true, aspect=false and memsize=32 (it was 16 by default). It runs full speed even with a scaler! No more crashes too!
avatar
Galdelico: Ciao! ^_-

I tweaked the game a bit further - more than I like to admit XD but I love Screamer... - so I'll update my previous post.

[sdl]
fullscreen=true
fulldouble=true
fullresolution=desktop
windowresolution=original
output=ddraw
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper-0.74-2.map
usescancodes=true

[dosbox]
language=
machine=svga_s3
captures=capture
memsize=63

[render]
frameskip=0
aspect=false
scaler=none

[cpu]
core=auto
cputype=auto
cycles=150000
cycleup=1000
cycledown=1000

These are my current settings in the dosboxScreamer.conf file, and they run the game as close to the original as I can possibly remember. Oh, and one last thing, I also created a custom resolution - under NVidia Control Panel - to set my monitor to 1920x1080 at 70hz (actual refresh rate of the majority of DOS games). I'm not even sure it's needed, but I can't see that causing any issue, so for now I swith to that profile every time I want to play some Screamer (I'll be sure to run more tests with the other DOS games I own here on GOG).

Alla prossima! ^_-
Fantastico! Grazie mille! :D

(P.S.: non avevo notato che eri italiano lol, sorry! Thanks ancora!)
Post edited February 17, 2020 by PantsuJo