Showstoppers
From wiki.flightgear.org
| This article is a stub. You can help the wiki by expanding it.. |
This page is meant to become a list of issues that are frequently reported by users to severely affect the "FlightGear experience".
2009
near/far camera issue
Description: near/far camera issue
Workaround:
Solution:
TriangleIntersect /Qnan Issues in 1.9x release & CVS/HEAD
Description: Extensive console output that is caused by error messages significantly slows down the simulator and renders it unusable due to severely affected framerates.
Workaround: reduce log level or completely disable logging.
- Try reducing log-level to "alert" according to the instructions here
- Send all error output to "/dev/null" (unix systems) or "2>nul" (Windows). That means starting FG with a command like
fgfs.exe --fg-root="C:\Program Files\FlightGear\data\data" --fg-scenery="C:/Program Files/FlightGear/data-orig/Scenery;C:\Program Files\FlightGear\scenery;C:\Program Files\FlightGear\terrasync" [other options etc] 2> nul
OR
./fgfs [options etc] > /dev/null
- Under Windows you can use this solution with fgrun. Simply create a batch file named "fgfs.bat" in the bin/Win32 directory with this content:
fgfs.exe %* 2> nul
Now in fgrun, choose the file fgfs.bat as the executable. It will start FG and you will see absolutely no messages on console, including the problematic triangleintersect messages.
Solution: none so far, problem persists and requires complete simulator restart
- QNAN freeze bug report... (05/2009)
- "Warning: Picked up error in TriangleIntersect" freezes fg
- Fw: More reports to help debug the QNAN thing...
- More reports to help debug the QNAN thing...
- framerate hesitations
- fgfs lock up that is repeatable
- FlightGear Freezes Sporadically
- Help with Warning picked up triangle intersect error update
- Help with Warning picked up triangle intersect error
- "Warning: Picked up error in TriangleIntersect" freezes fg
- So what causes frame rate loss in FlightGear 1.9 ??????
- Lots of trouble
