Date: Wed, 03 Jul 2002 14:33:46 +1000
To: Per I Mathisen <per@xxxxxxxxxxx>
From: Christian Stock <cstock@xxxxxxxxxxxxxx>
Subject: Re: [Freeciv-Dev] Re: Maximum map size (was: Re: win32 client
compiling troubles)
Thanks. I didn't see that, it would explain the assert crash.
I'd like to have a go at extending those limits. I could limit my scenario
to a smaller size, but eventually, I'd like to do a whole world scenario,
and the detail in Europe is just not good enough on anything smaller than
320x180.
I hope some people (hopefully the ones who put these limits on) can tell
me what the problems are and what I have to be careful off? Maybe I can
come up with a solution?
Memory wise such a big map should take up about 2MB (just a rough estimate
from me) or so, which is nothing compared to the elevation maps flight
simulators have to deal with.
Cheers, Christian
At 08:26 PM 2/07/2002 +0200, you wrote:
On Tue, 2 Jul 2002, Andreas Kemnade wrote:
> That seems not to be a win32 problem.
> from common/map.h:
> #define MAP_DEFAULT_WIDTH 80
> #define MAP_MIN_WIDTH 40
> #define MAP_MAX_WIDTH 200
>
> #define MAP_DEFAULT_HEIGHT 50
> #define MAP_MIN_HEIGHT 25
> #define MAP_MAX_HEIGHT 100
>
> I don't know this part of the code very well.
> IMHO the network protocol cannot handle such large maps (I got the
> info by grepping through the source) so changing the maximum map size
can lead
> to problems.
Changing these defaults may have unforseen consequences in other parts of
the code. As you mention, the network protocol is a likely problem area.
However, such big maps also swamp up enormous amounts of memory, and the
minimap in the client swallows up a lot of real estate from the map when
it gets too wide (someone should fix this).
The latter begs the question, why is the X maximum bigger than the Y
maximum, when most clients have plenty real estate available in the Y
direction but not in the X direction?
Yours
Per
