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


Jump to: navigation, search

Canvas Issues

5,718 bytes added, 13:52, 25 February 2017
still needs to be added to the canvas navbar
{{Canvas Navigation}}
{{Canvas Navigation}}
== Critical / Bugs ==
=== White Square / No FBO ===
Regarding the Canvas related issues you are mentioning, those would seem to suggest that your GPU/driver is lacking support for features required for Canvas - which is exactly why we're asking people to provide '''complete''' bug reports, including their GPU make/model and OS/driver etc (see the red box at the top of the support forum)<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=217338#p217338
|title = <nowiki> Re: Some bugs or errors with the FG 3.2 RC 1 </nowiki>
|author = <nowiki> Hooray </nowiki>
|date = Aug 27th, 2014
|added = Aug 27th, 2014
|script_version = 0.40
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.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=304481#p304481
|title = <nowiki> Re: White square error </nowiki>
|author = <nowiki> zakalawe </nowiki>
|date = Jan 30th, 2017
|added = Jan 30th, 2017
|script_version = 0.40
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 to 3.4.0 </nowiki>
|author = <nowiki> Martien van der P. </nowiki>
|date = Dec 7th, 2015
|added = Dec 7th, 2015
|script_version = 0.40
on an old Intel graphics netbook, and while FG obviously doesn't work very well, some of the osg RTT demos actually DO work correctly. Besides, osgviewer itself, and even fgviewer, work well enough, with acceptable framerates/performance - so it would seem possible to optimie things a bit to also support such hardware.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=203409#p203409
|title = <nowiki> Re: Blank </nowiki>
|author = <nowiki> Hooray </nowiki>
|date = Mar 15th, 2014
|added = Mar 15th, 2014
|script_version = 0.40
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
please post your hardware specs as per the box at the top of the forum.
It seems that you are lacking some OpenGL support that is required by the new canvas system.
This has been recently reported at least once: [http://forum.flightgear.org/viewtopic.php?f=68&amp;t=20887&amp;hilit=canvas+fbo viewtopic.php?f=68&amp;t=20887&amp;hilit=canvas+fbo]
So please follow up with your exact hardware/software specs, including info from the HELP/ABOUT dialog.
And if you are affected by this, please consider filing a bug report so that we can look into it: [http://flightgear-bugs.googlecode.com/ http://flightgear-bugs.googlecode.com/]<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=195615#p195615
|title = <nowiki> Re: Blank </nowiki>
|author = <nowiki> Hooray </nowiki>
|date = Dec 5th, 2013
|added = Dec 5th, 2013
|script_version = 0.40
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]]
[[File:About dialog 2.10.png|250px]]
Likewise, this should affect any other FBO use-cases in FlightGear, including multi-camera setups (think Rembrandt)<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=305841#p305841
|title = <nowiki> Re: White square error </nowiki>
|author = <nowiki> Hooray </nowiki>
|date = Feb 25th, 2017
|added = Feb 25th, 2017
|script_version = 0.40
could the people getting "white canvases" please get in touch to test a patch ?
Basically, the idea is to check if FBO setup failed and try some more conservative alternatives like pbuffers or ARBs instead.
We can use PIXEL_BUFFER_RTT or PIXEL_BUFFER instead of FRAME_BUFFER_OBJECT: http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/2007-November/004790.html
Given that we're going to use Canvas in more and more placed, including the GUI, it would seem like a good idea to get this sorted obviously.
On the other hand, it is hard to troubleshoot this without being affected by the problem yourself :-)
it's not a new problem: http://www.mail-archive.com/flightgear-devel%40lists.sourceforge.net/msg20103.html<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=201515#p201515
|title = <nowiki> Re: Blank </nowiki>
|author = <nowiki> Hooray </nowiki>
|date = Feb 21st, 2014
|added = Feb 21st, 2014
|script_version = 0.40
== References ==

Navigation menu