public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Lincoln Peters <sampln@sbcglobal.net>
To: Elijah Meeks <elijahmeeks@yahoo.com>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: Pre-alpha version of a coating-based terrain module
Date: Thu, 23 Sep 2004 00:46:00 -0000	[thread overview]
Message-ID: <1095898364.15989.41950.camel@localhost> (raw)
In-Reply-To: <20040922223938.77398.qmail@web13122.mail.yahoo.com>

On Wed, 2004-09-22 at 15:39, Elijah Meeks wrote:
> > One way to maybe display multiple coatings would be
> > to make custom
> > tiles for each coating
> > with holes in them...for instance, for grass make a
> > cloating that is
> > "patchy", so you
> > can see the underlying tile terrain underneath.  For
> > rain, clouds, and
> > snow, it could be patchy
> > in alternating areas, so that you could put a grass
> > coating and a rain
> > coating together
> > and have the holes in one merge with the patches in
> > the other.
> > 
> > For thick forest, you could fill the center totally
> > with tree texture,
> > and leave a couple of
> > corners open to show other coatings/terrain...
> > 
> 
> I think this is the best way, and I'd take it a step
> farther by saying you don't need any caveats to show
> the terrain underneath, except insofar as, say a
> forested hill would need to be obvious.  As it stands,
> a high-K-dirt hex, with a sparse-grass coating and a
> dense-redwood-forest coating on top of that can look
> like just the top coating, with further information
> available to players in the position to gather it. 
> For the most part, the top coating in this style of
> terrain is the dominant terrain in our current method
> and that seems to work fine for players.

I hadn't thought of that, but I suspect that we might be able to get
away with using the existing partial implementation of the coating view
code as long as the most important coatings are defined first.  That
way, the most important one will always be the one that shows up.

> 
> Now, if the Tolkien-style map tiles works, and we can
> import GIS data, does that mean we could one day have
> a Tolkien-style map of, say, North America?  Maybe
> complete with 'The Desolation of Pittsburgh'...

I think it would work.  Of course, the terrain module needs to be able
to model 'The Desolation of Pittsburgh' in an appropriate manner.  Maybe
the omniterr.g module needs a few more coating types to represent
different kinds of pollution... (I'll worry about that later.)

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

Push where it gives and scratch where it itches.

  reply	other threads:[~2004-09-23  0:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-21  5:43 Lincoln Peters
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 [this message]
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=1095898364.15989.41950.camel@localhost \
    --to=sampln@sbcglobal.net \
    --cc=elijahmeeks@yahoo.com \
    --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).