20,741
edits
FlightGear Newsletter July 2014: Difference between revisions
Jump to navigation
Jump to search
m
.. fix up a few HTML tags as per User_talk:Hooray#FlightGear_Newsletter_July_2014.23FGCanvas_Updates - however: a newsletter is edited once, and then locked - so doesn't exactly need "maintenance", so we could do without making a fuss here ...
(New version is approaching) |
m (.. fix up a few HTML tags as per User_talk:Hooray#FlightGear_Newsletter_July_2014.23FGCanvas_Updates - however: a newsletter is edited once, and then locked - so doesn't exactly need "maintenance", so we could do without making a fuss here ...) |
||
| Line 40: | Line 40: | ||
The stable release is due around August 17. See our [[release plan]] for details on the release procedure. | The stable release is due around August 17. See our [[release plan]] for details on the release procedure. | ||
=== FGCanvas Updates === | === FGCanvas Updates === | ||
[[File:Dedicated-aircraft-subsystem-group-for-fgcanvas.png|600px|thumb|checking how difficult it would be to put all aircraft related subsystems (fdm, replay, history, controls etc) into a single SGSubsystemGroup named "main-aircraft" to easily make the whole shebang optional using a single --prop for "FGCanvas" use, but also to check if it's feasible to prepare things for later reuse by the AI traffic system (for AI traffic that uses actual FDMs, APs and RMs - but also so that things are affected by the environment) , and it's actually working - even though reset/re-init is obviously hard-coded currently, which I am breaking by shuffling around subsystems, but as long as each SGSubsystemGroup implements the full SGSubsystem interface (postinit, reinit, shutdown etc), this could help clean up fg_init.cxx quite considerably [http://forum.flightgear.org/viewtopic.php?f=71&t=23499]]] | [[File:Dedicated-aircraft-subsystem-group-for-fgcanvas.png|600px|thumb|checking how difficult it would be to put all aircraft related subsystems (fdm, replay, history, controls etc) into a single SGSubsystemGroup named "main-aircraft" to easily make the whole shebang optional using a single --prop for "FGCanvas" use, but also to check if it's feasible to prepare things for later reuse by the AI traffic system (for AI traffic that uses actual FDMs, APs and RMs - but also so that things are affected by the environment) , and it's actually working - even though reset/re-init is obviously hard-coded currently, which I am breaking by shuffling around subsystems, but as long as each SGSubsystemGroup implements the full SGSubsystem interface (postinit, reinit, shutdown etc), this could help clean up fg_init.cxx quite considerably [http://forum.flightgear.org/viewtopic.php?f=71&t=23499]]] | ||
| Line 54: | Line 53: | ||
|title=<nowiki>FGCanvas Experiments & Updates</nowiki> | |title=<nowiki>FGCanvas Experiments & Updates</nowiki> | ||
|author=<nowiki>Hooray</nowiki> | |author=<nowiki>Hooray</nowiki> | ||
|date=<nowiki>Sun Jul 06</nowiki> | |date=<nowiki>Sun Jul 06 2013</nowiki> | ||
}} | }} | ||
}} | }} | ||
| Line 65: | Line 64: | ||
|title=<nowiki>Re: FSWeekend 2010</nowiki> | |title=<nowiki>Re: FSWeekend 2010</nowiki> | ||
|author=<nowiki>zakalawe</nowiki> | |author=<nowiki>zakalawe</nowiki> | ||
|date=<nowiki>Tue Nov 02</nowiki> | |date=<nowiki>Tue Nov 02 2010</nowiki> | ||
}} | }} | ||
}} | }} | ||
{{FGCquote | {{FGCquote | ||
|Since then, we made some first FGCanvas experiments, and things proved to be fairly tricky, because many C++ subsystems were not exactly easy to make entirely optional, and because of all the implicit assumptions in Nasal code that is unconditionally-loaded from $FG_ROOT/Nasal, and which assumes to have a full session up and running: | |Since then, we made some first FGCanvas experiments, and things proved to be fairly tricky, because many C++ subsystems were not exactly easy to make entirely optional, and because of all the implicit assumptions in Nasal code that is unconditionally-loaded from $FG_ROOT/Nasal, and which assumes to have a full session up and running: | ||
{{cquote|Yeah, the stand alone mode won't be to easy. Maybe for now we should use a powerful enough computer which can also run the unneeded parts Separating the parts will be very important, not only for FGCanvas...}} | {{cquote|Yeah, the stand alone mode won't be to easy. Maybe for now we should use a powerful enough computer which can also run the unneeded parts Separating the parts will be very important, not only for FGCanvas...}} | ||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=214206#p214206 | |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=214206#p214206 | ||
|title=<nowiki>FGCanvas Experiments & Updates</nowiki> | |title=<nowiki>FGCanvas Experiments & Updates</nowiki> | ||
|author=<nowiki>Hooray</nowiki> | |author=<nowiki>Hooray</nowiki> | ||
|date=<nowiki>Sun Jul 06</nowiki> | |date=<nowiki>Sun Jul 06 2013</nowiki> | ||
}} | }} | ||
}} | }} | ||
{{FGCquote | {{FGCquote | ||
|Fast forward a year later, many of those show stoppers have already been resolved, mainly thanks to the work done by Zakalawe and TheTom, who've both been working on reset&re-init, but also overall better run-time re-initialization support, as can be seen in the screen-shot below: | |Fast forward a year later, many of those show stoppers have already been resolved, mainly thanks to the work done by Zakalawe and TheTom, who've both been working on reset&re-init, but also overall better run-time re-initialization support, as can be seen in the screen-shot below: [[FGCanvas]] | ||
[[File:Patching-fg-3.2-to-make-more-subsystems-optional.png|250px]] | |||
[[FGCanvas]] | |||
[[File:Patching-fg-3.2-to-make-more-subsystems-optional.png|250px]] | Most subsystems still running in the screen shot shown here can be considered to be essential now, the only remaining subsystems that still need to be decoupled are: | ||
Most subsystems still running in the screen shot shown here can be considered to be essential now, the only remaining subsystems that still need to be decoupled are: | * flight (FDM) | ||
* scenery (tile manager, ephemeris) | |||
* view manager | |||
* lighting | |||
* terrasync | |||
Otherwise, it's mostly Nasal code in $FG_ROOT/Nasal where dependencies need to be better established and formalized to get rid of implicit assumptions regarding availability of certain subsystems (e.g. view.nas) | Otherwise, it's mostly Nasal code in $FG_ROOT/Nasal where dependencies need to be better established and formalized to get rid of implicit assumptions regarding availability of certain subsystems (e.g. view.nas) | ||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=214206#p214206 | |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=214206#p214206 | ||
|title=<nowiki>FGCanvas Experiments & Updates</nowiki> | |title=<nowiki>FGCanvas Experiments & Updates</nowiki> | ||
|author=<nowiki>Hooray</nowiki> | |author=<nowiki>Hooray</nowiki> | ||
|date=<nowiki>Sun Jul 06</nowiki> | |date=<nowiki>Sun Jul 06 2014</nowiki> | ||
}} | }} | ||
}} | }} | ||
| Line 108: | Line 103: | ||
|title=<nowiki>FGCanvas Experiments & Updates</nowiki> | |title=<nowiki>FGCanvas Experiments & Updates</nowiki> | ||
|author=<nowiki>Hooray</nowiki> | |author=<nowiki>Hooray</nowiki> | ||
|date=<nowiki>Sun Jul 06</nowiki> | |date=<nowiki>Sun Jul 06 2014</nowiki> | ||
}} | }} | ||
}} | }} | ||
| Line 117: | Line 112: | ||
|title=<nowiki>Re: FGCanvas Experiments & Updates</nowiki> | |title=<nowiki>Re: FGCanvas Experiments & Updates</nowiki> | ||
|author=<nowiki>Philosopher</nowiki> | |author=<nowiki>Philosopher</nowiki> | ||
|date=<nowiki>Sun Jul 06</nowiki> | |date=<nowiki>Sun Jul 06 2014</nowiki> | ||
}} | }} | ||
}} | }} | ||
=== A Canvas based GNS 530 GPS === | === A Canvas based GNS 530 GPS === | ||
After a long hiatus (3 years!) forum user cbendele felt like doing some FlightGear aircraft modeling again. Three years ago, when he started the panel for his Bo, he could not find a nice, modern, panel mount IFR GPS. The King GPS we have is ancient, and the Garmin 196, while nicely modelled, Is a VFR handheld. So he decided to start with this: | After a long hiatus (3 years!) forum user cbendele felt like doing some FlightGear aircraft modeling again. Three years ago, when he started the panel for his Bo, he could not find a nice, modern, panel mount IFR GPS. The King GPS we have is ancient, and the Garmin 196, while nicely modelled, Is a VFR handheld. So he decided to start with this: | ||