Runing C2C with 2 gb of ram

methastasis

Chieftain
Joined
Aug 9, 2012
Messages
2
There is any chance of runing this mod with only 2 gb of ram?
because i have ed up one of the ram slots
 
Yes, it is possible. Although it will limit the size of the game you can play, even if you use the viewport feature.

You could also try the Rocks 2 Rockets mod-mod of C2C, which is intended for just such a situation. R2R is a trimmed down version of C2C. The content started as what was in version 24 of C2C and was trimmed a bit (I'm not sure, but the total quantity of stuff is probably similar to something in the v22 to v23 range). The game engine itself (the DLL) is based on the one used by C2C v26, but has had many of the bug fixes and optimizations done after v26 added to it (but not most of the new capabilities, which increase the memory used) - it has not quite caught up to v27 with these things yet. The various optimizations cause it to use a bit less memory than earlier versions.
 
Hm. I couldn't even get the mod to load a map correctly when I still had Win7 x86 installed, although I had deployed all of my excessive RAM as a RAM drive holding the page file.
The game would either crash while creating the map, or not display the interface. Even when selecting "duel" map type.
Other mods worked just fine.

After changing to x64 windows I had no problems at all. Well, almost none, I still get the occasional memory allocation error even with 16gb of RAM.
 
I have just under 2.5G of RAM on XP. V27 was very unstable for me even on a tiny viewport, but I got an early December SVN (4417ish), and now I don't need viewports at all.

But I can only load a Small map...

If I wanted to play a Standard-size map (which I do of course), what can I try (ie. settings, modmods, or RoM)?
 
1st, and sorry about this , but do not use GEM, SEM, Perfect World or Perfect Mongoose maps. They are heavily scripted and require more ram. Use one of the "regular" BtS maps.

Turn the Graphics down to Medium.

Do Not use more than 7 AI on a Standard size map. Do not use Barb Civ or Barb World. Do not use REV. Any setting that will generate More Civs will use more ram.
Do Not use Mastery Victory setting either, keep Victory settings to 2 or 3 conditions.
Try this for starters.

JosEPh
 
1st, and sorry about this , but do not use GEM, SEM, Perfect World or Perfect Mongoose maps. They are heavily scripted and require more ram. Use one of the "regular" BtS maps.

Turn the Graphics down to Medium.

Do Not use more than 7 AI on a Standard size map. Do not use Barb Civ or Barb World. Do not use REV. Any setting that will generate More Civs will use more ram.
Do Not use Mastery Victory setting either, keep Victory settings to 2 or 3 conditions.
Try this for starters.

JosEPh

Now this is REAL good advice! ;)
 
One thing I never understood is how the graphic settings affect your normal RAM. I was having video memory crashes left and right as well when I was running my 32 bit Windows, which did get a lot better when I turned down the graphics.
These type of problem is now entirely gone after changing to 64 bit, with the exact same hardware configuration as before.

So obviously even if the graphics cards itself would be able handle all the stuff, the lack of RAM (or what Civ considers as RAM, as it doesn't play along very nicely with the page file) can also cause some video memory errors instead of a more "fitting" general memory allocation error.
 
One thing I never understood is how the graphic settings affect your normal RAM. I was having video memory crashes left and right as well when I was running my 32 bit Windows, which did get a lot better when I turned down the graphics.
These type of problem is now entirely gone after changing to 64 bit, with the exact same hardware configuration as before.

So obviously even if the graphics cards itself would be able handle all the stuff, the lack of RAM (or what Civ considers as RAM, as it doesn't play along very nicely with the page file) can also cause some video memory errors instead of a more "fitting" general memory allocation error.

Part of the problem is Civ IV is old, graphics cards were new when it was written. This means that some of the graphics stuff is done in RAM not in the video memory.
 
Part of the problem is Civ IV is old, graphics cards were new when it was written. This means that some of the graphics stuff is done in RAM not in the video memory.

I don't believe that's because graphic cards were "new" when Civ4 was written. It was released in 2005, which is "only" 7/8 years from now.
That fabulous Geforce 4400 Ti I once had was released in 2002, so 3D graphics card were well established when Civ4 was being developed (Civ3 was released 2001).

Though it may very well be the case that the developers simply didn't care much and rather relied on the "normal" RAM.
 
I run the game with 8 gigs of ram, and I get /massive/ slowdown on maps like GEM 50 civs or a huge map with rev/barbarian civs that gets a lot of civs on the map. It's still playable, but my wait time between turns can be up to five minutes long. Makes me wonder what kind of beast machines the people who made these maps must be running.
 
I haven't seen my game use more than 2.8 gb of RAM so far, so after a certain treshold the limiting factor is single core CPU power and not the amount of memory you have. At least unless there's a nifty trick that'll teach civ to use more than the 1 core it currently uses.
Which I don't know of.
 
Actually, C2C (and R2R) use more than one core for a few things: animal/barb spawn plot eligibility checking and property (flammability, etc.) processing. C2C uses 4 threads for these things, and R2R uses 2. Using more than one thread for these things is a small speedup, since they are only a small part of what happens for the AI turn processing, but it is better than nothing. If you monitor the CPU usage while playing you can see that the total CPU time has occasional spikes that are well over using 100% of just one core; I have noticed R2R going over 75% briefly each turn on a 2 core system, where 50% is all you can get from a single thread (it presumably actually hits, or comes very close to, 100% briefly but the interval is shorter than one update shown by the Task Manager so it is diluted with some processing that is single threaded).
 
i got 4 gb of ram total (i'm still desperately looking on my calender when i can upgrade it to 8 gb)

it works Perfect on Medium size maps and large size maps do also want to work though Viewports are badly needed on large map (haven't gone GEM but i do use Perfect world and high end Graphics options)
 
i got 4 gb of ram total (i'm still desperately looking on my calender when i can upgrade it to 8 gb)

it works Perfect on Medium size maps and large size maps do also want to work though Viewports are badly needed on large map (haven't gone GEM but i do use Perfect world and high end Graphics options)

No offense BUT if you dont have an X64, no need for the extra memory.
 
Windows 7 X64 here ;)
 
Back
Top Bottom