COD only using 1 core and 32bit???

Originally Posted by SEE

Just copied this from the CoD Cnfg file posted at SimHQ....should there be a colon in front of the ProcessAffinityMask?



[rts]
tickLen=30
;ProcessAffinityMask=2
maxTimerTicksInRealTick=20
; 0 - not use, 1 - show cursor and not capture, 2 - not show cursor, and capture
mouseUse=2
; 0 - not use, 1 - use if hardware exist
joyUse=1
; 0 - not use, 1 - use if hardware exist
trackIRUse=1
DisableIME=0
culture=en-GB

looks very much like the Il2 config, looks like the multicore hasn't made the initial release.

[Sven]

Sven, can that be enlarged so we can see the figures?

[SEE]

I wonder if that explains many of the Russian comments regarding CPU type not making much difference compared to physical RAM and GFX card specs?

[Sven]

Sorry Tree not mine, it's from russian sukhoi.su site, but it clearly indicates that of the 6 cores only 1 is running properly, there is something wrong with multi core support, that also explains why people with dual core are getting about same results FPS wise over there.

[Wolf_Rider]

this is a sad state of affairs to be discovering early on a Sunday morning...



as an aside, do some research on/ turning off Core Parking (W7 64bit users)

[SEE]

Feuerfalke has just posted a link that clearly states Multicore support was not a high priority during development but that CoD uses 'multi threading'. I don't understand the mechanics of this but I do find the minimum and preferred specs that were released a bit confusing given that performance on Dual core v multicore with identical Ram and GFX seems fairly similar. Best to read the interview linked in another thread byTREE UK.

Yes the Cnfg is posted at simhq no mention of OPenGL.

keep an eye on their thread, they are evaluating CPU control 2.1 as a posssible means to share the load across mutliple cores based on info/results from the Russian forums.

[flyingbullseye]

Originally Posted by SEE

Yes the Cnfg is posted at simhq no mention of OPenGL.

OpenGL was mentioned specifically in an interview with Oleg something like a year ago. He said COD is a DX only sim.

Flyingbullseye

[Heliocon]

Originally Posted by SEE

Feuerfalke has just posted a link that clearly states Multicore support was not a high priority during development but that CoD uses 'multi threading'. I don't understand the mechanics of this but I do find the minimum and preferred specs that were released a bit confusing given that performance on Dual core v multicore with identical Ram and GFX seems fairly similar. Best to read the interview linked in another thread byTREE UK.

Yes the Cnfg is posted at simhq no mention of OPenGL.

keep an eye on their thread, they are evaluating CPU control 2.1 as a posssible means to share the load across mutliple cores based on info/results from the Russian forums.

I read the article - multicore and mutlithreading are the exactly the same thing. Simplified - each cpu core has a thread, single core cpus have 1 thread, duals have 2, quads (like i5) have 4. Now i7 have 8 threads but only 4 cores. Each core is dual threaded. So a core can have more than 1 thread, (intel calls it hyperthreading). For a program though there is no distinction as they are all seen as "virtual cores".

@flying - they used to be d9+openGL, they left open gl to do dx10 (which seems to be absent).

[recoilfx]

Originally Posted by Heliocon

I read the article - multicore and mutlithreading are the exactly the same thing. Simplified - each cpu core has a thread, single core cpus have 1 thread, duals have 2, quads (like i5) have 4. Now i7 have 8 threads but only 4 cores. Each core is dual threaded. So a core can have more than 1 thread, (intel calls it hyperthreading). For a program though there is no distinction as they are all seen as "virtual cores".

@flying - they used to be d9+openGL, they left open gl to do dx10 (which seems to be absent).

Actually multi-thread and multi-core are different.

CPUs can have more or elss unlimited threads (till memory/resources run out) - a thread is a small unit of processing block that the OS can schedule.

All threads within the mutli-threaded program must share the same core - unless they are multi-process (utilizing multiple cores).

See: http://en.wikipedia.org/wiki/Multith...rchitecture%29