Complete.Org: Mailing Lists: Archives: freeciv-dev: July 2002:
[Freeciv-Dev] Re: Maximum map size (was: Re: win32 client compiling trou
Home

[Freeciv-Dev] Re: Maximum map size (was: Re: win32 client compiling trou

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: <freeciv-dev@xxxxxxxxxxx>
Subject: [Freeciv-Dev] Re: Maximum map size (was: Re: win32 client compiling troubles)
From: Per I Mathisen <per@xxxxxxxxxxx>
Date: Tue, 2 Jul 2002 20:26:35 +0200 (MEST)

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



[Prev in Thread] Current Thread [Next in Thread]