I fixed this a few days ago.
probably cvs at sourceforge is still lagged a bit.

Hmmm, still seems to be doing it, even with the 0.61 release of DOSBox. It mentions the same symptoms in the Crusader readme and they say it's something to do with a programmable keyboard (which I dont have).

well inside dosbox you might have 😉

Btw what cycles are you playing it ?
Is your pc maxed out then ?

I'm playing it at 13500 cycles with a frameskip of 3 (DOSBox's frameskip not the in-game one). My CPU is an Athlon XP 3000+ running at the standard 2.167Ghz. It runs pretty sweet using the "normal" core and "surface" output. Everything is smooth apart from the movies. They are all choppy and the sound stutters, but who cares about them 😁
I'm using the mouse in the mean time until the keyboard issue is resolved which isnt too bad once you get used to it 😜

I've never been able to play it at those high speeds 😀 So no way I can reproduce the "errors" I hope it got better though. (since it was first playable in the cvs)
I noticed that pressing esc fixes the key stuck (discoverred that when I though I fixed the keystuck problem(

Unfortunately that's not the case here. Escape key doesnt have any effect. I ran the debug and noticed the following errors when the keyboard craps out:

-1227121953: KEYBOARD:Unhandled SDL keysym 19
-1227121953: KEYBOARD:Unhandled SDL keysym 19
-1227121953: KEYBOARD:Unhandled SDL keysym 317
-1227121953: KEYBOARD:Unhandled SDL keysym 317
-1227121953: KEYBOARD:Unhandled SDL keysym 317
-1227121953: KEYBOARD:Unhandled SDL keysym 317

Well those are the input error for dosbox.
So dosbox doesn't know which key you pressed....

Do you have an american keyboard layout ?
(dosbox can only (properly) handle that one.)

Pressing caps lock/num lock/scroll lock breaks the keyboard in lots of games. This could be one of them.

It's a Standard 101/102-Key or Microsoft Natural PS/2 Keyboard. I'm sure the keyboard layout is US standard. I always choose that due to compatibility reasons. I never use scroll lock, caps lock or num lock during Crusader so I dont see how they could be a part of the issue. I just replaced my keyboard with a more generic one... Totally no frills 😁, still has the same results tho. I'll keep ya posted if I make any progress.

Yeah, the keyboard layout was on US... I tried changing it to US - International to see if that would make any difference but no luck unfortunately. 😕

I seem to remeber having this problem many years ago in DOS 6.22 on my pentium 75 (or was my Pentium 133). I just used to tap the arrow key that appeared to be stuck down. The key itself wasnt stuck, but it used to break the spining around cycle. I think its just a Crusader thing rather than DOS box

I dont think that is correct... The keyboard becomes completely unresponsive, tapping the keys makes no difference. I played crusader back in the the good old days of DOS also and never had this issue.

Well we can look at it in the near future as the cvs is capable of playing crusader again.

That would be awesome Qbix... At the moment the current CVS doesnt have correct aspect ratio for both the crusaders (as of 13/10/04). I tried changing aspect ratio to "true" in the config and setting the fixed width and height but that didnt seem to make much of a difference. It appears as if the screen is twice as large as it should be.

The same problem with the keyboard becoming unresponsive, but the mouse still working just occured for me. It happened shortly after I pressed F1 for the ingame help. I forgot to write down the exact error msg, it was something along the lines of "SDL spin lock failure." If the error occurs again, I will post it here.

p.s. I just found dosBox today, and I have to say, THANK YOU, to the guys that wrote this! I have been looking for something like this forever to be able to go back and play the games I bought when i was a kid! You guys rock.

I have upgraded to a new PC (very similar specs to mr_zen's) and continue to have the keyboard problem he mentions. after 5-10 minutes of playing the keyboard becomes completly unresponsive (The mouse however, continues to work). No errors are (such as the SDL keyboard ones) are being spewed to the console

wait till next version

I have the same sticky keys prob under Remorse - so do a few guys over at the DOSGAMES.COM forum. All I can do is shut the game down and start again. The clock cycles doesn't seem to have any effect as I've had them high and low and still get the prob. I have a standard keyboard and it's running on UK English.....

DOSbox is awesome though. Nice piece of coding - well done good sirs!

well 0.62 should have that sticky key bug fixed.