«

[Aldaraia]

Nah, I only got a 2.4ghz single-core processor, so I don't see the CPU being the problem. I usually have to crank the cycles up to about 5000 to get the game going in good playable speed, though the confg does mention that too high of a speed causes lag, I dunno if this lag is capable of causing the keyboard to become unresponsive until I alt-tab back to DOSBOX.

Currently I've got the output mode set to 'ddraw' with the aspect set to 'true', the scaler being set to 'supereagle forced'. Both the cores and cycles are set to auto as well. I suppose I can lower the cycles below the default 3000 to see what good it will do.

EDIT: CPU spikes that cause DOSBOX to momentarily lag, should these lags ever be capable of temporarily disabling keyboard input? I've decided to give DNII another try and set the cycles to 4000 and I got a wonderful 20 minutes of playtime in before the lag happened again. I'm guessing somewhere around 3500-4000 is the sweet spot for this game if the cycles are to blame. Should DOSBOX usually be ran without any other programs running?

[The Fifth Horseman]

Originally Posted by Aldaraia

Nah, I only got a 2.4ghz single-core processor, so I don't see the CPU being the problem. I usually have to crank the cycles up to about 5000 to get the game going in good playable speed, though the confg does mention that too high of a speed causes lag, I dunno if this lag is capable of causing the keyboard to become unresponsive until I alt-tab back to DOSBOX.

Unlikely.

EDIT: CPU spikes that cause DOSBOX to momentarily lag, should these lags ever be capable of temporarily disabling keyboard input?

I don't think they should.

I'm guessing somewhere around 3500-4000 is the sweet spot for this game if the cycles are to blame.

The cycles aren't to blame.

Should DOSBOX usually be ran without any other programs running?

Depend on what programs those are. Any more resource (and CPU) demanding ones should be closed down before starting DOSBox. If you are experiencing issues, that's one of the first things to check. Another is scanning your system for malware. Another yet is checking if the issue happens with a different keyboard (just to make sure).

[Aldaraia]

Originally Posted by The Fifth Horseman

Unlikely.
I don't think they should.The cycles aren't to blame. Depend on what programs those are. Any more resource (and CPU) demanding ones should be closed down before starting DOSBox. If you are experiencing issues, that's one of the first things to check. Another is scanning your system for malware. Another yet is checking if the issue happens with a different keyboard (just to make sure).

I think it just might be the game itself. After playing Masters of Orion for awhile, I haven't encountered the problem once. It probably just depends on the type of game apparently.

[Scatty]

Originally Posted by Aldaraia

Nah, I only got a 2.4ghz single-core processor, so I don't see the CPU being the problem. I usually have to crank the cycles up to about 5000 to get the game going in good playable speed, though the confg does mention that too high of a speed causes lag, I dunno if this lag is capable of causing the keyboard to become unresponsive until I alt-tab back to DOSBOX.

Currently I've got the output mode set to 'ddraw' with the aspect set to 'true', the scaler being set to 'supereagle forced'. Both the cores and cycles are set to auto as well. I suppose I can lower the cycles below the default 3000 to see what good it will do.

EDIT: CPU spikes that cause DOSBOX to momentarily lag, should these lags ever be capable of temporarily disabling keyboard input? I've decided to give DNII another try and set the cycles to 4000 and I got a wonderful 20 minutes of playtime in before the lag happened again. I'm guessing somewhere around 3500-4000 is the sweet spot for this game if the cycles are to blame. Should DOSBOX usually be ran without any other programs running?

Set the CPU cycles to 10.000 or 15.000 instead of auto, with the processor you mentioned it should be no problem, and the option auto not always works well. What you need is more cycles, not less than 3000. Also try setting the core to core=dynamic, with auto it happens to be set to normal, and that is slower.
Vga isn't a valid option for machine, try vgaonly or svga_s3 as suggested by DosBox itself.

See if all that above will be of any help. Good luck.

[Smiling Spectre]

Hmm, I seen exactly the same several times... but it was long time ago... but I don't use Official builds anymore, so maybe that's really "official" bug...

But also several times it was totally different problem. Lost focus. If any application can draw focus to itself from DOSBox, it will "stuck" in last "remembered" position, until you'll return to it.

And, of course, "pointing" software, like MoO, will be much less affected by it then "moving" like Duke. Just because "stuck" pointer will do nothing in MoO, and you'll release it in next click.

Did you tried de-capture mouse with Alt+F10 instead Windows key? If it is capture issue it would help.

Clicking left mouse button theoretically would work too, but I never tried it.