First, my PC specs:
Toshiba Satellite A505. Windows 7 Professional. Intel Core i3 CPU. M 330 @ 2.13Ghz. 4.00 GB RAM. 64 bit.
I tried running "The Dig" last night on the current stable build and experienced some severe lags which resulted in choppy animations and audio. Occasional clicks and pops were audible too at times. I previously played the game last year and do not recall experiencing anything of the kind then.
After playing through a portion of gameplay, then reloading a saved game from an earlier point, things became much smoother. But the minute I reached a point past where I had previously played, things became choppy again.
All data was copied from the CD to my hard drive at time of testing.
I read the F.A.Qs and tried making a batch file with the SDL audio settings modified, but that made no difference.
I tested several other games afterwards and experienced no such lags.
Any suggestions for settings to modify and/or PC issues to look for would be appreciated.
The Dig - Jerky animations, choppy audio
Moderator: ScummVM Team
- envisaged0ne
- Posts: 162
- Joined: Mon Nov 01, 2010 9:17 am
- Location: United States
That sounds like an issue with your libSDL sound or the low level sound drivers.
Firstly, if you have compressed your Dig datafiles using scummvm-tools, then this may happen with A/V sync.
If so, then revert to using the uncompressed files and see if the problem disappears.
We would also suggest that you use the latest v1.7.0pre (soon to be the next release) or v1.8.0git daily build, rather than v1.6.0 and see if the problem is still occurring with the latest code:
http://www.scummvm.org/downloads/#daily
Apart from this, if you run ScummVM from a command window as "scummvm -d 1", the you will see any debug messages and/or warnings which may be associated with this. However, some of these such as audio buffer size mismatch can occur and still be not the cause of the problem.
Firstly, if you have compressed your Dig datafiles using scummvm-tools, then this may happen with A/V sync.
If so, then revert to using the uncompressed files and see if the problem disappears.
We would also suggest that you use the latest v1.7.0pre (soon to be the next release) or v1.8.0git daily build, rather than v1.6.0 and see if the problem is still occurring with the latest code:
http://www.scummvm.org/downloads/#daily
Apart from this, if you run ScummVM from a command window as "scummvm -d 1", the you will see any debug messages and/or warnings which may be associated with this. However, some of these such as audio buffer size mismatch can occur and still be not the cause of the problem.