Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G

Difference between revisions of "Canvas Issues"

From FlightGear wiki
Jump to: navigation, search
(White Square / No FBO)
(White Square / No FBO)
Line 11: Line 11:
 
   |date  =  Jan 30th, 2017  
 
   |date  =  Jan 30th, 2017  
 
   |added  =  Jan 30th, 2017  
 
   |added  =  Jan 30th, 2017  
 +
  |script_version = 0.40
 +
  }}</ref>
 +
 +
For example, reported on Intel GMA 3100, Intel G33/G31 Express Chipset Family<ref>{{cite web
 +
  |url    =  https://forum.flightgear.org/viewtopic.php?p=267596#p267596
 +
  |title  =  <nowiki> Having trouble with changing from 2.8.0.5 to 3.4.0 </nowiki>
 +
  |author =  <nowiki> Martien van der P. </nowiki>
 +
  |date  =  Dec 7th, 2015
 +
  |added  =  Dec 7th, 2015
 
   |script_version = 0.40  
 
   |script_version = 0.40  
 
   }}</ref>
 
   }}</ref>

Revision as of 08:44, 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]


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)[3]

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  (Feb 25th, 2017).  Re: White square error .