Not enough memory to play this game O_o

MrDawkins · 2012-11-20, 01:31 PM

I played the beta from work on my laptop just fine with its 2 gigs of ram. I was able to res people and do my job, but now I can't even install the game!?

Even on my work PC witch has 4 gigs of ram, it wont let me install saying I only have 2.5 gigs of ram because of my video card. Why did they bother only making the game 32 bit if THEY WON'T ALLOW IT TO EVEN RUN ON A 32 BIT MACHINE

I think it should be my choice to install and play a slide show if I choose.

PS home pc is installing just fine.

Strube · 2012-11-20, 01:46 PM

Same thing here. Hope this is a bug and not a "feature" or "intentional limitation".

Jaybonaut · 2012-11-20, 01:47 PM

As it's been listed since the beginning:

Current Minimum System Requirements
OS: Windows XP
Processor: Intel Core 2 Duo E6850 or higher / AMD Phenom II X2 or higher
Memory: 4 GB RAM
Hard Drive: 15 GB free
Video Memory: 256 MB RAM
Video Card: nVidia GeForce 8600 series or higher / AMD or ATI 4850 series or higher
Sound Card: DirectX compatible

Current Recommended System
OS: Windows 7
Processor: Intel i5 processor or higher / AMD Phenom II X6 or higher
Memory: 8 GB RAM
Hard Drive: 15 GB free
Video Memory: 1,024 MB RAM
Video Card: nVidia GeForce 500 series or higher / AMD HD 6870 or higher
Sound Card: DirectX compatible

Skepsiis · 2012-11-20, 10:11 PM

I only have 2 gigs of ram in my PC and ps2 was able to install via steam and play today.

Everlast · 2012-11-21, 03:26 AM

IF the game works with 2 gigs of ram then congratulations. The official system requirements are what they are tho, so dont be surprised when the game doesnt work with 2 gigs of ram, i mean its not the games fault or the developers.

Bags · 2012-11-21, 03:38 AM

If it worked on less than 4gb of ram in beta I don't see why bar them from playing live.

Also, if you require 4gb of ram to play... you alienate all 32 bit OS users

lol

Mechzz · 2012-11-21, 03:41 AM

4 Gig required - and they went with DX9. Talk about mixed priorities?

Buggsy · 2012-11-21, 02:32 PM

Originally Posted by Jaybonaut

As it's been listed since the beginning:

Current Minimum System Requirements
OS: Windows XP
Processor: Intel Core 2 Duo E6850 or higher / AMD Phenom II X2 or higher
Memory: 4 GB RAM
Hard Drive: 15 GB free
Video Memory: 256 MB RAM
Video Card: nVidia GeForce 8600 series or higher / AMD or ATI 4850 series or higher
Sound Card: DirectX compatible

Current Recommended System
OS: Windows 7
Processor: Intel i5 processor or higher / AMD Phenom II X6 or higher
Memory: 8 GB RAM
Hard Drive: 15 GB free
Video Memory: 1,024 MB RAM
Video Card: nVidia GeForce 500 series or higher / AMD HD 6870 or higher
Sound Card: DirectX compatible

It doesn't specify if it's Windows XP 32 bit or 64 bit.

I've got 32 bit, but am using the /3GB switch on bootup.

Fenrys · 2012-11-21, 09:47 PM

I was showing 3.5GB RAM usage when I checked earlier today at the warp gate, and that was with bittorrent and firefox open in the background.

Skepsiis · 2012-11-22, 01:23 AM

It hitches like crazy and i have hard faults coming out of my ass as the page file gets battered.... but the game will run on 2 gigs of ram. Ive actually got a kd ratio of about 3. You just need to potshot to help friendlies or flank campers

The hitching is real bad most of the time though and incredibly frustrating so i completely agree with the official minimum spec being 4 gb.

Rbstr · 2012-11-22, 01:41 AM

Originally Posted by Bags

Also, if you require 4gb of ram to play... you alienate all 32 bit OS users

*shrug* All of the CPUs in the requirements are 64bit. Gotta leave the obsolete behind at some point.

Rushyo · 2012-11-22, 08:04 AM

Even on my work PC witch has 4 gigs of ram, it wont let me install saying I only have 2.5 gigs of ram because of my video card. Why did they bother only making the game 32 bit if THEY WON'T ALLOW IT TO EVEN RUN ON A 32 BIT MACHINE

You're conflating process memory allocation for physical memory available. 32-bit is irrelevant. Your problem (if your statement about the video card is to make any sense) is that you've allocated 1.5GB of your system's RAM to your video card. It may be that your video card relies on shared memory, in which case I'd suggest not playing on a non-gaming laptop. Otherwise, you can just de-allocate that memory from the video card in the BIOS.

Fenrys · 2012-11-22, 11:47 AM

Originally Posted by Rushyo

You're conflating process memory allocation for physical memory available. 32-bit is irrelevant. Your problem (if your statement about the video card is to make any sense) is that you've allocated 1.5GB of your system's RAM to your video card. It may be that your video card relies on shared memory, in which case I'd suggest not playing on a non-gaming laptop. Otherwise, you can just de-allocate that memory from the video card in the BIOS.

That's not the problem I don't think. A 32 bit system only has 4GB of address space. The motherboard takes about 0.5GB, in the example you quoted the GPU probably had 1GB of it's own on-board VRAM, and that leaves 2.5GB of addresses available for system RAM. Even if they had 3-4GB of system RAM, they'd only be able to use 2.5GB because the rest of it would be 'invisible' due to lack of addresses.

Rushyo · 2012-11-22, 12:31 PM

That's not the problem I don't think. A 32 bit system only has 4GB of address space. The motherboard takes about 0.5GB, in the example you quoted the GPU probably had 1GB of it's own on-board VRAM, and that leaves 2.5GB of addresses available for system RAM. Even if they had 3-4GB of system RAM, they'd only be able to use 2.5GB because the rest of it would be 'invisible' due to lack of addresses.

Does the graphics card's on-board VRAM really get included in the process addressable memory? I suppose I should know this (as a games developer) but it's never actually come up. Isn't it the driver's job to address the on-board memory, not the host process? If I give the renderer a reference I don't think of it as looking in process' mapped memory. I expect it to look at the some other mapping that I really don't care about at the process level (such as a mapping across the system RAM and the GPU RAM, in the case of shared VRAM). Why would that restrict what my process can map?

EDIT: Mmm. Just checked MSDN. Devices do indeed happily gobble addressable memory in Windows because of MMIO. So my question would then be: Does PAE not then come in to play?

EDIT2: Answering my own question again. So the Windows XP and 7 kernels are borked to limit addressable space to 4GB even with PAE-aware processes. You can use a custom kernel (with bits nicked from 2003) to overcome this limitation: http://superuser.com/questions/52275...-3-5-gb-of-ram but obviously this is dangerous as all hell.

EDIT3: This article is really enlightening: http://www.geoffchappell.com/notes/w...nse/memory.htm. Comes down to Microsoft's absurd licensing model. Essentially DRM. They don't want consumers getting the luxury of this functionality, even though the software can handle it.