Anyone have any idea why Build 22 is using 50% of my CPU constantly? (I'm running a dual core system, and looking at the graphs, it isn't running at 100% on one core, its running at 50% of each core on each core, e.g. 25% per core totaling 50%). It freezes randomly when bringing up the menu just after losing control of a previous body (dying). At first I thought it jumped up to 50% usage when it froze, but it is running like this constantly. I am not using any mods, I only just got the new build and wanted to try the new mission, so far I haven't been able to get even a little bit into the first part of the cave without it freezing.

This has never happened with any of the other builds since I bought Cortex Command at Build 19.

It is most definitely an issue with the program itself, as my hardware is more than adequate, and as I said I haven't had any issues with any other builds. No background programs are running either.

Specs:
Intel Core 2 Duo E6850 @ 3.00GHz
nVidia 8800GT 512MB
2GB Corsair XMS2 800MHz

It's running in windowed mode if that makes any difference.
Even if it is meant to be running at a capped 50% CPU usage, what's up with all the freezing for no reason?
I think 'm going back to 21, I'm sure half my mods won't work if I just copy them over to the new build anyway, and the new features don't seem to be real necessities.

EDIT: CPU Usage from previous builds seems similar but the 50% cap still scares me.
I can now replicate the freeze every time and it's not just in the zombie mission it's any game mode. It will freeze when I right click to bring up the menu (left trigger I think for you 360 controller people) within at least the first 2 minutes of play. Usually the 3rd or 4th time I bring the menu up in any situation. Now my question is, is this a known issue? Build 21 still works absolutely perfectly.

It means only the other core is used. Every non-multi-core program does the same. The 50% for each core is just windows showing it that way for some reason. If it buggers you, you can set the processes affinity to one core from the task manager, but it doesn't really affect anything.

Aaaah.

People should know that CC isnt a stupid game and the doesnt use a stupid amount of CPU.

Have you updated your drivers.

Some dual-cores have a timing issue.

Your freeze/crash issue is a known one, and I believe it has been fixed on the IGF/mac builds.

Either wait for B23 and see if it is, or try the IGF build.

what? CC is one of the most CPU-heavy games out there. Oo"