FlightGear high-level architecture support: Difference between revisions

FlightGear high-level architecture support (view source)

754 bytes added , 25 April 2013

m

20,741

edits

@@ Line 22: / Line 22: @@
 {{cquote|There's a larger issue here, that 'soon' (likely during the summer) I want to start restructuring the codebase into multiple processes, so we can support different rendering architectures (and use multiple CPUs) better. That's Mathias Fröhlich's HLA/RTI work, and indeed he has done the recent work on extending fgviewer to test changes to the current terrain system. <ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39693.html |title=Generating ground textures on the fly?|author=James Turner |date=Mon, 11 Mar 2013 15:24:07 -0700}}</ref>|James Turner}}
+{{cquote|concerning the larger issue of different rendering pipelines / approaches, my opinion is, and remains, that the long-term solution is separate viewer codebases - while a plethora would be bad, we would already benefit from a 'fixed-function, no shaders' renderer codebase distinct from a Rembrandt renderer and modern, forward-rendering OpenGL 3.x pipeline. This needs the  viewer to be cleanly split out from the simulation backend, via HLA, which is exactly what Mathias (and soon, myself) are working towards, but slowly.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39922.html |title=Atmospheric Light Scattering|author=James Turner |date=Thu, 25 Apr 2013 08:09:08 -0700}}</ref>|James Turner}}
 <references/>