arizonachris wrote:I'm still sticking to my original opinion about RW needing fast hard drive reads. For now anyways. RW3 may bring a big change.
Now, the RAM question pops up. No 32 bit Windows can access anything over 3.2Gb. Known fact. 64 bit Windows can access 128Gb or more. But, for RW, the system RAM has nothing to do with load times. Yet.
So, Chessie's right, and SMM is right. (of course I'm right too

)
Yes, HDD reads are likely a large part of the performance for RW, since there is quite a bit that the game has to access to load the next tile. I would bet that the vast majority of stuttering would disappear if you had RW on a modern performance HDD (Caviar Blacks from WD, or even better, Raptors from WD, F3 from Samsung, etc) or a good SSD.
As for the 32 bit thing, its 32 bit ANYTHING, not just Windows, since any program written in 32 bits cannot address more than 4096MiB (4GiB) of memory. The reason Windows reports something less than 4GiB when 4 GiB are installed is that that 4GiB address includes ALL memory present in the system, including and memory built onto video cards, modems, sound cards, and the mobo itself. So if you stick 4GiB of RAM into a 32-bit system, like I currently am, you see somewhere between 3 and 4 GiB of RAM. My desktop reports 3.25GiB, and my laptop, lacking the video card, reports 3.5GiB. But at this point we are arguing semantics...
And not all 64-bit windows are the same. Home Basic (available only in certain South American, Asian, and Middle Eastern countries) supports only 8GiB of RAM; Home Premium (NA, Europe, "Developed" South American, Asian, and Middle Eastern countries) supports 16GiB. Professional, Enterprise, and Ultimate support 192GiB. Windows Server 2008 R2 supports 8GiB for Foundation, 32GiB for Standard and Web, 128 GiB for HPC, and 2TiB for Enterprise, Datacenter, and Itanium.