Mortal Kombat 1 & 2 scroll \ VOGONS

Mortal Kombat 1 & 2 scroll

Topic actions

Post a reply

First post, by theelf

Posted on 2016-06-15, 16:19

theelf Online

Rank Oldbie

Rank: Oldbie
Posts: 634
Joined: 2011-09-25, 19:39

Hi, im having problems to configure Mortal Kombat 1 and 2 (i did not test 3 or trilogy) in Dosbox 0.74

The scroll and framerate is very bad, not like in real DOS

I already tried

1 - CPU simple, normal, dynamic
2 - Cycles from 3000 to 50000, max, and auto
3 - Screen resolution with refresh rates from 60hz to 75hz, and original resolution
4 - Diferent memory configurations (8-24mb, xms, ems, etc)

My screen is a 14" CRT, and i tried custom resolutions from 60 to 75hz in increments of 1hz (61,62,63..74,75hz)

Nothing works, the game always feel slugish, not like real DOS

Any ideas?

Just for the record, is the only two games that give me problems. I have more than 800 games already perfect working in dosbox

Reply 1 of 7, by Jorpho

Posted on 2016-06-15, 17:07

Jorpho Offline

Rank l33t++

Rank: l33t++
Posts: 8168
Joined: 2003-02-14, 19:50
Location: Canada

theelf wrote:
The scroll and framerate is very bad, not like in real DOS

Are you sure the version you are trying to run is the same version you once ran in DOS?

According to Versions of Mortal Kombat (1) (DOS port) there are at least several different versions of MK1.

Reply 2 of 7, by theelf

Posted on 2016-06-15, 17:43

theelf Online

Rank Oldbie

Rank: Oldbie
Posts: 634
Joined: 2011-09-25, 19:39

Jorpho wrote:
theelf wrote:
The scroll and framerate is very bad, not like in real DOS
Are you sure the version you are trying to run is the same version you once ran in DOS?

According to Versions of Mortal Kombat (1) (DOS port) there are at least several different versions of MK1.

Thanks for reply

Yes, same version, in fact i have the DualCore PC with dosbox and the real 486 PC each other, is easy to compare

Reply 3 of 7, by Jorpho

Posted on 2016-06-15, 18:05

Jorpho Offline

Rank l33t++

Rank: l33t++
Posts: 8168
Joined: 2003-02-14, 19:50
Location: Canada

The only other thing I can think of is to change the machine type – maybe vesa_oldvbe or vesa_nolfb . A cputype of 486_slow or pentium_slow might be worth trying too.

If you want to do some experimenting, I notice GOG is selling MK 1+2+3 (they're the DOS versions) for two bucks at the moment.

Reply 4 of 7, by theelf

Posted on 2016-06-15, 18:53

theelf Online

Rank Oldbie

Rank: Oldbie
Posts: 634
Joined: 2011-09-25, 19:39

Jorpho wrote:
The only other thing I can think of is to change the machine type – maybe vesa_oldvbe or vesa_nolfb . A cputype of 486_slow or pentium_slow might be worth trying too.

If you want to do some experimenting, I notice GOG is selling MK 1+2+3 (they're the DOS versions) for two bucks at the moment.

Hi, thanks

Ok, i already tried all video and CPU options (vgaonly, vesa, 386, 486, etc) without luck. The only thing that make the game slightly better, is when i create a custom resolution of 320x200 at 140hz, the game is a little smoth, but still not like in the 486

Im out of ideas, but must be a refresh problem for sure

I checked too the GOG version... wow, what a disaster... here is the MK1 GOG config... not good at all, at least in a CRT screen, no idea TFT, i dont have any tft in home right now to test

1# This is the configurationfile for DOSBox 0.74. (Please use the latest version of DOSBox)
2# Lines starting with a # are commentlines and are ignored by DOSBox.
3# They are used to (briefly) document the effect of each option.
4
5[sdl]
6#       fullscreen: Start dosbox directly in fullscreen. (Press ALT-Enter to go back)
7#       fulldouble: Use double buffering in fullscreen. It can reduce screen flickering, but it can also result in a slow DOSBox.
8#   fullresolution: What resolution to use for fullscreen: original or fixed size (e.g. 1024x768).
9#                     Using your monitor's native resolution with aspect=true might give the best results.
10#                     If you end up with small window on a large screen, try an output different from surface.
11# windowresolution: Scale the window to this size IF the output device supports hardware scaling.
12#                     (output=surface does not!)
13#           output: What video system to use for output.
14#                   Possible values: surface, overlay, opengl, openglnb, ddraw.
15#         autolock: Mouse will automatically lock, if you click on the screen. (Press CTRL-F10 to unlock)
16#      sensitivity: Mouse sensitivity.
17#      waitonerror: Wait before closing the console if dosbox has an error.
18#         priority: Priority levels for dosbox. Second entry behind the comma is for when dosbox is not focused/minimized.
19#                     pause is only valid for the second entry.
20#                   Possible values: lowest, lower, normal, higher, highest, pause.
21#       mapperfile: File used to load/save the key/event mappings from. Resetmapper only works with the defaul value.
22#     usescancodes: Avoid usage of symkeys, might not work on all operating systems.
23
24fullscreen=true
25fulldouble=false
26fullresolution=original
27windowresolution=original
28output=overlay
29autolock=true
30sensitivity=100
31waitonerror=true
32priority=higher,normal
33mapperfile=mapper.txt
34usescancodes=true
35
36[dosbox]
37# language: Select another language file.
38#  machine: The type of machine tries to emulate.
39#           Possible values: hercules, cga, tandy, pcjr, ega, vgaonly, svga_s3, svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe.
40# captures: Directory where things like wave, midi, screenshot get captured.
41#  memsize: Amount of memory DOSBox has in megabytes.
42#             This value is best left at its default to avoid problems with some games,
43#             though few games might require a higher value.
44#             There is generally no speed advantage when raising this value.
45
46language=
47machine=svga_s3
48captures=capture
49memsize=16
50
51[render]
52# frameskip: How many frames DOSBox skips before drawing one.
53#    aspect: Do aspect correction, if your output method doesn't support scaling this can slow things down!.
54#    scaler: Scaler used to enlarge/enhance low resolution modes.
55#              If 'forced' is appended, then the scaler will be used even if the result might not be desired.
56#            Possible values: none, normal2x, normal3x, advmame2x, advmame3x, advinterp2x, advinterp3x, hq2x, hq3x, 2xsai, super2xsai, supereagle, tv2x, tv3x, rgb2x, rgb3x, scan2x, scan3x.
57
58frameskip=0
59aspect=false
60scaler=normal2x

…Show last 172 lines

61
62[cpu]
63#      core: CPU Core used in emulation. auto will switch to dynamic if available and appropriate.
64#            Possible values: auto, dynamic, normal, simple.
65#   cputype: CPU Type used in emulation. auto is the fastest choice.
66#            Possible values: auto, 386, 386_slow, 486_slow, pentium_slow, 386_prefetch.
67#    cycles: Amount of instructions DOSBox tries to emulate each millisecond.
68#            Setting this value too high results in sound dropouts and lags.
69#            Cycles can be set in 3 ways:
70#              'auto'          tries to guess what a game needs.
71#                              It usually works, but can fail for certain games.
72#              'fixed #number' will set a fixed amount of cycles. This is what you usually need if 'auto' fails.
73#                              (Example: fixed 4000).
74#              'max'           will allocate as much cycles as your computer is able to handle.
75#            
76#            Possible values: auto, fixed, max.
77#   cycleup: Amount of cycles to decrease/increase with keycombo.(CTRL-F11/CTRL-F12)
78# cycledown: Setting it lower than 100 will be a percentage.
79
80core=auto
81cputype=auto
82cycles=auto
83cycleup=1000
84cycledown=1000
85
86[mixer]
87#   nosound: Enable silent mode, sound is still emulated though.
88#      rate: Mixer sample rate, setting any device's rate higher than this will probably lower their sound quality.
89#            Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
90# blocksize: Mixer block size, larger blocks might help sound stuttering but sound will also be more lagged.
91#            Possible values: 1024, 2048, 4096, 8192, 512, 256.
92# prebuffer: How many milliseconds of data to keep on top of the blocksize.
93
94nosound=false
95rate=44100
96blocksize=1024
97prebuffer=20
98
99[midi]
100#     mpu401: Type of MPU-401 to emulate.
101#             Possible values: intelligent, uart, none.
102# mididevice: Device that will receive the MIDI data from MPU-401.
103#             Possible values: default, win32, alsa, oss, coreaudio, coremidi, none.
104# midiconfig: Special configuration options for the device driver. This is usually the id of the device you want to use.
105#               See the README/Manual for more details.
106
107mpu401=intelligent
108mididevice=default
109midiconfig=
110
111[sblaster]
112#  sbtype: Type of Soundblaster to emulate. gb is Gameblaster.
113#          Possible values: sb1, sb2, sbpro1, sbpro2, sb16, gb, none.
114#  sbbase: The IO address of the soundblaster.
115#          Possible values: 220, 240, 260, 280, 2a0, 2c0, 2e0, 300.
116#     irq: The IRQ number of the soundblaster.
117#          Possible values: 7, 5, 3, 9, 10, 11, 12.
118#     dma: The DMA number of the soundblaster.
119#          Possible values: 1, 5, 0, 3, 6, 7.
120#    hdma: The High DMA number of the soundblaster.
121#          Possible values: 1, 5, 0, 3, 6, 7.
122# sbmixer: Allow the soundblaster mixer to modify the DOSBox mixer.
123# oplmode: Type of OPL emulation. On 'auto' the mode is determined by sblaster type. All OPL modes are Adlib-compatible, except for 'cms'.
124#          Possible values: auto, cms, opl2, dualopl2, opl3, none.
125#  oplemu: Provider for the OPL emulation. compat might provide better quality (see oplrate as well).
126#          Possible values: default, compat, fast.
127# oplrate: Sample rate of OPL music emulation. Use 49716 for highest quality (set the mixer rate accordingly).
128#          Possible values: 44100, 49716, 48000, 32000, 22050, 16000, 11025, 8000.
129
130sbtype=sb16
131sbbase=220
132irq=7
133dma=1
134hdma=5
135sbmixer=true
136oplmode=auto
137oplemu=default
138oplrate=44100
139
140[gus]
141#      gus: Enable the Gravis Ultrasound emulation.
142#  gusrate: Sample rate of Ultrasound emulation.
143#           Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
144#  gusbase: The IO base address of the Gravis Ultrasound.
145#           Possible values: 240, 220, 260, 280, 2a0, 2c0, 2e0, 300.
146#   gusirq: The IRQ number of the Gravis Ultrasound.
147#           Possible values: 5, 3, 7, 9, 10, 11, 12.
148#   gusdma: The DMA channel of the Gravis Ultrasound.
149#           Possible values: 3, 0, 1, 5, 6, 7.
150# ultradir: Path to Ultrasound directory. In this directory
151#           there should be a MIDI directory that contains
152#           the patch files for GUS playback. Patch sets used
153#           with Timidity should work fine.
154
155gus=false
156gusrate=44100
157gusbase=240
158gusirq=5
159gusdma=3
160ultradir=C:\ULTRASND
161
162[speaker]
163# pcspeaker: Enable PC-Speaker emulation.
164#    pcrate: Sample rate of the PC-Speaker sound generation.
165#            Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
166#     tandy: Enable Tandy Sound System emulation. For 'auto', emulation is present only if machine is set to 'tandy'.
167#            Possible values: auto, on, off.
168# tandyrate: Sample rate of the Tandy 3-Voice generation.
169#            Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
170#    disney: Enable Disney Sound Source emulation. (Covox Voice Master and Speech Thing compatible).
171
172pcspeaker=true
173pcrate=44100
174tandy=auto
175tandyrate=44100
176disney=true
177
178[joystick]
179# joysticktype: Type of joystick to emulate: auto (default), none,
180#               2axis (supports two joysticks),
181#               4axis (supports one joystick, first joystick used),
182#               4axis_2 (supports one joystick, second joystick used),
183#               fcs (Thrustmaster), ch (CH Flightstick).
184#               none disables joystick emulation.
185#               auto chooses emulation depending on real joystick(s).
186#               (Remember to reset dosbox's mapperfile if you saved it earlier)
187#               Possible values: auto, 2axis, 4axis, 4axis_2, fcs, ch, none.
188#        timed: enable timed intervals for axis. Experiment with this option, if your joystick drifts (away).
189#     autofire: continuously fires as long as you keep the button pressed.
190#       swap34: swap the 3rd and the 4th axis. can be useful for certain joysticks.
191#   buttonwrap: enable button wrapping at the number of emulated buttons.
192
193joysticktype=auto
194timed=true
195autofire=false
196swap34=false
197buttonwrap=false
198
199[serial]
200# serial1: set type of device connected to com port.
201#          Can be disabled, dummy, modem, nullmodem, directserial.
202#          Additional parameters must be in the same line in the form of
203#          parameter:value. Parameter for all types is irq (optional).
204#          for directserial: realport (required), rxdelay (optional).
205#                           (realport:COM1 realport:ttyS0).
206#          for modem: listenport (optional).
207#          for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
208#                         transparent, port, inhsocket (all optional).
209#          Example: serial1=modem listenport:5000
210#          Possible values: dummy, disabled, modem, nullmodem, directserial.
211# serial2: see serial1
212#          Possible values: dummy, disabled, modem, nullmodem, directserial.
213# serial3: see serial1
214#          Possible values: dummy, disabled, modem, nullmodem, directserial.
215# serial4: see serial1
216#          Possible values: dummy, disabled, modem, nullmodem, directserial.
217
218serial1=dummy
219serial2=dummy
220serial3=disabled
221serial4=disabled
222
223[dos]
224#            xms: Enable XMS support.
225#            ems: Enable EMS support.
226#            umb: Enable UMB support.
227# keyboardlayout: Language code of the keyboard layout (or none).
228
229xms=true
230ems=true
231umb=true
232keyboardlayout=auto

Reply 5 of 7, by Jorpho

Posted on 2016-06-15, 19:24

Jorpho Offline

Rank l33t++

Rank: l33t++
Posts: 8168
Joined: 2003-02-14, 19:50
Location: Canada

I've never heard of anyone trying to fix scrolling and framerate issues in DOSBox by changing the refresh rate or custom resolution. I wouldn't expect a CRT or TFT to make any difference either. Whatever the problem is, it's probably something else.

Are you saying the GOG version has exactly the same problems? The config you posted appears to be the DOSBox default.

Reply 6 of 7, by theelf

Posted on 2016-06-15, 21:07

theelf Online

Rank Oldbie

Rank: Oldbie
Posts: 634
Joined: 2011-09-25, 19:39

Jorpho wrote:
I've never heard of anyone trying to fix scrolling and framerate issues in DOSBox by changing the refresh rate or custom resolution. I wouldn't expect a CRT or TFT to make any difference either. Whatever the problem is, it's probably something else.

Are you saying the GOG version has exactly the same problems? The config you posted appears to be the DOSBox default.

From what i know, maybe Im wrong, VGA DOS games in 320x200, run at 69.9Hz. for sure must be a lot of games that use different refresh rate, but it seems 69.9 is a common value, at least for now all games i tested that are 320x200 use 69.9

640x480 and 320x240 games use 59.8Hz, at least, looks like the correct value comparing DOSbox and my 486 side by side

if MK1 and Mk2 are standar VGA games, they will run at 69.9Hz, like all other games, but the scroll is not good, then i think or is a dosbox problem, a refresh problem, or a config problem

GOG MK compilation configuration is the one i post, the name is "dosboxMortalKombat.conf" there is 2 more settings, but just for ipx connection

Yes, GOG Mk compilation out of the box, have more problems that my config, a lot of tearing

About custom resolutions and refresh rate, yes, I found is a good way to fix some things, for example PC98 ports to DOS, that original games are 640x400 at 56.4hz, but DOS ports are 640x480x60Hz. I realize that something was bad when playing some PC98 ports, because i have a real PC98

In this case, i dont want to fix anythong using 320x200@140Hz, just test a higher refresrh rate, to check if something change

Reply 7 of 7, by Yesterplay80

Posted on 2016-06-17, 10:15

Yesterplay80 Offline

Rank Oldbie

Rank: Oldbie
Posts: 540
Joined: 2016-02-23, 11:02
Location: Germany

I already have MK1-3 on Steam, but just out of curiosity (and to support GOG), I spent the insane amount of 1.39€ on GOG for all 3 games to check if they make any trouble. So far I only tested MK1, as always I copied the game (in this case the MK1 folder) to another place and set it up with my SVN build of DOSBox as I set up all my games. And it runs flawlessly, without having to meddle around with resolutions, timings, cycles or anything else.

Here is my config, maybe it is of some help for you:

Filename: MK1.conf
File size: 11.41 KiB
Downloads: 128 downloads
File license: Fair use/fair dealing exception

Are you using a frontend for DOSBox? Or did you actually change the resolution of your Windows in the screenshot up there? Have you tried a recent version of DOSBox? If not, please do so, you won't regret it. You can find one in my signature.

My full-featured DOSBox SVN builds for Windows & Linux: Vanilla DOSBox and DOSBox ECE (Google Drive Mirror)

Go to top of page Go to top of page

Back to DOSBox Games/Apps

Main menu

Common searches