for speed - better read dosbox's manual
btw i noticed that you can use 6 buttons in this game - second stick left and up are buttons 5 and 6 😀
Look at the dates of those compat list comments, they're ancient. Just play around with the cycles settings until you find the "sweet spot". You can change cycles while DOSBox is running, see the DOSBox readme for instructions.
On my Fightpad the controls are like Street Fighter IV. Just kicks and punches are a little bit messed, like I said before. I managed to fix this, so I got my Fight Pad working like in SF4. Fight Pad has 6 buttons and 2 shoulders, layout is the same as good old Mega Drive controllers, except that the buttons are 6 and not just 3.
So the reason my Logitech had only 2 working buttons might be the analog sticks, but I don't care about that anymore - Fight Pad is a hundred times better anyway.
@Addict: Yeah, I did that a few times and changed standard cycles to 6500. I didn't find the sweet spot yet, only the spot where the game begins to run smooth but unplayable fast.
Oh, and next time read the effing game readme!
When selecting controllers, remember that only one 6 button or 4 button pad can be connected to a PC at any time. If you try to […]
When selecting controllers, remember that only one 6 button or
4 button pad can be connected to a PC at any time. If you try
to select two of these controllers, the game will revert one
back to keyboard.
I didn't ever try to select two controllers ingame. Like I said before I connected only one controller in the beginning and it didn't work.
but you had two controllers connected to the pc. if you disconnect fightpad and connect the other one it should work fine too
or just set 4axis in dosbox's configuration, so only one will be used
Mate, I don't need help with it anymore. And no, when I tried the Logitech it was the only controller connected to my PC. I tried multiple solutions, not only the one you see in the log I posted. Just leave it as it is. Also, if I can choose between FightPad and Logitech, I'll always choose the FightPad. It was made for fighting games.
Thanks again. I'm going to enjoy some SSF2T now. IF I can get this damn thing to run smoothly. Changing cycles only makes it worse.
wrote:
you can also select what speed you want before first fight
I know the game and what it features, the ability to choose game speed before you start a fight is gameplay related, it has nothing to do with technical problems I am encountering.
runs fine here with for example 20000 cycles, core dynamic
Tried the same settings and I'm having freezes, lag and sound issues with it.
What scaler did you use?
Maybe it's my hardware. What about your specs?
wrote:
I followed your tutorial but unfortunately it didn't help me out in this case. I tried everything except running sound with GUS, because I didn't understand how to set it up. Can you explain it to me? When I chose GUS manually, I didn't have any sound at all.
No matter what I do, it keeps freezing, lagging or stuttering from time to time, whatever you wish to call it. Long loading times and pushing up cycles only makes it worse.
enclose your new config file
and how much cpu is used by it now?
# This is the configurationfile for DOSBox 0.73. # Lines starting with a # are commentlines. # They are used to (briefly) docume […]
# 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=surface
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=none[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=dynamic
cputype=auto
cycles=fixed 6500
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=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.
# 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.
mount c c:\progra~1
mount d d:\ -t cdrom
c:
cd gametek
cd ssf2t
I changed most options back to default, because performance didn't improve the slightest bit. 20.000 cycles are like 3% CPU load. I can only tell you again, if I push cycles to a higher count it gets even worse, even though my CPU has more than enough power left.
I have another idea: Maybe it is the CD causing problems? I mean it's a pretty old game, used cd and there are signs of use on it. No big scratches or anything...it's just an idea.
yeah, try making a cue/bin and imgmount it
memsize=31
i noticed game creates a swapfile on hdd when memsize=16
rate=44100
blocksize=1024
prebuffer=20
and all other rates to 44100 too
these settings are generally better and will be in next dosbox version as default
try disconnecting all joysticks just in case
also don't test game with 6500 cycles as it is just very slow with it. use at least 20000
Do other games work properly?
Okay, got it. Finally I can enjoy smooth gameplay. 😀
Looks like it was the CD OR my drive (my bet goes on the drive), it is an older one since my "new" dvdr died a few weeks ago. I could install the game without problems. Lucky enough I didn't pay more than 5 bucks, it was worth it to add it to my SF collection.
Thanks mate. Now I need to get back to configuring my controller. It is messed somehow, if I press RB button in WinXP configuration the 6 flashes, but when I press RT button Z-axis flashes and it should be the 5 flashing.
Since this muthafucka is pretty picky with dosbox settings, here are after many trials and errors, my config settings to run the game in the best way, surely this can be useful for someone:
get dosbox 0.74
use surface output, use auto or dynamic come, use auto cycles (it will go to max when you start the game) or (if you have problems), select =+ 20000
IMPORTANT: install the game patch someone mentioned in the previous posts!!! (this will enable some usefull commands like midi or nocdstatus, and fix numerous bugs).
Start the game using "ssf2t NOCDSTATUS" (believe me, it will run way better)
I suggest to use a cd image in bin+cue format and imgmount command, sometimes with physical cd + mount command there are small cd-seek pauses. Note: if you encounter random audio interruptions or static sound in music during play, add -ioctl_mci to your mount command.
Oh..and use "frame lock ON" in the game options menu.
peace
