Dave Hunsinger

Hi All - MadMatt mentions that the thread shows that this problem shows up in games other that CM games, but I don't see that mentioned anywhere. I, too, have such problems with the timer in CMBB PBEM games that I can't play turns at all. I'm using a newer Sony desktop machine, and as far as I know, all drivers are up to date, and all of the latest and greatest from Microsoft has been applied as well. I can't play movies at all now on the desktop box - the clock now just jumps from 0 to 60 seconds during movie playback, though earlier turns could be 'forced' to work by hitting the fwd & start buttons a few times until the normal timer showed up and the long numbers disappeared. Everything else on the machine works fine. Interestingly, I have a new Sony laptop, and the same PBEM movie turn plays just fine on it. So, it seems that the problem is being experienced by more that a few CMBB users, and it's not hardware specific. We now have Dell users, homebrew machine users and Sony users experiencing the same problem. I don't know how the uptime program mentioned in the thread tries to calculate system uptime (it's obviously wrong), but that's not the problem here. Regardless of how the uptime program works, the quartz clock that's in everybody's machine works the same (perhaps with a bit of variation), and 'timers' for games like CMBB are created and destroyed by the program itself, not by the uptime counter or by any other 'clock' on the machine. Ask yourselves this - of all of you who are experiencing the 'clock issue' in CMBB, do any of the clocks in your Windows system tray ever show the wrong time the way CMBB does? I'll bet a squad of Soviets against a batallion of Romanians the answer is 'no' - so the uptime thing is probably a red herring. One thing that would be interesting to know is which dll's CMBB calls when it works, what video cards people are using (though I'll bet the timer problem is unrelated to the jerky video problem mentioned in the thread). And... a better description of the play that causes the problem might help. I've only noticed the problem during PBEM, though I don't play solo much, and never have played TCP/IP. Also, I never saw the problem playing the beta scenarios - but I am having this problem with 'The Seam' scenario. Maybe with that information, we can start to figure out how all of the problem machines are similar and we might find an answer. CM is the greatest infantry combat game that exists - I sure hope we can figure out how to make it work on all 'approved' machines instead of most, because I don't want to have to give it up!