20,741
edits
Troubleshooting crashes: Difference between revisions
Jump to navigation
Jump to search
m
→Performance Issues
m (→Performance Issues: http://forum.flightgear.org/viewtopic.php?f=37&t=22309&p=202574&hilit=amd+load#p203655) |
|||
| Line 18: | Line 18: | ||
== Performance Issues == | == Performance Issues == | ||
If working through this article doesn't solve problem, you are probably facing a hardware/driver issue, which means that you may need to upgrade (or even downgrade) your drivers, and/or disable some settings on the driver side of things. | If working through this article doesn't solve the problem, you are probably facing a hardware/driver issue, which means that you may need to upgrade (or even downgrade) your drivers, and/or disable some settings on the driver side of things. | ||
If however, the "minimal startup profile" stops the error from occurring, that would suggest that FG is using some "code paths" that are not supported by your current driver - this isn't all that uncommon, we have an increasing number of GLSL shaders, while most of the existing FG code was really only written with a fixed rendering pipeline in mind - and in fact, much of it even predates the OSG port, such as for example the GUI (PLIB/PUI). | If however, the "minimal startup profile" stops the error from occurring, that would suggest that FG is using some "code paths" that are not supported by your current driver - this isn't all that uncommon, we have an increasing number of GLSL shaders, while most of the existing FG code was really only written with a fixed rendering pipeline in mind - and in fact, much of it even predates the OSG port, such as for example the GUI (PLIB/PUI). | ||