Hi,
Some discussions have already taken place on JSBsim devel mailing list
regards communication between modules of flightgear.
My thoughts are that flightgear divides naturally into four major
sub-system modules:
a) FDM (jsbsim is already standalone)
b) cockpit input and output (ie
Hi Jim,
Jim Campbell wrote:
Some discussions have already taken place on JSBsim devel mailing list
regards communication between modules of flightgear.
Indeed, the idea of cutting FlightGear into modules is not a new one
and has been floating around way before this nice new arcitecture
paper
Martin Spott wrote:
Hi Jim,
Jim Campbell wrote:
Some discussions have already taken place on JSBsim devel mailing list
regards communication between modules of flightgear.
Indeed, the idea of cutting FlightGear into modules is not a new one
and has been floating around way before
Harald JOHNSEN schreef:
Martin Spott wrote:
Hi Jim,
Jim Campbell wrote:
Some discussions have already taken place on JSBsim devel mailing list
regards communication between modules of flightgear.
Indeed, the idea of cutting FlightGear into modules is not a new
Harald JOHNSEN wrote:
One should not forget that FG has allready some networking capacity.
This alone has allready allowed ppl to split fdm and rendering on
several machines. Perhaps there is something to reuse here.
Well, we've been driving two 'external' displays on last years LinuxTag
Martin Spott schreef:
Well, we've been driving two 'external' displays on last years LinuxTag
exhibition using the 'generic' protocol. We were surprised to encounter
a significant performance hit on the master machine serving two clients
at 20 Hz. Throttling the thing down to 10 Hz made the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Martin Spott wrote:
Personally I think some thing like distributed shared memory might fill
the gap. I've been doing some literature research on this topic several
years ago, the idea looks pretty promising and different OpenSource
7 matches
Mail list logo
