Canvas issues: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
Line 22: Line 22:
   |script_version = 0.40  
   |script_version = 0.40  
   }}</ref>
   }}</ref>
if in doubt, post more screenshots detailing exactly what you are doing, or even post a youtube video illustrating the problem<ref>{{cite web
  |url    =  https://forum.flightgear.org/viewtopic.php?p=281426#p281426
  |title  =  <nowiki> Re: No text in dialog boxes </nowiki>
  |author =  <nowiki> Hooray </nowiki>
  |date  =  Apr 3rd, 2016
  |added  =  Apr 3rd, 2016
  |script_version = 0.40
  }}</ref>





Revision as of 13:45, 25 February 2017

This article is a stub. You can help the wiki by expanding it.

Critical / Bugs

White Square / No FBO

The white square is the popup message / tooltip, shown via the Canvas. The texture or framebuffer used for the canvas isn't working. This seems to happen on some very old drivers.[1]

For example, reported on Intel GMA 3100, Intel G33/G31 Express Chipset Family[2]

if in doubt, post more screenshots detailing exactly what you are doing, or even post a youtube video illustrating the problem[3]


we talked about this issue a (long) while ago - and what would really be interesting is if people seeing this could also try one of the aircraft using other OD_gauge based avionics (navdisplay, agradar, wxradar etc) - because under the hood, this should be using the same OSG code - if those instruments work/display properly, it is likely that this issue can be fixed once and for all by looking at what the Canvas FBO/RTT setup code is doing differently compared to od_gauge based avionics using the same back-end. If I remember correctly, we also once posted patches telling OSG to use a non-FBO fallback - unfortunately nobody seeing this issue was able to follow up to test this. If in doubt, anybody seeing this, PLEASE post a screenshot showing your help/about dialog (and ideally your fgfs.log file): About dialog

Commonly used debugging tools#fgfs.log

About dialog 2.10.png

Likewise, this should affect any other FBO use-cases in FlightGear, including multi-camera setups (think Rembrandt)[4]

References

References
  1. zakalawe  (Jan 30th, 2017).  Re: White square error .
  2. Martien van der P.  (Dec 7th, 2015).  Having trouble with changing from 2.8.0.5 to 3.4.0 .
  3. Hooray  (Apr 3rd, 2016).  Re: No text in dialog boxes .
  4. Hooray  (Feb 25th, 2017).  Re: White square error .