Poor performance from a high-end build?

[Zok]

Who told you that was a high end build?

Problem 1: ---I5--- It's just a new name for the word "Celeron"
Problem 2: Windows 7 64bit (home edition)
All windows 7 even pro 64, with exclusion to ultimate still has the 3.2gb memory limit (straight off Microsoft's Technical forum)
So you have 4.8gb just sitting there gathering heat only.
---------
What resolution are you running at?
The higher you go; the more memory gets taken away to run the game. (so if your at 3.2gb do the math)
---
This games video rendering is pretty intense!

You video card comes in 3 versions 1gb 2gb an 4gb
Most Games have the option of hardware/software control.
(however) I'm beginning to wonder, that by default this game is 1/2 software then video controlled, (which would explain the heavy CPU usage).

[Raist]

Who told you that was a high end build?

Problem 1: ---I5--- It's just a new name for the word "Celeron"
Problem 2: Windows 7 64bit (home edition)
All windows 7 even pro 64, with exclusion to ultimate still has the 3.2gb memory limit (straight off Microsoft's Technical forum)
So you have 4.8gb just sitting there gathering heat only.
---------
What resolution are you running at?
The higher you go; the more memory gets taken away to run the game. (so if your at 3.2gb do the math)
---
This games video rendering is pretty intense!

You video card comes in 3 versions 1gb 2gb an 4gb
Most Games have the option of hardware/software control.
(however) I'm beginning to wonder, that by default this game is 1/2 software then video controlled, (which would explain the heavy CPU usage).

umm.. not sure where you got your information from, but I think you may be a bit confused about what you are reading. It sounds like you are looking at individual, specialized heap sizes... but even then, it's not entirely correct. Here's an actual link to the real numbers:
http://msdn.microsoft.com/en-us/libr...=vs.85%29.aspx

Windows runs on virtual memory. It is kind of "dumb" when it comes to your physical memory. It will use physical memory that it finds it can address up to a certain point, then it uses virtual memory (basically, your hard drive). The problem comes with x86 architecture that claimed address spaces for hardware in Windows mappings, which prevented it from seeing the full 4GB, and that is why many only saw about 3.2GB on average. Combine that with the default 2GB/1GB caps on the system and user heaps, and you had some wonkiness with memory management in XP. Let's not even talk about 98... that was a fun one when you passed the 384MB line... lol.

Most of that is obliterated with the newer x64 OS's now. With specific setups, in some cases you can hit TB's of address space now. Granted.. the page/nonpage pools are still limited to GB's, but that is 128GB or more--but the system can track up to a TB for specific situations. I mean.. come on... when your physical limit is 8TB.... yeah, Microsoft has ways for you to use the piss out of your physical memory.

Now... whether SE is claiming a big-@$$ed heap for the game, that is another story... but your SYSTEM will use it for other processes, if nothing else.