573
edits
Howto:Understand console output: Difference between revisions
Jump to navigation
Jump to search
m
link update
m (+-cat Category:Troubleshooting) |
m (link update) |
||
| Line 227: | Line 227: | ||
=== Unknown exception in main loop. Aborting...<br/>Possible cause: Not enough space === | === Unknown exception in main loop. Aborting...<br/>Possible cause: Not enough space === | ||
* When running 64 bits Windows, make sure to uncheck the "force 32-bits" option on installation. | * When running 64 bits Windows, make sure to uncheck the "force 32-bits" option on installation. | ||
* Most notebooks that run Windows 7 have the so called Optimus Technology (NVidia) or Hybrid Graphics technology (ATI) onboard. This is meant to increase battery life, by automatically switching of the powerfull graphics card when it's not needed. However, FlightGear needs it all the time, even if Optimus says it doesn't! See [[ | * Most notebooks that run Windows 7 have the so called Optimus Technology (NVidia) or Hybrid Graphics technology (ATI) onboard. This is meant to increase battery life, by automatically switching of the powerfull graphics card when it's not needed. However, FlightGear needs it all the time, even if Optimus says it doesn't! See [[Troubleshooting performance issues#Operating system and driver setup|here]] for instructions on how to disable this behaviour. | ||
When the above mentioned points do not apply or did not work, you are likely to be unable to run FlightGear at the current graphics settings. See [[Howto:Improve framerates#Shaders]] for instructions on how to switch off demanding eye candy. | When the above mentioned points do not apply or did not work, you are likely to be unable to run FlightGear at the current graphics settings. See [[Howto:Improve framerates#Shaders]] for instructions on how to switch off demanding eye candy. | ||