Yea, but it is no concern of programmer. The OS handles that, unless the programmer specifically wants to participate in the process. Despite your needs, there is no way a regular PC could move all that data to registers and do calculations with it at once. Even if there is data available worth of Xgb, you'll need only few kilobytes of that at once. That is why the virtual memory can work so independently.

True, and that is why I said I'll simplify it. That is not a technical issue, it is a marketing and user issue. In reality the programmer probably really is forced to limit the parameters so that nobody tries to create the huge world which even a super computer couldn't run. But in the end, it is a choice between allowing things and not allowing, because RAM is not the real limit here.

Your point? Lets assume you have 16gb ram in your computer and all that is available for the game. Do you seriously think your cpu could process all that all the time? Even the bus speed limits transfers to somewhere around 5-10gb/sec, so with that kind of processing you would get something like 2fps game. And that assumes you only transfer the data between cpu and ram modules without doing even a simple 1+1 calculations, which would reduce the frame rate even more. No, most of that data just sits there until it is needed and while doing that, it could just as well be in the hdd (or more preferably in ssd). Of course too much data there hurts, but we are talking about big rams now and not some little 2gb machine.

First, as far as I have understood right, modern AI works all the time in the own thread(s) ( ) and not just when you press end turn. Second, I don't think the AI needs all the graphical data needed for planetary views for example, or enemy data it doesn't see, or objects waiting something before things happend etc etc. I'm no game programmer so I could be wrong about that, but I doubt because it is common sense. However, it doesn't change the fact that 16gb precious data doesn't compute well in such situation no matter where it is.

The stuff that happens at the end of a turn can't happen until the player pushes the end turn button, no matter how many threads you have. Also if turns are sequential the AI can't go at all until their turn comes around, no matter how many threads you have.

The AI can use lots of threads to figure out what it wants to do, but actually doing it is a sequential process.

Just to put something in perspective, I have windows 8.1 with the following up and running: Firefox, + Classic Shell, + Bitmeter (shows lan/net usage rates), + "7 Sidebar" with a clock, CPU Usage (also shows RAM usage, clock speed, and CPU temperatures), GPU Meter (shows GPU usage and GPU temperature), and Drives Meter, These alone use almost 3GB of RAM.

Steam adds another 200MB.

Bringing up GC2 TotA with an immense galaxy adds about another 700 MB.

So, if you only have 4GB of RAM, GC2 is already close to page faulting, which will start slowing down the game's performance, as we have discussed in other threads.

For comparison purposes, Windows 7 uses a bit less memory. I just checked my wife's PC, on which she has the sidebar with a clock, CPU Usage, GPU Usage, and Network Monitor, and Live Mail up and running using a bit more than 2.3GB RAM. FireFox adds about 300 MB to that.

I think we can see from this that the 4GB RAM minimum figure being talked about on these forums is an absolute bare minimum to run anything on a modern PC.

Trying to calculate how much GC3 is going to need just for ships is also very short sighted. Ship designs need very little memory compared to how much memory is needed just for a segment of the galaxy, with all of the stuff that must be put in each tile, such as stars, planets, ships, resources, anomalies, path lines for trade routes and asteroid mine delivery routes, tile borders, etc. etc. And that isn't all that GC3 is going to have in its address space. Oh, and don't forget all the executable code.

***********

EDIT---> I just found out that the game I am playing is a gigantic galaxy, not an immense one. I also tried loading a Tiny galaxy, just to see how much RAM would be allocated to it. It was about 150MB smaller than for a gigantic galaxy. Since the Tiny was a new game without any turns, and the Gigantic was after exploring the entire galaxy, seeing two major races die due to wars with other races, and having conquered half of the drengin's planets (about half a dozen planets), it is quite likely that any comparison between the memory usage is skewed a bit.

Yes, this is true, but I think you missed the keyword "just" in the first sentence. I wasn't saying that ship designs don't use memory, but that there are other things that use quite a bit more space. And ships aren't the only thing that are going to use more space in GC3 due to the improvements they have told us about so far.. So is everything else displayed in the galaxy that will have improvements. Let's just say that talking about how much RAM will be needed by GC3 solely on how many ships you have in your fleet is rather short sided.

No, I am not against memory swapping (also called page swapping since it is handled by the OS a page at a time, and is caused by page faulting). Page faulting and the resultant page (or memory) swapping is a natural function of virtual address space operations. A little bit can be considered good, as that means you haven't spent more money on RAM than you needed to.

But, when the page fault rate gets high the performance of the OS and all running apps can become unbearable, and even appear hung.

So, it becomes a balancing act. Which do you want? More paging or more memory?

As an added note, don't forget how much damage to performance AdWare can cause.

Yes, and nobody has tried to deny that fact. 

I have 16gb ram on my notebook and something like 12gb of that actually free. I'm not going to even try filling it with a regular game, swapping or no swapping. I don't care if the game allocates it all just for fun, but once it tries to make use of it all, then the things start to fall apart.

And the beta party drinking party starts.....

Games today are already attempting to break the 32-bit limitations. Games that have heavy mod capabilities like Skyrim had to have LAA enabled so that more and more mods could be loaded. But in the end the 32-bit exe means that there is a hard limit as to how many mods and what you can do at one time. A 64-bit skyrim could in theory load every conceivable mod imaginable.

Steam workshop already makes mod support easy for devs and mod creators to distribute and insatll. So the need to break out from the 32-bit wall is already necessary.

http://www.gameranx.com/img/12-Aug/fpsmapdesign2010063628.jpg

This image is commonly used to deride modern FPS shooters. yet part of the reason for this is 32-bit architecture. Consumers DEMAND more polygons, more textures, more STUFF. Yet the memory contraints mean that you really have a lot of limitations on what you can do. FPS creators have to funnel you into areas because otherwise the engine would implode upon itself. Creators have to take the 2GB limit and figure out what they can and cannot possibly render at one time. Models, textures, lighting, etffects etc.

The move to 64-bit removes these barriers. It also means more memory can be allocated to other functions. Before you could never have the AI take up 1GB of memory. With 64-bit that's a reality and more.

Not sure whare you got that from but 64-bit is 64-bit thru and thru. As long as you compile the exe for 64bit.

Great thread. This started back in December of last year. 

Does anyone want to say, there is no need for 64bit now that we have seen and had chance to play? Further up the thread there was mention about this game having almost no chance of hitting the 4 gig threshold in data. I am wondering if it has already passed it and if the new ship designs as previously stated do in fact add to the overall total used?

The coming 'Immense' and the 'OH MY GOD ITS GOT STARS IN IT' map sizes,  I am sure will test the memory limits. 

Before we extol the virtues of 64-bit we have to consider potential drawbacks

1. Optimization:  Developers had to optimize and hoard system resources to not hit the 2GB limit. Lets wait for the next EA hype hit that is poorly coded and will crash and hog all the ram and never release it.

2....Thats about it