Posted December 16, 2014
high rated
A quick note for those with collision issues:
Firstly, changing cycles does almost nothing to fix collision. You need to slow the game right the way down to the 486 era and that means a stupidly low number of cycles. Emulating older CPUs can be done in DOSbox 0.74 and later, so make sure that's the version you have, then go into the dosboxShatteredSteel.conf file and make the changes to the following:
Change the line that reads "core=dynamic" to "core=normal."
Under core=normal add a new line that reads "cputype=486_slow"
To extrapolate, your [cpu] options should look similar to the code below, assuming you had a default config file to begin with:
[cpu]
# core -- CPU Core used in emulation: normal,simple,dynamic,auto.
# auto switches from normal to dynamic if appropriate.
# cycles -- Amount of instructions DOSBox tries to emulate each millisecond.
# Setting this value too high results in sound dropouts and lags.
# You can also let DOSBox guess the correct value by setting it to max.
# The default setting (auto) switches to max if appropriate.
# cycleup -- Amount of cycles to increase/decrease with keycombo.
# cycledown Setting it lower than 100 will be a percentage.
core=normal
cputype=486_slow
cycles=auto
cycleup=1000
cycledown=1000
Cycles shouldn't really matter because the emulated CPU should be trapped to the performance of a slow Intel 486.
Afterwards, go into Launch Graphic Mode Setup and under basic settings change the "Graphic mode" option to read "Overlay". This was an earlier fix I tried that did less than I would have liked but it's late and for now the game is running fairly smooth on an i5 750 @ 2.66ghz. I'm suggesting you make the change as well so that we both try the same thing on different systems, which should benchmark how effective the fix actually is...
These are the settings I changed so if you good folks would like to try them and post your results in the forums, please feel free, ideally on this thread so we can get some idea of how effective the changes are, but for me collision detection has been very solid since the tweaks and I would experiment more but it's 1am here and I have an early start.
So tired...
Firstly, changing cycles does almost nothing to fix collision. You need to slow the game right the way down to the 486 era and that means a stupidly low number of cycles. Emulating older CPUs can be done in DOSbox 0.74 and later, so make sure that's the version you have, then go into the dosboxShatteredSteel.conf file and make the changes to the following:
Change the line that reads "core=dynamic" to "core=normal."
Under core=normal add a new line that reads "cputype=486_slow"
To extrapolate, your [cpu] options should look similar to the code below, assuming you had a default config file to begin with:
[cpu]
# core -- CPU Core used in emulation: normal,simple,dynamic,auto.
# auto switches from normal to dynamic if appropriate.
# cycles -- Amount of instructions DOSBox tries to emulate each millisecond.
# Setting this value too high results in sound dropouts and lags.
# You can also let DOSBox guess the correct value by setting it to max.
# The default setting (auto) switches to max if appropriate.
# cycleup -- Amount of cycles to increase/decrease with keycombo.
# cycledown Setting it lower than 100 will be a percentage.
core=normal
cputype=486_slow
cycles=auto
cycleup=1000
cycledown=1000
Cycles shouldn't really matter because the emulated CPU should be trapped to the performance of a slow Intel 486.
Afterwards, go into Launch Graphic Mode Setup and under basic settings change the "Graphic mode" option to read "Overlay". This was an earlier fix I tried that did less than I would have liked but it's late and for now the game is running fairly smooth on an i5 750 @ 2.66ghz. I'm suggesting you make the change as well so that we both try the same thing on different systems, which should benchmark how effective the fix actually is...
These are the settings I changed so if you good folks would like to try them and post your results in the forums, please feel free, ideally on this thread so we can get some idea of how effective the changes are, but for me collision detection has been very solid since the tweaks and I would experiment more but it's 1am here and I have an early start.
So tired...
