From: Eric McDonald <mcdonald@phy.cmich.edu>
To: mskala@ansuz.sooke.bc.ca
Cc: xconq7@sources.redhat.com
Subject: Re: Using terrain coatings and existing code to model topography, weather, and vegetation
Date: Tue, 21 Sep 2004 00:43:00 -0000 [thread overview]
Message-ID: <414E41E2.2030502@phy.cmich.edu> (raw)
In-Reply-To: <Pine.LNX.4.21.0409192045520.23753-100000@diamond.ansuz.sooke.bc.ca>
mskala@ansuz.sooke.bc.ca wrote:
> On Mon, 20 Sep 2004, Andreas Bringedal wrote:
>
>>infantry through it and see the attrition skyrocket. It would be
>>nifty to have a strenght 5 storm move semirandomly across the map by
>>spesific scenario design or by a very low random chance.
>
>
> I think if I wanted to model a hurricane, I might do it by having the
> storm be a unit that detonates on every turn but doesn't destroy itself
> when it detonates. Then the detonation effect could cause damage to
> nearby units and potentially even modify terrain. I'm not sure how I'd go
> about making it move in a storm-like way, although I think maybe it could
> be made to be blown around by the existing "wind" code.
To the best of my knowledge, the wind code acts as an impediment to
movement and not a driver for it. But, it would be interesting to extend
so that it could be a motivator as well. Some of the restructuring of
the ACP computations that I did a while back ago should help in this regard.
> I was actually already thinking of something very similar to model Project
> Pluto - that's a remote-controlled supersonic airplane powered by an
> unshielded fission reactor, so that it kills anything it flies near. It
> was a real-life design (thankfully never built) but used to good advantage
> in fiction here: http://www.infinityplus.co.uk/stories/colderwar.htm
Neat little story. I see the author borrowed from Lovecraft in places.
Of course, one problem I have with nuclear-powered aircraft and
spacecraft is the cooling aspect. If you're dumping 60% to 70% of the
energy due to the efficiency of your "engine", all that energy has got
to go somewhere. But, I digress.... Now that I took the time to read the
story, I probably won't be able to get a new Windows installer and
source tarball for Xconq ready this evening. Oh well, it was a fun
little read.
Eric
next prev parent reply other threads:[~2004-09-20 2:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-19 23:17 Lincoln Peters
2004-09-19 23:32 ` mskala
2004-09-20 0:24 ` Eric McDonald
2004-09-20 0:30 ` Andreas Bringedal
2004-09-20 1:33 ` mskala
2004-09-20 2:35 ` Lincoln Peters
2004-09-21 0:43 ` Eric McDonald [this message]
2005-01-04 19:30 ` Weather tidbit mskala
2004-09-20 0:32 ` Using terrain coatings and existing code to model topography, weather, and vegetation Lincoln Peters
2004-09-20 0:45 ` D. Cooper Stevenson
2004-09-19 23:44 ` Coatings Eric McDonald
2004-09-20 0:45 ` Coatings Lincoln Peters
2004-09-20 0:58 ` Coatings Elijah Meeks
2004-09-21 2:09 ` Coatings 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=414E41E2.2030502@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=mskala@ansuz.sooke.bc.ca \
--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).