3D Maps / defining one possible software approach

By james vassilakos ·

TML message #6274From bundle 514

Yesterday I wrote some guidelines for a computer software package that
could display 3d maps.

> 1. 3d/rotatable (obviously)
> 2. display name of the star-system beside the identifier on the map,
>    legibly, semi-regardless of the user's point of perspective.
> 3. use color and size to further distinguish stellar/system features.
> 4. incorporate an adjustable cartesian grid with numbering displayed.
> 5. IBM executable (assume SVGA or better)
> 6. Input data stored in TEXT file (this is important, because we need
>    to be able to write simple programs to generate this data, and it
>    would be nice to be able to hand-modify it with choice of editor).

One response, received this morning, is from [email removed]
who is actually considering taking on the project.

> Having read your message in the TML I though why not give it
> a go and write a 3d viewing program.

He went on about it being important to have pre-defined specs, which
I have to agree, would be important for such a project as this (I'm
used to programming simple things. This puppy is a monster my comparison.).
On this note, we got talking about data file format.

> I assume that stats for a planet will be something like
>
> <x,y,z> Name <UWP> etc
>
> Does this seem correct to you?

I'm forwarding my response to the list, since there may be others who are
thinking about the problem.

> More or less. The thing is that this type of tool will probably not be
> specifically for Traveller or any other SF-RPG. Hence, you don't need to
> have UWP in the usual sense. You should probably impliment something like:
>
> +xxxx +yyyy +zzzz Name_of_star_system_as_displayed_on_map Sz Cp Ci
>
> where +    is the sign of the coordinate
>       xxxx is x-coordinate
>       yyyy is y-coordinate
>       zzzz is z-coordinate
>       Name field should be as wide as the maximum size name you're willing
>            to display on the map
>       Sz   is Size of circle on map (circles are used to denote stars.
>             a circle with size=1 would be a point)
>       Cp   Color of perimeter (the color of the skin of the circle)
>       Ci   Color of interior
>
> So that each point has two colors (perimeter and interior) and a size.
> Of course, very small circles will look like points, and their two
> colors will be identical.
>
> But in this way, the users can illustrate their data any way they want,
> and it won't clutter the map with a bunch of confusing (and often
> inconsequential) symbols. If the user wants a blue interior to denote a
> terra-norm world, then that's what it means to her/him. If the user wants
> a blue interior to denote a hot-blue star, then it means that instead.
> Different attributes will be important to different people. It's best not
> to tie yourself down to a single UWP but instead keep the data based solely
> on the mechanism of the actual map (i.e. what color(s) and size is this
> "dot" going to have). In this way, as well, the program will be useable for
> a wider variety of RPGs.

Also, for anybody thinking about this stuff, Kerry Harrison
([email removed]) mentioned a program named "Outlander's
Starchart 3d" which is supposed to be available somewhere somehow.
I dunno yet, but talk to Kerry.

Anyway, if anybody makes any progress on this, please let the rest of
know what you're up to.

           _   /|       Jim Vassilakos
           \`o_O'       [email removed]
             ( )        [email removed]
              U         [email removed]
           Aachk!       (USA) [phone removed]