20,741
edits
Line 305: | Line 305: | ||
|title = <nowiki> Re: [Flightgear-devel] botom line: if i don't my aircraft to be | |title = <nowiki> Re: [Flightgear-devel] botom line: if i don't my aircraft to be | ||
subject to GPL FGAddon clauses </nowiki> | subject to GPL FGAddon clauses </nowiki> | ||
|author = <nowiki> Stuart Buchanan </nowiki> | |||
|date = May 10th, 2016 | |||
|added = May 10th, 2016 | |||
|script_version = 0.39 | |||
}}</ref> | |||
You could certainly run the FDM model externally and use one of the many Network I/O options in FlightGear to pass data back and forth. Quite a few research projects have done this in the past to use FlightGear as a visualiation tool. By extension you could do the same for scripting - have the scripting run externally and interact with FlightGear via one of these protocols.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35076187/ | |||
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared | |||
library, and what legislation issues would that ensue? </nowiki> | |||
|author = <nowiki> Stuart Buchanan </nowiki> | |author = <nowiki> Stuart Buchanan </nowiki> | ||
|date = May 10th, 2016 | |date = May 10th, 2016 |