Asking for help: Difference between revisions

Asking for help (view source)

Revision as of 23:16, 24 May 2014

1,527 bytes removed , 24 May 2014

→‎OpenGL related: moving troubleshooting info away

Bigstones

573

edits

@@ Line 25: / Line 25: @@
 People experiencing corrupted textures, should also see [[Troubleshooting graphics artifacts]]
-'''Note:''' While you should normally get to see something like "''direct rendering: Yes''" indicating working hardware acceleration, this doesn't have to be the case if you are running an OpenGL X server such as Xgl-still hardware acceleration may be working. However, it is important to realize that running OpenGL applications on top of current Xgl implementations may rather '''severely''' affect overall application performance, in fact FlightGear may be slowed down by a factor of 2.5 or even more, in addition more complex OpenGL features (such as multi-texturing and shaders) may not work as expected (e.g. the latest shader-based clouds in CVS/HEAD are unlikely to work with current Xgl implementations).
-So if you are using an GL-accelerated X-server (i.e. to run Compiz/Fusion) under Linux and are experiencing performance issues or other graphics related problems, please verify if these problems persist after having disabled Xgl support, this can usually be accomplished using xgl-switch --disable
-For Linux, there's now an OpenGL benchmarking test suite available [http://www.phoronix-test-suite.com/ here] ([http://www.phoronix-test-suite.com/download.php?file=phoronix-test-suite-1.4.0 download]) that provides useful information about your system's degree of OpenGL support, if you are unsure about your system's OpenGL support and if you are experiencing performance issues in FlightGear, you may want to try running this test suite first in order to ensure that OpenGL is properly set up on your system.
 === General hardware info ===

Asking for help: Difference between revisions

Asking for help (view source)

Revision as of 23:16, 24 May 2014

Navigation menu

Search