max_scenario_size
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| max_scenario_size [2011/01/22 14:55] – created vic | max_scenario_size [2026/06/22 12:14] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| Basicly you are safe when map: | Basicly you are safe when map: | ||
| + | |||
| -stays below 20.000 hexes | -stays below 20.000 hexes | ||
| - | -does not use more then 10 regimes | ||
| - | -does not use more then 500 subformationtypes and/or itemtypes | ||
| - | It doesnt mean the game will run into issues if you make a scenario bigger than that but above this i am not sure it will always go ok. | + | -does not use more then 10 regimes if on 10-20.000 hex+ map. |
| + | |||
| + | -does not use more then 500 subformationtypes and/or itemtypes (especially not if using a lot of regimes) | ||
| + | |||
| + | It doesnt mean the game will run into issues if you make a scenario bigger than that but above this i am not sure it will always go ok. Especially if you go very far above the maximum recommendated | ||
| + | |||
| + | ====Memory==== | ||
| + | I checked out some out of memory errors and am quite sure they are actually caused by real memory considerations. Your RAM memory maybe very high but the application can maximum use maybe 1.5 GB or something around it (depending on multiple factors). Basicly as it is now you can hold a huge scenario in memory but not neccessarily have the memory left to load another scenario in memory as big as the current one and perform operations on it like importing or making it a masterfile. | ||
| - | best regards, | ||
| - | Vic | ||
max_scenario_size.1295708156.txt.gz · Last modified: 2026/06/22 12:13 (external edit)
