13,255
edits
Troubleshooting graphics artifacts: Difference between revisions
Jump to navigation
Jump to search
m
Troubleshooting graphics artifacts (view source)
Revision as of 21:56, 17 January 2014
, 17 January 2014cat: Howto
m (cat: Howto) |
|||
| Line 4: | Line 4: | ||
== Bad Performance, corrupted textures & other artifacts == | == Bad Performance, corrupted textures & other artifacts == | ||
To help us help you, please answer the following questions and post your answers: | To help us help you, please answer the following questions and post your answers: | ||
| Line 30: | Line 29: | ||
So, first of all, I'd ensure that OpenGL in general works properly. glxinfo and glxgears are just the start, there are other benchmarks, and also shader tests. If on the other hand, other software like UrbanTerror works at >= 30 fps, you should also be able to customize FG a little more, so that unsupported stuff can be disabled. | So, first of all, I'd ensure that OpenGL in general works properly. glxinfo and glxgears are just the start, there are other benchmarks, and also shader tests. If on the other hand, other software like UrbanTerror works at >= 30 fps, you should also be able to customize FG a little more, so that unsupported stuff can be disabled. | ||
[[Category:Howto|Troubleshooting Graphics Artifacts]] | |||