Question on performance

[Haldurson]

I had MoO 1 on my previous PC (purchased from Gog.com) -- I never got around to installing it when I upgraded to my current computer, because I wasn't really playing it a lot. I just downloaded this steam version, and it seems to run far more sluggishly on my new, upgraded computer than it did on my old one (when I was running it without Steam). Does anyone know of any tweaks to settings or config files that can help me juice up the performance a tad?

[andychow1234]

you need to edit the dosbox config files so it'll run faster.

locate dosboxmoo1.conf in your moo1 directory. Open the file with notepad/textpad and ticker with the CPU section. Change the 'auto' values into numerical ones. There's comments in the file that describes it.

[garoo]

You'd think they'd fix that by default.

[Haldurson]

Originally posted by andychow1234:

you need to edit the dosbox config files so it'll run faster.

locate dosboxmoo1.conf in your moo1 directory. Open the file with notepad/textpad and ticker with the CPU section. Change the 'auto' values into numerical ones. There's comments in the file that describes it.

The comments don't actually give suggestions of actual numbers. This is what is there:
[cpu]
# core: CPU Core used in emulation. auto will switch to dynamic if available and appropriate.
# Possible values: auto, dynamic, normal, simple.
# cputype: CPU Type used in emulation. auto is the fastest choice.
# Possible values: auto, 386, 386_slow, 486_slow, pentium_slow, 386_prefetch.
# cycles: Amount of instructions DOSBox tries to emulate each millisecond.
# Setting this value too high results in sound dropouts and lags.
# Cycles can be set in 3 ways:
# 'auto' tries to guess what a game needs.
# It usually works, but can fail for certain games.
# 'fixed #number' will set a fixed amount of cycles. This is what you usually need if 'auto' fails.
# (Example: fixed 4000).
# 'max' will allocate as much cycles as your computer is able to handle.
#
# Possible values: auto, fixed, max.
# cycleup: Amount of cycles to decrease/increase with keycombo.(CTRL-F11/CTRL-F12)
# cycledown: Setting it lower than 100 will be a percentage.

According to the documentation here,Auto is fastest for cputype (which is what its set to). I'm clueless as to the 'correct' number to use for cycles (the only thing under CPU, other than Cycleup and Cycledown, which DOES give the option to enter numbers.

I'm going to try max instead, and see how that goes. Thanks for, at least, pointing me in the right direction.

/edit Max seems to work just fine for me. Thank you! The lag is gone.