public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Lincoln Peters <sampln@sbcglobal.net>
To: cstevens@gencom.us
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: GIS Update
Date: Wed, 27 Oct 2004 17:17:00 -0000	[thread overview]
Message-ID: <1098855994.26829.38.camel@localhost> (raw)
In-Reply-To: <200410270401.09702.cstevens@gencom.us>

On Tue, 2004-10-26 at 21:01, D. Cooper Stevenson wrote:
> All,
> 
> Quick Take:
> 
> During the game, you might see something like this (review):
> 
>   http://wiki.xconqgis.org/index.php?WhatGisImageMightLookLike
> 
> The world size is the same as Normandy's, 186x159. I've recalibrated the 
> image's resolution to match. The computer "sees" this:
> 
>   http://wiki.xconqgis.org/images/grass2xconq/seattle_lowres_large.jpg
> 
> How about that?

Quite impressive.

> 
> Now, this is really important. Note that these are images not of _elevation_ 
> data; it's actual _landcover_ data! The landcover data translates directly 
> into terrain types. Note too that exporting GIS elevation data is trivial. 
> Very nice!

Do you think that this data map nicely to the terrain types in an
existing terrain module (plains, forest, desert, mountains, swamp,
shallows, sea), or does this call for a new terrain module to be of any
real interest?  If at this point you're just dealing with landcover, I
could create a simplified spin-off of my proposed omniterr.g terrain
module toward that end (no coatings would be needed).

Elevation data, of course, is a fairly simple matter to import. 
Although as far as I can tell, it only affects the isometric view code
and (sometimes) the fractal percentile terrain generator.

> 
> I did a spot check and found that the ascii export and the low res image seem 
> to coincide. I'll know for sure when I'm finished with the conversion script.
> 
> The best news is that the entire process is capable of automation. This has 
> the potential for real-time rendering wherever the tacticians wish to fight 
> (or run).

What kind of CPU and memory does the process require?  It probably
wouldn't be an issue on newer computers (especially those built
specifically for playing games), but somewhere out there, someone is
probably still playing Xconq through an ASCII terminal with the Ncurses
interface, and you can guess how much power that thing would have...

> 
> I hope to have 3D renderings soon. Just for fun, here's an image created with 
> GIS data similar to the elevation data I'm using:
> 
>   http://photojournal.jpl.nasa.gov/jpegMod/PIA06668_modest.jpg

Looks like we might be able to dramatically improve the isometric view
code (at least for some games) without having to make any major changes
to the actual view code!  Of course, since I've never messed with the UI
code, I'm guessing there.

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

BOFH excuse #13:

we're waiting for [the phone company] to fix that line

  reply	other threads:[~2004-10-27  5:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-27  5:42 D. Cooper Stevenson
2004-10-27 17:17 ` Lincoln Peters [this message]
2004-10-27 17:25   ` D. Cooper Stevenson
2004-10-28  0:54     ` D. Cooper Stevenson
2004-10-28  4:54     ` Lincoln Peters
2004-10-30 22:15       ` D. Cooper Stevenson
  -- strict thread matches above, loose matches on Subject: below --
2004-09-22  2:26 D. Cooper Stevenson
2004-09-22  2:59 ` Eric McDonald
2004-09-22 16:36 ` mskala
2004-10-02  1:29   ` Christopher Wood

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=1098855994.26829.38.camel@localhost \
    --to=sampln@sbcglobal.net \
    --cc=cstevens@gencom.us \
    --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).