Curtis Olson wrote:
> My recollection is that the "original" fgfs-construct created any shared
> edges that weren't already created. So if free standing tile was created
> before any of its neighbors, all the shared edges (and corners) should be
> created: N, S, E, and W.
>
> If that's not the case, then perhaps I'm misunderstanding your comments, or
> something got changed in the code along the way.
>
> Note that if you march along creating tiles in regular strips, then after
> you've completely one row, and after you've completed the first tile of the
> next row, then each new tile would create just two new edges (so perhaps
> that is what you are seeing?)
A agree with all of the above. Creating all four edges for a stand-
alone tile sounds reasonable and creating just N/E when S/W are
available isn't that bad either. Anyhow, as far as I understand,
"fgfs-construct" was made for a workflow where _at_minimum_ two new
edges are being created with a new tile.
It's missing the feature to smoothly align a tile with a surrounding
box of four edges which are given from a previous terrain build.
Trying to insert a single tile, or a chunk of just a few tiles
connected tiles results in strange artifacts in almost every second
case.
Cheers,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
