James,
while I'm pretty much in favour of spatial indices, note that a lot of work in
that direction has been done already. As far as I know, Mathias Fröhlich has
written a general templated spatial index for simgear. I've the code with me,
but haven't found time to look at it yet (Sorry
On 16 Aug 2008, at 09:50, Thomas Förster wrote:
while I'm pretty much in favour of spatial indices, note that a lot
of work in
that direction has been done already. As far as I know, Mathias
Fröhlich has
written a general templated spatial index for simgear. I've the code
with me,
On 16 Aug 2008, at 11:37, Melchior FRANZ wrote:
ftp://ftp.uni-duisburg.de/FlightGear/Misc_maf/SGHTMMap-20060223/SGHTMMap-first-take.diff
Mathias will know more about it. :-)
Gave this a quick eyeball and it seems pretty nice - and
straightforward to integrate with my proposed base
On ven 15 août 2008, Alexis Bory - xiii wrote:
Erik Hofman wrote:
Hi,
Ever since I switched to the CVS version of FlightGear I wondered
whether the black-out behavior really is that realistic . Although I
never experienced it I couldn't imagine this would happen in real
life, at
As you may have noticed, Erik has recently overhauled (or rather
rewritten) xmlgrep. That's a fast utility for finding properties
in an XML file. It works with any XML file, not just our internal
PropertyList flavor.
In many cases a simple recursive grep isn't good enough. If you
do a simple
--- On Sat, 16/8/08, gerard robin wrote:
Coming back to the Erik, Alexis remark and my crazy first
answer.
Won't it be possible,
to include in the Cockpit view parameters the additional
parameters delay
which gives the delay for 5g blackout and 9 g blackout ?
All the code calculating
On sam 16 août 2008, Stuart Buchanan wrote:
--- On Sat, 16/8/08, gerard robin wrote:
Coming back to the Erik, Alexis remark and my crazy first
answer.
Won't it be possible,
to include in the Cockpit view parameters the additional
parameters delay
which gives the delay for 5g
On 08/15/2008 06:53 PM, James Turner wrote:
If you could enumerate the issues here, in a new thread, that'd be
interesting.
Here's a start:
*) There should be false localizer courses abeam the antenna, as
there are in real life. This is implemented in the _Sport Model_
in navradio.cxx
*)
'FGPositioned' . I'll buy a beer/beer-substitute for
anyone who comes up with a shorter, more meaningful class name.
How about FGSite???
-- It's shorter.
-- Also in this context site is a noun, which seems preferable to
adjectives such as positioned or located. [The
Attached patch refactors the KLN89 code to use the same navaid / fix /
airport storage as the rest of FG - instead of copying each (large)
list when the instrument is initialised. This gets rids of the
_waypoints member of DCLGPS - the waypoint class is still used in the
internal
James Turner wrote:
So, I actively *want* the base class. It allows replacing various
'type-testing' code with a single unified enum, which cleans up
various other places - right now there's code that is looking at
FGNavRecord's type directly (which is a integer code from Robin's DB),
John Denker wrote:
I don't know what the 'Sport Model' is, can you elaborate?
A summary of _Sport Model_ features can be found here:
http://www.av8n.com/fly/fgfs/README.sport.model
Sport Model was last updated to CVS FlightGear over a year ago. Do you have any
plans to update it to
Traditionally, the three main sources of FlightGear users' joy (TM)
are tightly coupled together:
The Base Package depends on the Sim-/FlightGear source mainly because
aircraft features are being developed in sync with the available FDM-
and rendering facilities. The Scenery on the other hand
On 08/16/2008 03:32 PM, Tim Moore wrote:
Sport Model was last updated to CVS FlightGear over a year ago. Do you have
any
plans to update it to current CVS?
I could be persuaded.
Do you think it would be helpful?
-
14 matches
Mail list logo
