Unifying the 2D rendering backend via canvas: Difference between revisions

Jump to navigation Jump to search
Line 47: Line 47:


{{cquote|Moving the HUD to use the Canvas would be a great step from my point of view, since it and 2D panels (which I am happy to write the convert for!) are the last places besides the UI which make raw OpenGL calls, and hence would benefit from moving to the Canvas (and thus, to use OSG internally)|[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38629.html James Turner]}}
{{cquote|Moving the HUD to use the Canvas would be a great step from my point of view, since it and 2D panels (which I am happy to write the convert for!) are the last places besides the UI which make raw OpenGL calls, and hence would benefit from moving to the Canvas (and thus, to use OSG internally)|[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38629.html James Turner]}}
{{FGCquote
|1= One solution would be to port the HUD to use osgText : that’s actually somewhat doable because it’s already centralised, but rather high risk close to release.
|2= {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/34769314/
  | title  = <nowiki>Re: [Flightgear-devel] Corrupted HUD / 2D panel text</nowiki>
  | author = <nowiki>James Turner</nowiki>
  | date  = Jan 15th, 2016
  | added  = Jan 15th, 2016
  | script_version = 0.23
  }}
}}


<references/>
<references/>

Navigation menu