Intel Core i7-875K 2.93GHz Unlocked Quad-Core Processor ReviewThu, May 27, 2010 - 11:00 PM
S.T.A.L.K.E.R.: Call of Pripyat
The events of S.T.A.L.K.E.R.: Call of Pripyat unfold shortly after
the end of S.T.A.L.K.E.R.: Shadow of Chernobyl following the ending in
which Strelok destroys the C-Consciousness. Having discovered the open
path to the Zone’s center, the government decides to stage a large-scale
operation to take control of the Chernobyl nuclear plant.
S.T.A.L.K.E.R.: Call of Pripyat utilizes the XRAY 1.6 Engine,
allowing advanced modern graphical features through the use of DirectX
11 to be fully integrated; one outstanding feature being the inclusion
of real-time GPU tessellation. Regions and maps feature photo realistic
scenes of the region it is made to represent. There is also extensive support for older versions of DirectX, meaning that Call of Pripyat is
also compatible with older DirectX 8, 9, 10 and 10.1 graphics cards.
The game S.T.A.L.K.E.R.: CoP has no internal benchmarking tools built
into the game engine, but they do have a standalone benchmark available
that we used for our testing purposes. The screen capture above shows
the main window of the benchmark with our settings. Notice we are
running Enhanced Full Dynamic Lighting “DX10″ as our renderer.
Results: With the game running enhanced full dynamic lighting (DX10) we found again that the Intel Core i7 platform with either the 975 or 980X processor was hands down faster than the AMD Phenom II X4 965 Black Edition Processor. This is the only benchmark of the more than a dozen we tested that had the Intel Core i7 975 processor beating out the 980X processor. The Intel Core i7-875K does very well once again and shows that the LGA 1156 platform is a very good performer as it beats the Intel Core i7-930 on its LGA 1366 platform.
Looking for a way to explain this, we turned to task manager and found that S.T.A.L.K.E.R.: Call of Pripyat is threaded too well. In fact we only saw signs of life in four of the 12 threads with the majority being loaded up in one thread on CPU0.