It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
What's the deal here? I can edit every single setting - resolution, sound quality, scaler, etc - but anything I attempt to do to the cycles is ignored. Any core type or cycle amount seems to switch right back to 'max' on it's own.
Anyone else having this issue? It's clearly reading the config file, but it's ignoring these lines. As a result I can't fix the sound skipping since it's always max.
This question / problem has been solved by Collectorimage
Huh. Now I'm REAALY confused. Editing the settings does indeed affect the speed yet the titlebar is stuck saying 'max'. A bug in this version of dosbox? I'll just ignore it I guess.
I would recommend that you use an abbreviated conf file. In other words, one that only has the changed value that you want. That way DOSBox will use defaults for all of the other settings. GOG tends to use a conf from an older version of DOSBox, which may lead to problems. A good starting point would be:
[sdl]
output= overlay
[cpu]
core= normal
cycles= 10000
[autoexec]
(just copy exactly from the [autoexec] section of the existing conf file here)
You can change or add to this as you wish.
avatar
Collector: I would recommend that you use an abbreviated conf file. In other words, one that only has the changed value that you want. That way DOSBox will use defaults for all of the other settings. GOG tends to use a conf from an older version of DOSBox, which may lead to problems. A good starting point would be:
[sdl]
output= overlay
[cpu]
core= normal
cycles= 10000
[autoexec]
(just copy exactly from the [autoexec] section of the existing conf file here)
You can change or add to this as you wish.

Full configs never really hurt, I've always used them. I also tend to use 'ddraw' since I find it easier to scale to my resolution and it looks crisp (yeah I like pixels)
Thing is though I can't find the magic cycle number. 10000 isn't right, it still skips. I'm going to keep experimenting but it seems really hard to find the perfect number. I'm sure I'll get it eventually.
avatar
Collector: I would recommend that you use an abbreviated conf file. In other words, one that only has the changed value that you want. That way DOSBox will use defaults for all of the other settings. GOG tends to use a conf from an older version of DOSBox, which may lead to problems. A good starting point would be:
[sdl]
output= overlay
[cpu]
core= normal
cycles= 10000
[autoexec]
(just copy exactly from the [autoexec] section of the existing conf file here)
You can change or add to this as you wish.
avatar
avatar_58: Full configs never really hurt, I've always used them. I also tend to use 'ddraw' since I find it easier to scale to my resolution and it looks crisp (yeah I like pixels)
Thing is though I can't find the magic cycle number. 10000 isn't right, it still skips. I'm going to keep experimenting but it seems really hard to find the perfect number. I'm sure I'll get it eventually.

Full configs can hurt when the conf file is from the wrong version of DOSBox. GOG tends to use the conf from 0.72 while shipping DOSBox 0.73. Full conf files also make it hard to spot what has been changed from defaults. This is why on VOGONS that they urge users having trouble with configuring DOSBox for a game to start over with a default config. 10000 may not be quite right for this game on your PC, but it is always a good point to start with the SCI games.
avatar
Collector: Full configs can hurt when the conf file is from the wrong version of DOSBox. GOG tends to use the conf from 0.72 while shipping DOSBox 0.73. Full conf files also make it hard to spot what has been changed from defaults. This is why on VOGONS that they urge users having trouble with configuring DOSBox for a game to start over with a default config. 10000 may not be quite right for this game on your PC, but it is always a good point to start with the SCI games.

Ah see you didn't mention this. I didn't notice it was 0.72 and not the latest. I've fixed it up now, removing the useless options.