20,741
edits
FlightGear Newsletter April 2015: Difference between revisions
Jump to navigation
Jump to search
→Development news
| Line 18: | Line 18: | ||
== Development news == | == Development news == | ||
=== Understanding Rembrandt and VSync === | |||
{{Note| | |||
{{FGCquote | |||
|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 framerate that we should. | |||
I've written up my findings here http://chateau-logic.com/content/deferred-rendering-rembrandt-performance | |||
It appears that vsync is causing problems; and I get a marked improvement in deferred rendering performance (Rembrandt) using the following flags: | |||
<code> | |||
—prop:/sim/rendering/vsync-enable{{=}}false —prop:/sim/frame-rate-throttle-hz{{=}}60 | |||
</code> | |||
Without these flags I get 30fps with nothing visible (/sim/rendering/draw-mask all false). With these flags I get 60fps when drawing nothing which is what I'd expect. | |||
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. | |||
|{{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> | |||
}} | |||
}} | |||
}} | |||
== In the hangar == | == In the hangar == | ||