From: Eric McDonald <mcdonald@phy.cmich.edu>
To: mskala@ansuz.sooke.bc.ca
Cc: xconq7@sources.redhat.com, <xconq-hackers@lists.sourceforge.net>
Subject: Re: Image handling: update on my status and plans
Date: Tue, 04 Jan 2005 19:45:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0501041438140.22983-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <Pine.LNX.4.53.0501041403160.7387@opal.ansuz.sooke.bc.ca>
On Tue, 4 Jan 2005 mskala@ansuz.sooke.bc.ca wrote:
> > that name from elsewhere; I think he had something to do with the DeCSS
> > stuff or maybe a DMCA lawsuit....
>
> He was an expert witness in the Federal Microsoft anti-trust case, and
> more recently was attacked by the RIAA after leading the team that
> broke the SDMI Challenge files.
Ah, that's right. It was SDMI, not DeCSS.
> > The terrain generator ensures that the all terrain with the 'liquid'
> > property set has a uniform elevation with all neighboring liquid terrain.
>
> I think what triggers the bug is elevation=0 rather than liquid terrain as
> such, but the way the games are designed means that terrain at elevation 0
> normally will be liquid.
Right. I was saying that 'liquid' acts an elevation leveler.
Usually, this means leveling the terrain to a height of 0.
However, if the problem is caused by elevation == 0, then why
don't I see it on all cells that are part of the same ocean? This
is what I was getting at.
> kernel that lives on the server. The point is that we shouldn't have to
> make each change to the "decide what image to show" code in more than one
> place in the source tree; I think we're on the same page about that.
Yes, absolutely.
> one image per terrain type. That image is of a three-dimensional chunk of
> (for instance) mountains, with a hexagonal base but sticking up
> vertically, probably outside the hex tile boundaries, to express vertical
> height.
Right.
> What I was imagining for automatic generation would be that the designer
> specifies a hexagonal overhead view (they already do), the program renders
> that into 3D as a flat hexagon, and then if the designer wants relief,
> they specify a height field which is used to add the relief.
I see.
Eric
next prev parent reply other threads:[~2005-01-04 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 7:31 mskala
2004-12-22 20:59 ` Eric McDonald
2005-01-04 19:15 ` mskala
2005-01-04 19:45 ` Eric McDonald [this message]
2004-12-23 5:00 ` Isometric Terrain Elijah Meeks
2004-12-23 6:25 ` Eric McDonald
2004-12-24 20:20 ` Stan Shebs
2004-12-25 19:57 ` Elijah Meeks
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=Pine.LNX.4.44.0501041438140.22983-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=mskala@ansuz.sooke.bc.ca \
--cc=xconq-hackers@lists.sourceforge.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).