by NatVac on 05 Oct 2008 08:57
Yes, it could be a multi-core synchronization problem or a race condition issue. You might be able to tweak your system (e.g., reduce background tasks, lower memory requirements) to avoid the problem.
The problem started with 1.0004, but it can occur in 1.0005 as well. As of 1.0004, object creation was deferred to a second processor if one was available. The second thread sometimes "stalls", so that the object is not created at the time of the request. Perhaps some requirement is not ready, so the thread is put to sleep, only to be awakened long seconds and maybe even minutes later.
You could also disable all but one core in the BIOS before booting, and then play that way to see if it makes a difference. There are applications that can force a program and its spawned processes to use a single processor, but a game can be difficult to control this way because the different hardware drivers might already be running on separate cores before the game is even started.
STALKER is using an engine whose foundation dates back seven (now eight) years, from a time when dinosaur fish still swam in the oceans* and multi-core was considered RISCy business.
____________
*The coelacanth is probably still extant, but I've not heard anything about him in a while. And no, he is not a relative. :P --Well, at least to the best of my knowledge...