public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Lincoln Peters <sampln@sbcglobal.net>
To: Xconq list <xconq7@sources.redhat.com>
Subject: Pre-alpha version of a coating-based terrain module
Date: Tue, 21 Sep 2004 05:43:00 -0000	[thread overview]
Message-ID: <1095739618.15989.38909.camel@localhost> (raw)

I've given up on implementing bodies of water as coatings (I'll make
them cell terrain), I've given up on soil composition (at least for
now), and I've re-implemented climate as cell terrain.  It's still a
rather complicated terrain module, and it has a ways to go before it's
usable, but it should offer at least a general idea of what I'm trying
to do.

You can download it at:
http://homepage.mac.com/lmpeters/omniterr.g

Right now, it's probably usable for the Xconq/GIS project, but for
anything else, the following issues need to be addressed:

1. The existing code for generating maps does not allow me to place
climate zones in a realistic manner.  Currently (though this may be
partially due to the means by which I laid out terrain), it sees nothing
wrong with placing a "tropical wet" zone right next to a "polar ice cap"
zone!  Eventually, I would also need a way to ensure that, for example,
a random map does not place a Mediterranean climate on the east coast of
a continent (Mediterranean climates are *never* found on the east coast
of anything).

2. There needs to be a synthesis method for applying coatings to terrain
when the coatings are unlikely to change over time (as would be the case
when climates and vegetation are defined as coatings).  Perhaps some way
to run the make-fractal-percentile-terrain (or a variant thereof, as per
#1) on coatings after running it on cell terrain?  (For now, I'm not
even going to consider making dynamic coatings work!)


The following issues affect the Xconq/GIS project, although they would
not necessarily preclude the use of this module for that project:

3. I opened the module in "Design" mode, since I could then apply
coatings to cells manually with little fuss.  I discovered that, when
multiple coatings exist on one cell, only the coating defined first in
the module will appear.  For example, if you apply a "savanna grass"
coating to a cell, followed by a "rain" coating, only the "savanna
grass" coating shows up on the map (both show up correctly in the text
on the "description" bar).  There needs to be a way to display multiple
coatings simultaneously on the map.

4. There need to be terrain images that would correspond to each of
these 20 different climate zones (not to mention the 8 types of
vegetation, though they tend to be specific to one or two climate
zones).  If you don't understand why, try running the module and notice
the color scheme I had to use!*

5. As soon as I put some real-world figures into the temperature
definitions, I found snow spontaneously appearing, due to the hard-coded
hack that was used to make ww2-eur-42.g work!

6. While trying to make the best of the unexpected snow, I discovered
that, when a cell is in night conditions, coatings are *not* drawn at
all.  Weird.


* Actually, I didn't try very hard to make the terrain images look
good.  At the moment, they're each basically the same color that is used
in the color-coded map I was studying while writing the GDL code, and it
didn't turn out very well.

---
Lincoln Peters
<sampln@sbcglobal.net>

A committee takes root and grows, it flowers, wilts and dies, scattering the
seed from which other committees will bloom.
		-- Parkinson


             reply	other threads:[~2004-09-21  4:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-21  5:43 Lincoln Peters [this message]
2004-09-21 16:39 ` Feeling left out of the terrain talk Elijah Meeks
2004-09-22  0:26   ` Eric McDonald
2004-09-22  1:45     ` Lincoln Peters
2004-09-22  1:59       ` Eric McDonald
2004-09-21 16:41 ` Pre-alpha version of a coating-based terrain module Eric McDonald
2004-09-22  1:15   ` Lincoln Peters
2004-09-22 22:39     ` Steven Dick
2004-09-23  0:10       ` Elijah Meeks
2004-09-23  0:46         ` Lincoln Peters
2004-09-23  3:03         ` Eric McDonald
2004-09-23  2:37       ` Eric McDonald

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1095739618.15989.38909.camel@localhost \
    --to=sampln@sbcglobal.net \
    --cc=xconq7@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).