I'm not bitching about how my computer can't run CC, it can, I'm just wondering if I should be able to run large explosions with minimal lag? Because right now, I can't. It gets laggy with too many people on the map sometimes. Anyway, just tell me if this should be able to run CC lag free?

Also, running Windows 7

Well, I have some trouble with explosions, or moving really, with a processor equivalent to your except with 2000 Mhz, but I usually have a lot of other things running.

Also, running Windows 7
Also, 32 bit

3.5 gigs ram what

Nothing should be able to run lag free during the hectic parts.

PSSSSSHHH, yeah right, try out a core i5.

DDR2. I'm trying to find the PC part, if that matters, but I don't really want to open my computer up to see.

Still utilizes only one core.

Thing is, the other three cores take care of all the other processes.
Well, they should in theory.

But you can do that with a normal dual-core too. No significant boost from my experience.

Try setting every other processes' affinity to one core and setting CC's affinity to both cores.

New socket, new architecture.
Better processor.
Mhz and RAM are not the only contributing factors to processor speed.


http://www.brighthub.com/computing/hard ... 48391.aspx

And hardware is not the only thing that dictates software performance. The main reason why we experience so much lag is because a) the software is not optimized for multi-core systems, and b) the system is not optimized to fully utilize VRAM.

Data can jump in here and correct me if I am wrong, but these are--allegedly--the software design flaws holding this game back from being a breeze on a decently constructed machine. There are plenty of 2D side-scrolling physics-y games that don't have the computational latency that this game has.

tl;dr data is a bad programmer.

Ahahaahahahahah

Thor, now you're just talking nonsense.

Hey now, that's not very nice

There's a lot of very expensive-on-the-cpu maths that have to be done every tick for all them particles to fly around properly. There's probably some optimization both on the code end and perhaps even on the mathematics end of things. Not to mention CPU/GPU offloading.

It's common to leave those things until late development because they are:

a) boring to code,
b) not necessary to code immediately (it has no dependencies)
and c) doesn't provide a valuable feature.

It's a "polish" thing.