573
edits
Asking for help: Difference between revisions
Jump to navigation
Jump to search
m
link update
m (+-cat Category:Troubleshooting) |
m (link update) |
||
| Line 26: | Line 26: | ||
* the output from running glxinfo | * the output from running glxinfo | ||
People experiencing corrupted textures, should also see [[ | 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). | '''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). | ||