Changes

Jump to navigation Jump to search
m
Better link about osgText not working in OSG > 3.4.2.
Line 90: Line 90:  
=== Canvas ===
 
=== Canvas ===
 
{{See also|Unifying the 2D rendering backend via canvas}}
 
{{See also|Unifying the 2D rendering backend via canvas}}
* currently osgText doesn't work under the ALS pipeline.  <ref>https://sourceforge.net/p/flightgear/mailman/message/37042335/</ref> one issue that seems to occur in a few places is missing text elements on cockpit devices ...  We all know the issue of osgText not working in OSG &gt; 3.4.2 for text-animations <ref>https://sourceforge.net/p/flightgear/mailman/message/37047266/</ref> We need to find a migration solution for osgText that works with Compositor and newer OSG versions <ref>https://sourceforge.net/p/flightgear/mailman/message/37047567/</ref> ... another option was creating a Canvas for each text animation, but creating a FBO for every small piece of text doesn't sound very performance-friendly. <ref>https://sourceforge.net/p/flightgear/mailman/message/37042457/</ref> We need to find some way to approximate with the old OSG text did<ref>https://sourceforge.net/p/flightgear/mailman/message/37042476/</ref>
+
* currently osgText doesn't work under the ALS pipeline.  <ref>https://sourceforge.net/p/flightgear/mailman/message/37042335/</ref> one issue that seems to occur in a few places is missing text elements on cockpit devices ...  There are [https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/1362c1cf-e0e7-3774-da92-63b2720aab7f%40gmail.com/#msg36702528 issues with osgText not working in OSG &gt; 3.4.2]. We need to find a migration solution for osgText that works with Compositor and newer OSG versions <ref>https://sourceforge.net/p/flightgear/mailman/message/37047567/</ref> ... another option was creating a Canvas for each text animation, but creating a FBO for every small piece of text doesn't sound very performance-friendly. <ref>https://sourceforge.net/p/flightgear/mailman/message/37042457/</ref> We need to find some way to approximate with the old OSG text did<ref>https://sourceforge.net/p/flightgear/mailman/message/37042476/</ref>
 
* [[Canvas_News#2D_Panels|Remove the 2D panel code in favour of Canvas]] (this requires completing some work to load 2D panel elements as Canvas, from XML) <ref>https://sourceforge.net/p/flightgear/mailman/message/36973988/</ref> (as of 06/2020,  Gaétan Allaert  is still working on the replacement of the 2D panel by canvas <ref>https://sourceforge.net/p/flightgear/mailman/message/37042351/</ref>) {{Progressbar|60}}<ref>https://sourceforge.net/u/gallaert/flightgear/ci/789f5bdbce10637222ffa25206938947fec4bc64/</ref>
 
* [[Canvas_News#2D_Panels|Remove the 2D panel code in favour of Canvas]] (this requires completing some work to load 2D panel elements as Canvas, from XML) <ref>https://sourceforge.net/p/flightgear/mailman/message/36973988/</ref> (as of 06/2020,  Gaétan Allaert  is still working on the replacement of the 2D panel by canvas <ref>https://sourceforge.net/p/flightgear/mailman/message/37042351/</ref>) {{Progressbar|60}}<ref>https://sourceforge.net/u/gallaert/flightgear/ci/789f5bdbce10637222ffa25206938947fec4bc64/</ref>
 
* Remove the C++ HUD in favour of Canvas-based version: this requires some kind of migration script or framework, so we have at least the default UFO HUD available <ref>https://sourceforge.net/p/flightgear/mailman/message/36973988/</ref>
 
* Remove the C++ HUD in favour of Canvas-based version: this requires some kind of migration script or framework, so we have at least the default UFO HUD available <ref>https://sourceforge.net/p/flightgear/mailman/message/36973988/</ref>
90

edits

Navigation menu