20,741
edits
Line 237: | Line 237: | ||
|script_version = 0.37 | |script_version = 0.37 | ||
}}</ref> | }}</ref> | ||
Realistically, if you want to sell a commercial aircraft, your customer base is going to be Flight Sim X, X-Plane, Prepar3D. You're simply not going to get any traction in the FlightGear ecosystem. It's not built for it. <ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35074166/ | |||
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared | |||
library, and what legislation issues would that ensue? </nowiki> | |||
|author = <nowiki> geneb </nowiki> | |||
|date = May 9th, 2016 | |||
|added = May 9th, 2016 | |||
|script_version = 0.37 | |||
}}</ref> | |||
Besides, OSG's scripting language support (lua) cannot access all the internals Nasal does, simply because there was no glue code implemented in FlightGear. So no properties for you and no access to internal function call which does Nasal provide. <ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35074133/ | |||
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared | |||
library, and what legislation issues would that ensue? </nowiki> | |||
|author = <nowiki> Erik Hofman </nowiki> | |||
|date = May 9th, 2016 | |||
|added = May 9th, 2016 | |||
|script_version = 0.37 | |||
}}</ref> | |||