2,732
edits
Red Leader (talk | contribs) m (Update {{func link}} form) |
|||
(4 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{Newsletter-header|October 2016}} | {{Newsletter-header|October 2016}} | ||
<div style="border-bottom:3px double #BBB;"> | <div style="border-bottom:3px double #BBB;"> | ||
Line 14: | Line 12: | ||
| valign="top" width="33%" | | | valign="top" width="33%" | | ||
{{Newsletter-cover-header|In the hangar}}<br> | {{Newsletter-cover-header|In the hangar}}<br> | ||
[[#MBB | [[#MBB/Kawasaki BK 117|MBB/Kawasaki BK 117]]<br> | ||
[[#2016 Camaro SS | [[#2016 Camaro SS|2016 Camaro SS]]<br> | ||
{{Newsletter-cover-header|Scenery Corner}}<br> | {{Newsletter-cover-header|Scenery Corner}}<br> | ||
[[# | [[#New experimental terrain engine|New experimental terrain engine]]<br> | ||
| valign="top" width="33%" | | | valign="top" width="33%" | | ||
{{Newsletter-cover-header|Contributing}}<br> | {{Newsletter-cover-header|Contributing}}<br> | ||
Line 33: | Line 31: | ||
|author = chris_blues | |author = chris_blues | ||
|date = Oct 4th, 2016 | |date = Oct 4th, 2016 | ||
}}</ref> Some details about the airport can be found [https://forum.flightgear.org/viewtopic.php? | }}</ref> Some details about the airport can be found [https://forum.flightgear.org/viewtopic.php?p=295274#p295274 here]. | ||
=== Git multimail script updated === | === Git multimail script updated === | ||
Line 82: | Line 80: | ||
}}</ref> However, performance tests indicate that the cause of the bottleneck is the huge amount of [[Property Tree|property]] manipulation involved during each update, ''after'' the actual calculations have been completed. This has also been shown to be a problem for any very complex Canvas. | }}</ref> However, performance tests indicate that the cause of the bottleneck is the huge amount of [[Property Tree|property]] manipulation involved during each update, ''after'' the actual calculations have been completed. This has also been shown to be a problem for any very complex Canvas. | ||
Some ways to help reduce bottlenecks include using {{func link|getprop}}/{{func link|setprop}} instead of [[Nasal library/props|props.nas APIs]] and using variables instead of properties where possible.<ref>{{cite web | Some ways to help reduce bottlenecks include using {{func link|getprop()}}/{{func link|setprop()}} instead of [[Nasal library/props|props.nas APIs]] and using variables instead of properties where possible.<ref>{{cite web | ||
|url = https://sourceforge.net/p/flightgear/mailman/message/30724363/ | |url = https://sourceforge.net/p/flightgear/mailman/message/30724363/ | ||
|title = <nowiki>Re: [Flightgear-devel] Nasal props API relative path support</nowiki> | |title = <nowiki>Re: [Flightgear-devel] Nasal props API relative path support</nowiki> | ||
Line 96: | Line 94: | ||
[[File:Canvas-ND-live-streaming-via-httpd.png|thumb|Screenshot showing a [[NavDisplay]]) streamed to Mozilla Firefox]] | [[File:Canvas-ND-live-streaming-via-httpd.png|thumb|Screenshot showing a [[NavDisplay]]) streamed to Mozilla Firefox]] | ||
ThomasS has created a patch for FlightGear for downloading any [[Canvas]] image from a running FlightGear process via HTTP.<ref>{{cite web | ThomasS has created a patch for FlightGear for downloading any [[Canvas]] image from a running FlightGear process via HTTP.<ref>{{cite web | ||
|url = https://forum.flightgear.org/viewtopic.php? | |url = https://forum.flightgear.org/viewtopic.php?p=296627#p296627 | ||
|title = Re: Canvas remote drawing | |title = Re: Canvas remote drawing | ||
|author = ThomasS | |author = ThomasS | ||
Line 107: | Line 105: | ||
== In the hangar == | == In the hangar == | ||
=== MBB | === MBB/Kawasaki BK 117 === | ||
User {{usr|HHS}}, the author of the [[Eurocopter EC135|Eurocopter EC135 P2]], [[EC130|Eurocopter EC130 B4]] and [[Cessna 182S|Cessna 182S Skylane]] is trying to the '''[[MBB Bk 117|MBB/Kawasaki BK 117]]''' into FlightGear. Unfortunately time is limited, so he will need help. | |||
When you have some spare time | When you have some spare time, are interested in helicopters, and always wished to improve things, you might want to apply for this job. Find out more on the [[MBB Bk 117|wiki page]]. | ||
=== 2016 Camaro SS | === 2016 Camaro SS === | ||
Auskunst is | Auskunst is seeking help to improve the handling of his '''2016 Camaro SS''' and another future automobile project. If you have experience in tweaking [[YASim]] [[FDM]]s, you can find out more [https://bulldogrs.wordpress.com/2016/10/16/help-request-1-0-yasim-fdm-expert/ here]. | ||
== Scenery corner == | == Scenery corner == | ||
=== | === New experimental terrain engine === | ||
psadro_gm has the | psadro_gm has been working on an experimental terrain engine. It works by using shaders and raster images to form the terrain. As of 10/2016, it allows for terrain generation on-the-fly and changes in the level of detail (LOD).<ref>{{cite web | ||
|url = https://forum.flightgear.org/viewtopic.php?p=295882#p295882 | |||
|title = Re: Next-generation scenery generating? | |||
|author = psadro_gm | |||
|date = Oct 1st, 2016 | |||
|added = Oct 1st, 2016 | |||
|script_version = 0.40 | |||
}}</ref> If the does get integrated fully, it will render [[TerraGear]] obsolete. However, there is still a lot of development work to do. The below videos show the change in LOD as one flies closer to the terrain. | |||
''To learn more, see [[Experimental terrain engine]]…'' | |||
{{#ev:youtube|-eWEB0-j7zk}} | |||
{{#ev:youtube|v9M2La8ZN1U}} | |||
== Contributing == | == Contributing == | ||
Line 196: | Line 165: | ||
If you want to participate in the screenshot contest of November 2016, you can submit your candidate to [https://forum.flightgear.org/viewtopic.php?f=19&t=30902 this] forum topic. Be sure to see the [https://forum.flightgear.org/viewtopic.php? | If you want to participate in the screenshot contest of November 2016, you can submit your candidate to [https://forum.flightgear.org/viewtopic.php?f=19&t=30902 this] forum topic. Be sure to see the [https://forum.flightgear.org/viewtopic.php?p=297955#p297955 first post] for participation rules. For purposes of convenience and organization, after all the entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there. Once the voting has finished, the best screenshot will be presented in the Newsletter edition of November 2016. | ||
{{Appendix}} | {{Appendix}} |