See $URL, version 2.12 was released September 21, 2013 Reproducible: Always
Packages also likely requiring upgrading: =dev-games/simgear-2.12.0 =games-simulation/flightgear-data-2.12.0 *NOTE: FlightGear-data-2.12.0.tar.bz2 seems to be listed as "FlightGear-data-2.12.0.tar.bz" on the mirrors! Rename as needed. Building... flightgear-data-2.12.0.ebuild -- doins -r data/* ++ doins -r fgdata/* Build completed. *TODO: 1) Patch flightgear-data.ebuild as specified above replacing the suffix 'bz' with 'bz2' and replacing folder name 'data' with 'fgdata'. 2) Check all files were installed as expected. 3) Check if anymore USEFLAGS are required. 4) Check for any other build problems exhibited during execution. ;-) Flightgear-2.12.0 runs here, albeit with some weird graphics corruptions, but still flyable.
FYI: My keyboard keys for throttle (ie. PgUp, PgDn, 3, 9) are not working, bug is filed here -> http://code.google.com/p/flightgear-bugs/issues/detail?id=1240 Also, the reason the Win32 has good frame rates, is likely due to the Win32 using the c172p-canvas as the default aircraft! The default aircraft loaded under linux (or normally) is the "c172p", and using it provides the really bad frame rates. Should probably provide a elog/einfo notice on this after install. A bug is also filed with this here -> http://code.google.com/p/flightgear-bugs/issues/detail?id=1243
I also might suggest providing an einfo/elog statements providing the user with some really basic command line options, similar to the default win32 build. ie. "fgfs --aircraft=c172p-canvas --control=joystick --disable-random-objects --prop:/sim/rendering/random-vegetation=false --disable-ai-models --enable-clouds3d --enable-fullscreen --prop:/sim/frame-rate-throttle-hz=60 --geometry=1680x1050 --bpp=32 --timeofday=noon" NOTE: "geometry" is likely auto probed and user specific. "noon" was added later, and the default win32 option is local time. This would also solve the issue of user experiencing poor frame rates when loading the default "c172p" aircraft model instead of the "c172p-canvas" aircraft model. Albeit, they first have to read the einfo/elog statements, as I rarely do either.
I've solved my throttle not working with keyboard and joystick input. Turns out it was caused by compiling with -funroll-loops CFLAG. I might have caught a backtrace with gdb and submitted along side the upstream filed bug. First bug I've seen in a long time with this flag, and the first bug with i7 CPU.
*** Bug 489840 has been marked as a duplicate of this bug. ***
Thanks for head up!
BTW. Compiling simgear with anything other then stable CFLAGS causes flightgear to ignore joystick throttle controller and other certain keyboard key mappings. (ie. The CC flag '-funroll-loops' provokes the previously mentioned issues.) Likely simgear needs some code fixes.
