On Jan 7, 2008 9:05 PM, LeeE <[EMAIL PROTECTED]> wrote:
>
> More information is helpful & useful - thanks.
>
> Yeah - script based routines for things like fuel handling doesn't
> seem right but Nasal, because of the timer functions, is
> effectively real-time - it's just a question of resolution - for
> fuel handling 1/3 sec seems reasonable.
>
> Not @ you John, but the bottom line regarding this bug is that four
> fuel tanks nodes are created by default but they're not fully
> populated when they are created - they cannot be. The fuel tank
> nodes cannot be fully populated until the fdm config is parsed
> because the number of fuel tanks, and their capacities, depends
> upon each individual aircraft.
>
> I can see how it may be necessary to declare a single initial fuel
> tank node as a template but declaring four seems irrational.
>
> The best hits I found in the source, having found nothing in the
> config data, were those two bits of code I pasted above but if they
> are not relevant to the problem then we need to look elsewhere.
>
> For sure, four incomplete fuel tank nodes are _not_ being created by
> magic:)
>
> Sorry to all for being a nag but it is a bit of a fundamental bug.
>
One possibility ... if you have a --native-fdm= option, it is blindly
grabbing data from 1 - MAX_TANKS (which is currently 4). So that could be
creating the nodes if they don't exist so it can fill the data into the
structure.
Regards,
Curt.
--
Curtis Olson: http://baron.flightgear.org/~curt/
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
