Re: [Flightgear-devel] FGFS Externals

[Alex P. <ale...@ie...>]

> (Not so good news)
> If you look at the code modules in External.cxx in the FDM directory you
> will see only placeholders,
> while the other models are"busy" exchanging data structures with Simgear. If
> the "external" option is
> envoked (see the fg_init function) then it would seem reasonable the data
> exchange would occur here.
> So broadcast works at the lower levels, the "cookie crumb trail" ends at
> External - nothing comes in and
> nothing goes out.

It isn't clear from your text; there may be a misunderstanding here.

The fdm=external is specifically present to force the system to run completely
without an FDM.  That's why there are only placeholders.  On the master system,
you must not use this option, in order that there is an FDM somewhere on your
network of computers!

The --native option is used to emit the fdm data (as you observed) and on
receipt is supposed to smear it on top of the existing fdm data structure,
completely ignoring all the usual method calls.

So, the fact that you're observing the packets travel (and arrive) suggests
that there is something about the way that the smearing is done, that might
not be working under Windows (but does under Linux).