FlightGear Newsletter April 2015: Difference between revisions

Jump to navigation Jump to search

FlightGear Newsletter April 2015 (view source)

Revision as of 09:25, 19 April 2015

132 bytes added ,  19 April 2015
More de-quoting
(Copy edit, needs dequoting)
(More de-quoting)
Line 8: Line 8:
{{Newsletter-cover-header|Development news}}<br/>
{{Newsletter-cover-header|Development news}}<br/>
[[#FlightGear now lives at SourceForge|FlightGear now lives at SourceForge]]<br/>
[[#FlightGear now lives at SourceForge|FlightGear now lives at SourceForge]]<br/>
[[#OpenRTI move|OpenRTI move]]<br/>
[[#Spaceflight|Spaceflight]]<br/>
[[#Spaceflight|Spaceflight]]<br/>
[[#Understanding Rembrandt and VSync|Understanding Rembrandt and VSync]]<br/>
[[#Understanding Rembrandt and Vsync|Understanding Rembrandt and Vsync]]<br/>
[[#SVG transparency|SVG transparency]]<br/>
[[#SVG transparency|SVG transparency]]<br/>
  | valign="top" width="33%" |
  | valign="top" width="33%" |
Line 15: Line 16:
[[#Boeing 707 liveries|Boeing 707 liveries]]<br/>
[[#Boeing 707 liveries|Boeing 707 liveries]]<br/>
{{Newsletter-cover-header|Scenery Corner}}<br/>
{{Newsletter-cover-header|Scenery Corner}}<br/>
[[#Belgium airports|Belgium airports]]<br/>
{{Newsletter-cover-header|Community News}}<br/>
{{Newsletter-cover-header|Community News}}<br/>
[[#FlightGear a featured project at SourceForge|FlightGear a featured project at SourceForge]]<br/>
[[#FlightGear: featured project at SourceForge|FlightGear: featured project at SourceForge]]<br/>
[[#FG Flights blog|FG Flights blog]]<br/>
[[#FG Flights blog|FG Flights blog]]<br/>
[[#New FGCom server maintainer|New FGCom server maintainer]]<br/>
[[#New FGCom server maintainer|New FGCom server maintainer]]<br/>
Line 28: Line 30:


== Development news ==
== Development news ==
{{FGCquote
  |Hi all, I have deleted the Gitorious OpenRTI repository in favor of the SourceForge repository that I already maintained since the original<br/>
berlios repository was closed.
To move your local clone over to the Sourceforge repository you can just set the URL of your remote repository to the new url. For the usual clone where the default remote repository is called 'origin', the command reads '''git remote set-url origin git://git.code.sf.net/p/openrti/OpenRTI'''
I hope that this one lasts a little longer ...
Greetings
Mathias
  |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33852792/
    |title=<nowiki>[Flightgear-devel] OpenRTI gitorious git repository deleted</nowiki>
    |author=<nowiki>Mathias Fröhlich</nowiki>
    |date=<nowiki>2015-04-16</nowiki>
  }}
}}
=== FlightGear now lives at SourceForge ===
=== FlightGear now lives at SourceForge ===
The move from Gitorious to SourceForge is now complete.  A historical read-only record will remain at [http://gitorious.org Gitorious.org], as well as other public locations.<ref>http://sourceforge.net/p/flightgear/mailman/message/33832698/</ref>  In addition, hooks have been added so that every commit to either the [http://sourceforge.net/p/flightgear/flightgear/ FlightGear], [http://sourceforge.net/p/flightgear/simgear/ SimGear] or [http://sourceforge.net/p/flightgear/fgdata/ FGData] repositories will (hopefully) send a message to the [http://sourceforge.net/p/flightgear/mailman/flightgear-commitlogs/ flightgear-commitlogs mailing list].<ref>http://sourceforge.net/p/flightgear/mailman/message/33827961/</ref>
The move from Gitorious to SourceForge is now complete.  A historical read-only record will remain at [http://gitorious.org Gitorious.org], as well as other public locations.<ref>http://sourceforge.net/p/flightgear/mailman/message/33832698/</ref>  In addition, hooks have been added so that every commit to either the [http://sourceforge.net/p/flightgear/flightgear/ FlightGear], [http://sourceforge.net/p/flightgear/simgear/ SimGear] or [http://sourceforge.net/p/flightgear/fgdata/ FGData] repositories will (hopefully) send a message to the [http://sourceforge.net/p/flightgear/mailman/flightgear-commitlogs/ flightgear-commitlogs mailing list].<ref>http://sourceforge.net/p/flightgear/mailman/message/33827961/</ref>
=== OpenRTI move ===
The OpenRTI project, maintained by Mathias Fröhlich, has been moved from Gitorious to [http://sourceforge.net/projects/openrti/?source=directory SourceForge].<ref>{{cite web
|url    = http://sourceforge.net/p/flightgear/mailman/message/33852792/
|title  = <nowiki>[Flightgear-devel] OpenRTI gitorious git repository deleted</nowiki>
|author = <nowiki>Mathias Fröhlich</nowiki>
|date  = April 16, 2015
}}</ref>  OpenRTI is an open-source {{Abbr|HLA|High-level architecture}}/{{Abbr|RTI|Run-time infrastructure}} implementation, used by FlightGear.  To move your local clone over to the Sourceforge repository, you can just set the URL of your remote repository to the new URL. Below is an example for the usual clone (where the default remote repository is called '''origin'''):
<syntaxhighlight lang="bash">
git remote set-url origin git://git.code.sf.net/p/openrti/OpenRTI
</syntaxhighlight>


=== Spaceflight ===
=== Spaceflight ===
Line 61: Line 58:
Modelers interested in realistic spaceflight are very welcome to come aboard and help taking FlightGear to the limits.
Modelers interested in realistic spaceflight are very welcome to come aboard and help taking FlightGear to the limits.


=== Understanding Rembrandt and VSync ===
=== Understanding Rembrandt and Vsync ===
{{FGCquote
Richard Harrison has been looking into Rembrandt to find the cause of unreasonably low frame rate.<ref>{{cite web
  |For the last few weeks I've been getting to grips with the way that deferred rendering works in an attempt to figure out why we don't get the frame rate that we should.
|url = http://sourceforge.net/p/flightgear/mailman/message/33671091/
 
|title = <nowiki>[Flightgear-devel] Deferred rendering (Rembrandt) performance</nowiki>
I've written up my findings here http://chateau-logic.com/content/deferred-rendering-rembrandt-performance
|author = Richard Harrison
|date = March 29, 2015
}}</ref>  To cut a long story short, he has found that {{Abbr|Vsync|Vertical synchronization}} is causing the problems.  After making some changes to the code so that he could turn Vsync on or off, he found that the following command line options provide a great increase in performance:
{{note|The first flag sets a custom property created during his tests; it isn't available in normal FlightGear.}}


It appears that VSync is causing problems; and I get a marked  improvement in deferred rendering performance (Rembrandt) using the following flags:
<syntaxhighlight lang="bash">
<code>
--prop:/sim/rendering/vsync-enable=false
—prop:/sim/rendering/vsync-enable{{=}}false —prop:/sim/frame-rate-throttle-hz{{=}}60
--prop:/sim/frame-rate-throttle-hz=60
</code>
</syntaxhighlight>


Without these flags I get 30 fps with nothing visible (/sim/rendering/draw-mask all false). With these flags I get 60 fps when drawing nothing which is what I'd expect.
These flags increased his frame rate from 30 fps to 60 fps (when drawing nothing).
What I'd like to know know is whether this makes a difference to anyone else - so I'd appreciate any test result FPS figures (with and without the flag) with graphics card and CPU posted here.


I didn't figure out if VSync can be turned off per camera; but I'm 99.9% certain that this is what VSync is causing to happen on my configuration.
You can read the full report at http://chateau-logic.com/content/deferred-rendering-rembrandt-performance.
  |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33671091/
    |title=<nowiki>[Flightgear-devel] Deferred rendering (Rembrandt) performance</nowiki>
    |author=<nowiki>Richard Harrison</nowiki>
    |date=<nowiki>2015-03-29</nowiki>
  }}
}}


See also [[FlightGear I/O Considerations#Understanding VSync|What is VSync?]].
See also [[FlightGear I/O Considerations#Understanding VSync|Understanding Vsync]].


=== SVG transparency ===
=== SVG transparency ===
Line 89: Line 82:


Currently, there is only support for the {{Func link|fill-opacity|ext=https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/fill-opacity}} and {{Func link|stroke-opacity|ext=https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/stroke-opacity}} properties, but there is a small bug if the value is 0.0.
Currently, there is only support for the {{Func link|fill-opacity|ext=https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/fill-opacity}} and {{Func link|stroke-opacity|ext=https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/stroke-opacity}} properties, but there is a small bug if the value is 0.0.
See commits [http://sourceforge.net/u/userid-1550991/flightgear/ci/7b71a8f361ce735372ed1cbacd7a2b66226d4e73/] and [http://sourceforge.net/u/userid-1550991/flightgear/ci/acb88337f2f31104752230cdc755143211a46ec5/].


{| align="center"
{| align="center"
! Before !! After
! Before !! After
|-
|-
| [[File:Be for SVG Transparent.png|400px|without SVG transparency]] || [[File:After SVG Transparent.png|400px|With SVG transparency]]
| [[File:Be for SVG Transparent.png|400px|Before patches]] || [[File:After SVG Transparent.png|400px|After patches]]
|}
|}


Line 106: Line 101:
* Trans European Airways
* Trans European Airways
* Belize Airways Ltd. (Nick Reimer, others by sanhozay).  
* Belize Airways Ltd. (Nick Reimer, others by sanhozay).  
See this [http://forum.flightgear.org/viewtopic.php?f=13&t=24144 forum post] for more information. Download the liveries [http://liveries.flightgear.org/aircraft.php?id=4 here].
See this [http://forum.flightgear.org/viewtopic.php?f=13&t=24144 forum post] for more information. You can download the liveries [http://liveries.flightgear.org/aircraft.php?id=4 here].


<gallery mode="packed">
<gallery mode="packed">
Line 119: Line 114:


== Scenery corner ==
== Scenery corner ==
=== Belgium airports ===
This month, various airports in Belgium are being populated with 3D buildings and shared models.  The source for most of the models is the Belgium Custom Scenery Project by [http://dvanmosselbeen.be David van Mosselbeen].
This month, various airports in Belgium are being populated with 3D buildings and shared models.  The source for most of the models is the Belgium Custom Scenery Project by [http://dvanmosselbeen.be David van Mosselbeen].


Line 189: Line 185:


=== FlightGear logos ===
=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (for example a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos.  And if you have some art skills, please don't hesitate to contribute with your own design creations.
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos.  And if you have some art skills, please don't hesitate to contribute with your own design creations.


=== Screenshots ===
=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release.  These should be of good quality, especially in content and technical image properties.  It is therefore recommended to use the best viable filter settings ([[antialiasing]], texture sharpening, etc.).  More info at [[Howto:Make nice screenshots]].
The FlightGear project always needs screenshots, which show features that were added since the last release.  These should be of good quality, especially in content and technical image properties.  It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.).  More info at [[Howto:Make nice screenshots]].


{{Appendix}}
{{Appendix}}
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/83643"

Navigation menu