«

[Goodguy3]

I got .70, installed it, and ti works fine. but when I try to increase teh CPU sycles more than 5000 (to run Wing Commander at a good speed) ,the mouse pointer just scrolls slowly to the bottom right corner of teh screen..makeign it impossible to fly.

Help me?

[Japo]

In 0.70 you don't need to adjust the cycles, it's done automatically. They're set to 3,000 at the DOS command prompt but they're changed as necessary if you don't press Ctrl+F11 or Ctrl+F12 and the game should play all right. If you still have problems edit dosbox.conf and change "cycles=auto" with the number you need, but you should try the auto mode before, it should work, it works for Wing Commander - Privateer.

[The Fifth Horseman]

Core=Auto and Cycles=auto means that for non-protected mode games the cycles will be set to 3000 with Normal core.

While sufficient for most games, this will not work for _all_ of them.

Change Core to Dynamic, change starting cycles to 5000 and then run the game.

[Icewolf]

QUOTE(the_fifth_horseman @ Mar 5 2007, 01:24 PM) [snapback]281940[/snapback]

While sufficient for most games, this will not work for _all_ of them.[/b]

Would you still recommend using the AUTO-settings?

[The Fifth Horseman]

Depends. Myself, I have core set to dynamic per default and cycles on 10000 with step set to 1000 for increasing or decreasing them.

QUOTE(Goodguy3 @ Mar 4 2007, 11:52 PM) [snapback]281877[/snapback]

I got .70, installed it, and ti works fine. but when I try to increase teh CPU sycles more than 5000 (to run Wing Commander at a good speed) ,the mouse pointer just scrolls slowly to the bottom right corner of teh screen..makeign it impossible to fly.

Help me?
[/b]

The solution is to set timed=false in dosbox.conf.

[Icewolf]

QUOTE(Anno @ Mar 21 2007, 07:40 PM) [snapback]284464[/snapback]

The solution is to set timed=false in dosbox.conf.[/b]

What does that (technically) do?

[Data]

changes joystick control offered to the game.

QUOTE(Icewolf @ Mar 22 2007, 09:17 AM) [snapback]284519[/snapback]

QUOTE(Anno @ Mar 21 2007, 07:40 PM) [snapback]284464[/snapback]

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=.