Fixing mouse lag in doxbox with Blood

[Metal Boss]

I got blood running fairly well in Dosbox I am just wondering though, how do I fix the dreadful mouse lag? I tried raising the sensitivity in the dosbox config, blood SETUP and the ingame options to no avail.

[ShadeEX]

What resolution are you running it at..

And what is your DOSBox settings for Blood ?

Also what mouse do you have USB / PS2 ??

[Daedolon]

The mouse lag in Blood is pretty much always caused by low framerates. Since DosBox is an emulator, you might get problems at 640x480 even with a dualcore system.

Suggested settings for any raycaster game for DosBox are core=dynamic and cycles=auto. If that doesn't solve the problem, try the native 320x200 mode before using any of the higher VESA modes.

[avatar_58]

Should not be any lag. How many cycles do you have set? Try setting them to "auto" and see if it helps. Or you could try lowering the priority to "normal" if it's set to high. This fixed the keyboard lag I had in Wolf3D.

[Damien_Azreal]

I've never experienced any mouse lag in Blood through DOSBox. The latest versions of DOS Box make running Blood great, game manages to play smooth at 1024*768.

On older releases of DOSBox I had mouse lag and performance problems.

[avatar_58]

I've never experienced any mouse lag in Blood through DOSBox. The latest versions of DOS Box make running Blood great, game manages to play smooth at 1024*768.

On older releases of DOSBox I had mouse lag and performance problems.

Depends on your PC though of course. Though I think with a modest CPU 640x480 should be no problem.

[SniperZERO]

Blood runs horrible on my computer using DOSBox, so I just use my Windows 98 machines.

[Metal Boss]

Im using dosbox 0.72

USB mouse by the way


Here is my current dosbox config

fullscreen=false
fulldouble=false
fullresolution=original
windowresolution=800x600
output=opengl
autolock=true
sensitivity=1000
waitonerror=true
priority=higher,normal
mapperfile=mapper.txt
usescancodes=true

language=
machine=vga
captures=capture
memsize=16

frameskip=1
aspect=false
scaler=normalx3

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


It feels like Im controlling a tank in this game.

[avatar_58]

It feels like Im controlling a tank in this game.

Wait - you do realize Blood doesn't have modern 1:1 mouse movement right? Have you played it before natively on an old PC? Eduke and it's kin are vastly different than the way the Build engine originally felt with the mouse+kb.

I'm just curious if you know this.

[Metal Boss]

I do, however I don't remember this amount of delay in the game. I have played Duke3D, Doom, & shadow warrior on this and they all seemed to respond alot better but maybe thats because I was using ports to play them and not dos box.

[avatar_58]

The ports use modern mouse movement, nowhere near the same. Try running Duke in dosbox and see if it's the same deal.

[Damien_Azreal]

Wait - you do realize Blood doesn't have modern 1:1 mouse movement right? Have you played it before natively on an old PC? Eduke and it's kin are vastly different than the way the Build engine originally felt with the mouse+kb.

I'm just curious if you know this.

Yeah, Blood's mouse movement won't feel precise or fast. It will feel a little sluggish on it's own.. but that's how it's always been.

Blood was designed to be played with a keyboard, mouse support was there... but it was still long before gamers were using mouse+keyboard specifically.

[Metal Boss]

I must be rusty in that case. Been a LONG time since I played it. Anyways, after messing around with all of the sensitivities now the game feels much better to control.

[Daedolon]

I got a mistake in my post anyway, I meant try cycles=max, that should make DosBox to play Blood as smooth as possible.

[avatar_58]

Yeah you have to think of mouse support as the same as turning with the keyboard and pressing page up/page down to look around. It's only marginally faster. If you adjust the sensitivity in the setup to make vertical/horizontal close to each other it's not bad, but it will never be as perfect as modern games are.

[Daedolon]

Also, remember that vertical looking is only a "hack" in the BUILD renderer, unlike Polymost.

[Qbix]

cycles=max and cycles=auto are identical for Blood.

output=opengl be sure to have decent opengl drivers. So not the ones distributed by microsoft.

[leilei]

It could even be an SDL related issue! Do you get mouse lag when you hold a key down and turn the mouse rather than just turning the mouse alone? If yes, then that's SDL screwing up at the input queues. There's nothing you can do about it except wait forever for a new SDL that fixes this horrible issue (it doesn't affect only DOSBox though)

If you have an ATI Radeon card, try also terminating ati2evxx processes. That'll help some input too