On Sat, 15 Oct 2011 08:53:45 + (UTC)
Martin Spott wrote:
> I think the only solution is to make GPC obsolete - either by replacing
> GPC by something different but functional equivalent or "simply" (TM ;-)
> by avoiding any polygon clipping in 'fgfs-construct' overall.
For what it's worth...
Hi Scenery
Here I provide converted and clipped Alaska elevation data (2arc
seconds) from NED USGS, for testing and developing purposes. The
original data is distributed from NED in ArcGIS format, I needed to
convert to USGSDEM format to create a new relief for my map. Maybe this
will be usefu
The 'bad' nodes are points that are co linear with a previous segment on the
same contour. When this happens, the even-odd algorithms used for clipping
only see one intersection instead of two. So, as a scanline is evaluated,
if we were currently outside a poly, we would then determine we were in
On Sun, Oct 16, 2011 at 7:22 AM, Peter Sadrozinski wrote:
> The 'bad' nodes are points that are co linear with a previous segment on
> the same contour. When this happens, the even-odd algorithms used for
> clipping only see one intersection instead of two. So, as a scanline is
> evaluated, if w
Hi,
I started splitting fgdata this morning. Created a project to store FlightGear
aircraft repositories,
under https://gitorious.org/flightgear-aircraft
More details are available on the wiki:
http://wiki.flightgear.org/FlightGear_Git:_splitting_fgdata
For some reason, this splitting s
On Sun, 16 Oct 2011, Gijs de Rooy wrote:
> Hi,
>
> I started splitting fgdata this morning. Created a project to store
> FlightGear aircraft repositories,
> under https://gitorious.org/flightgear-aircraft
>
> More details are available on the wiki:
> http://wiki.flightgear.org/FlightGear_Git:_sp
Am 16.10.2011 16:14, schrieb Gijs de Rooy:
> For some reason, this splitting seems to takes forever on Windows (like
> 25 minutes for the 744),
> while Jorg managed to split the F-f16 in 90 seconds on Linux! Jorg will
> run a script (being Cedric's
> script, or some homemade combination) to split a
Hi Thorsten,
thanks for your reply!
> Time also depends on aircraft size / commit count.
Yeah I figured that out, but I cannot believe the 744 and F-16 are that
different there...
> Worst and longest operation is eventually filtering the repo to get rid of
> all the
> aircraft. With somethi
Flightgear already has such a system for scenery. You only download what
you want, or need. Very few users need scenery for the whole world.
Extending this concept to the bloated aircraft section of fgdata seems quite
logical.
I don´t think that anyone is talking about splitting apart the core
Am 16.10.2011 20:01, schrieb Alan Teeder:
> Flightgear already has such a system for scenery. You only download
> what you want, or need. Very few users need scenery for the whole
> world.
> Extending this concept to the bloated aircraft section of fgdata
> seems quite logical.
It's important tho
Jorg and Gijs are working on the new fgdata repo now.
Therefore the existing fgdata repo is frozen as of now - even commit
privileges are removed - hopefully permanently for the (historic) fgdata
repo.
They'll start a new (temporary) repository. Once the new repo is all
setup and working as exp
Hi Thorsten,
One question: if we have our own local branches of the fgdata repository for
our own experimentation, will it be straightforward to hang these off the
new repository?
Thanks,
Curt.
On Sun, Oct 16, 2011 at 2:31 PM, ThorstenB wrote:
> Jorg and Gijs are working on the new fgdata rep
I guess that the aircrafts will just end up "deleted" in the next pull, leaving
the rest of FGDATA untouched. However, FGFS already supports a different path
for aircrafts, so it should be pretty simple to get everything running as
usual. Just copy the planes to another folder before the next p
Am 16.10.2011 23:30, schrieb Curtis Olson:
> One question: if we have our own local branches of the fgdata repository
> for our own experimentation, will it be straightforward to hang these
> off the new repository?
Simple answer: no. :-(
Since we really want to reduce the repository size - that
14 matches
Mail list logo
