QUOTE(Icewolf @ Mar 22 2007, 09:17 AM) [snapback]284519[/snapback]
Quote:
|
QUOTE(Anno @ Mar 21 2007, 07:40 PM) [snapback]284464[/snapback]
|
Quote:
|
The solution is to set timed=false in dosbox.conf.[/b]
|
What does that (technically) do?
[/b][/quote]
Different games can go different approaches of reading the joystick position.
The general porblem is real hardware did not change the CPU speed at runtime, DOSBox however does that with cycles=auto or when you change speed manually. Most games need fixed speed for their joystick routines, a few can handle different speeds.
The DOSBox versions before 0.70 have a simplified (kind of hack) joystick emulation that works speed independent with the games that require fixed speeds. However it causes problems with the other type of game and that's why timed=true was added. It's a more realistic implementation but is speed dependent in most games.
timed=false should be the best setting for most games.
timed=true is for Wing Commander Armada, Wing Commander 3, and probably other later Origin titles, but not the ealier like WC1/2 and Privateer.
Try it as well if the joystick doesn't work properly with timed=false.
You have to recalibrate in the game after changing timed=.