Optimal settings

[Mirek_Burczyn]

Since the game CONSTANTLY crashes (MAF errors) here and now with Immense map, I've decided to ask about optimal settings to avoid/reduce number of crashes. I'm interested with the biggest map possible, so:
- what kind of world to generate? from what i've collected, some types of maps crashes more than other
- how many AI-controlled civs are maximum?
- would neutering barbarians and/or animals help?


My PC is brand new - I've assembled it a month ago, so it's not the problem of hardware.

 

[Flowerpunkt]

I love immense maps.

My settings:
Planet generator 0.68 (perfectworld2f is good choice too..but I miss additional options like in PG)
Largest map size
50% ocean size
3 continents
no islands
17-18 civs
eternity/eons (I love antiquity and epic games

I played about 2k turns with just a few crashes and 1 corrupted save. That was version 33.

A couple of days I dwled latest SVN version (7353 I guess) and game seems to be most polished up to date.

The only MAF crash I acutally experienced lately was when I loaded a game (but does not happen too often).

Note that I use Win 7.

 

[strategyonly]

Since the game CONSTANTLY crashes (MAF errors) here and now with Immense map, I've decided to ask about optimal settings to avoid/reduce number of crashes. I'm interested with the biggest map possible, so:
- what kind of world to generate? from what i've collected, some types of maps crashes more than other
- how many AI-controlled civs are maximum?
- would neutering barbarians and/or animals help?


My PC is brand new - I've assembled it a month ago, so it's not the problem of hardware.

C2C no longer supports any map over Gigantic, sorry. We deleted all over that for maps. Just for that reason you listed above.

 

[Flowerpunkt]

I thought that with graphic paging the problem with immense maps was solved

 

[strategyonly]

I thought that with graphic paging the problem with immense maps was solved

paging is mainly for turn times. thats not saying that graphics do play a part of it.

 

[Mirek_Burczyn]

So... version 33 will be more stable than the latest one when playing Immense maps?

 

[Flowerpunkt]

paging is mainly for turn times. thats not saying that graphics do play a part of it.

So this does not apply for ver 34 anymore?

"the new "Graphics paging" option saves about 30% of RAM memory usage (with bigger maps, more RAM saving), and it should remove virtually all MAF errors."

 

[Flowerpunkt]

So... version 33 will be more stable than the latest one when playing Immense maps?

I think so but I wouldnt go back to 33 since they added a lot of interesting stuff in 34 and pre35

Try planet generator go on map size override and select something between giant and gigantic. Im using 192x120 map size and latest SVN...I will see how it works...

 

[Athmos]

v33 is considerably more stable and faster than the current one.

 

[JosEPh_II]

So... version 33 will be more stable than the latest one when playing Immense maps?

No! Any version with Immense map will eventually have problems. Just as playing a Large map with 48 AI will also have problems. Similar beasts and goblins, the 32 bit Civ IV BtS engine will eventually "choke" on all the data it will be required to handle.

JosEPh

 

[Thunderbrd]

You can still use viewports AND paging. And there are some paging settings that make it yet more effective at reducing memory problems but cause more issues with little delays in map shifts. I THINK Koshling left those settings manipulable by players if I'm not mistaken.

 

[Mirek_Burczyn]

Can someone explain me this viewports and paging settings? What they do, how to turn them on/off and so on.

 

[strategyonly]

Can someone explain me this viewports and paging settings? What they do, how to turn them on/off and so on.

Viewports:

http://forums.civfanatics.com/showthread.php?t=468011

If you have a 64 bit PC, you will most likely not need this, but you MUST have on graphic paging, (in short) it reduces the graphics so turn times are better.

 

[Athmos]

No! Any version with Immense map will eventually have problems. Just as playing a Large map with 48 AI will also have problems. Similar beasts and goblins, the 32 bit Civ IV BtS engine will eventually "choke" on all the data it will be required to handle.

JosEPh

Turn time was still considerably faster and I had A LOT less CTD and MAF with v33. Like, 10 faster and 10x less crashes. comparatively, v34 is broken.

 

[JosEPh_II]

Turn time was still considerably faster and I had A LOT less CTD and MAF with v33. Like, 10 faster and 10x less crashes. comparatively, v34 is broken.

Lets compare apples to apples and oranges to oranges here please. Wasn't addressing turn time directly between v33 release and v34 release. But was addressing the eventual issue of using Immense Map with Any version.

V34 Official Release version didn't have the MAF problem to start. But by SVN 7106 they started to show.

Also v33 had less content than v34. Custom Civs were being added daily in v34 SVN series that came after the release version.

Now are you talking about the release versions or the svn series after each release version? And the use of Immense Map in either?

JosEPh

 

[Athmos]

No, I'm only saying that with comparable settings, v33 is a lot faster and stabler than v34. Is that such a complex statement ?

Of course there were a lot of changes and addition between the 2. It would have been sad if the game ONLY became slower and more unstable !

 

[Sparth]

I tested c2c turn time and for exact same settings there is not significant differences between v34 and v28 (at least on the begining of the game).

 

[Mirek_Burczyn]

One more question. Is there any way to make World Editor work on Immense maps? The more land I've explored, the less stable the editor was (AI is still pathetic when it comes to creating new cities and editor allows it to catch on) and after exploring about 2/3 of the whole world the editor is a guaranteed way to get a MAF error.
Any suggestions?

 

[Athmos]

I tested c2c turn time and for exact same settings there is not significant differences between v34 and v28 (at least on the begining of the game).

Everything's fine at the start. Little by little however, the turn time grows, and it gets much slower in v34 than in v33. In my experience, v33 was also faster than v32, and much stabler than both (v34 being the worst offender). My guess is that the graphic paging introduced in v33 did wonder for both memory allocation and turn time, but v34 somehow added so much that that gain was nullified and then some.

I only got very few MAFs and no CTD whatsoever in v33, while they were common in v32 and are definitely back with a vengeance, earlier and more often in v34, with additional crashes while saving or loading as well.

 

[Sparth]

I only got very few MAFs and no CTD whatsoever in v33, while they were common in v32 and are definitely back with a vengeance, earlier and more often in v34, with additional crashes while saving or loading as well.

Hmm wait a while longer for v35 and nothing its changed then I show you how to made all civilizations using the same unit skins.