Hello. First off, thank you for FS_Open, it's a lovely piece of software. [thumbs up]
Okay, so i'm posting this here since (according to Karajorma) the May 9th build is apparently not much different. When using this April 25th build...
(in OpenGL, on Win98SE with DX8.1b, on a PIII 1.2GB with >400MB RAM and Radeon 9200)
...the game loads a mission smoothly, but then freezes during gameplay and will not resume. It happens totally at random. The OS doesn't crash with it. The freeze happens both in fullscreen and windowed modes. The debug spew ends with "TIMER ROLLED!" as the last entry.
Oddly enough, a search on the forum uncovered an earlier thread from October of last year:
http://www.hard-light.net/forums/index.php?PHPSESSID=7cdbf76508ecaed5f528274848979ab7&topic=35691.0In the thread, MatthewPapa pointed out where the "TIMER ROLLED!" arises in the code of timer.cpp:
-----
QueryPerformanceCounter(&time_tmp);
if ( time_tmp.QuadPart < Timer_last_value ) {
// The clock has rolled!
Timer_base = time_tmp.QuadPart;
mprintf(( "TIMER ROLLED!\n" )); // Hack: I'm not accounting for the time before roll occured,
// since I'm not sure at what value this timer is going to roll at.
// Time_now = time_tmp.QuadPart;
}
Time_now = time_tmp.QuadPart - Timer_base;
Timer_last_value = time_tmp.QuadPart;
out->QuadPart = Time_now;
LEAVE_CRITICAL_SECTION( Timer_lock );
}
#endif // _WIN32
----
Then taylor responded to him with:
"I highly doubt this is related to video problems. It's definitely an issue with the timer but I can't say why. Possibly some other hardware issue but likely just something between Windows and the system... Oh, you have a dual core CPU? That would most likely be your issue. It's having a fit with QueryPerformanceCounter so I guess we'll have to add that to the todo list, though I'm not sure what to do about it. Off to MSDN I guess... For now I think it will work if you run the game(s) in compatibility mode. If that doesn't help any report back and I'll put this at the top of my list of things to fix."
In my case though, i'm not using a dualprocessor system, so i doubt the "TIMER ROLLED!" error is arising from anything to do with that. And taylor presumably fixed any issues long since then. So, any ideas, anyone? Thanks in advance.