1. The Chase view is broken: it's too close, and does not center to a position behind the aircraft, but apparently to a fixed compass direction.
2. On the Mac version, at least, fgfs freezes on exit, requiring a force-quit.
3. It will not find the C172P in an Aircraft folder on the same level (i.e., not inside) the Data folder. It does find other aircraft there.
#3 is trivial to me and I haven't bothered to test for it, but FWIW the other two problems still exist in the March 8 build.
Regarding #2: Are you able to view the console when you have to force-quit? Does it have a message about pthread_cond_destroy?
If it's the same problem (as I am seeing on Linux), I've tracked down the offending commit and reported it on the mailing list.
The Mac OS console? FG is frozen with a spinning beachball cursor. If there's a FG console on Mac, I have no idea where to find it.
Try a spotlight search for "console" (cmd-space, then type console). Or you can try Launchpad, in the Others group.
If you open the Console app, it might list Flightgear console messages under "SYSTEM LOG QUERIES" - "All Messages". Or it might not.
Console only shows the force-quit, nothing at all about the crash on exit.
Is anyone else seeing the annoying Chase View problem? I downloaded the latest full package, and it's still there.
I've noticed the model view isn't quite how it used to be either. The first time I use it, it seems to rotate around the wrong point when moving position with the mouse.
What's your best estimate of when your view issues started?
It started with 2016.2.0. Centering the chase view points it toward a fixed compass heading, instead of following the aircraft from behind. Also, it's either too close, or the zoom level is wrong. The horizon is always not-quite-level, instead of the view banking with the plane. I don't see any changes in the chase view code in preferences.xml, so I presume thenproblem is in the executable.
This is way more annoying than having to force-quit every time.
I believe the commit that introduces the chase view problem is Flightgear 65d503.
Have you raised a bug in the tracker or mentioned this issue on the mailing list? I can do so, if you like.
In today's 2016.2.0 build, the chase view bug is fixed Thanks!
However, I can't seem to find anywhere to put the C172P where the launcher can find it. Even if I specify its own folder, I get this error: "No aircraft found in the folder '/Users/xxxxxx/FlightGear/data/Aircraft/c172p'." All my other aircraft are found, in fact each appears in the list twice (three times, if you count the catalog copy FG doesn't think has been downloaded yet). This is using today's C172P build.
I know it's a work in progress, I'm just reporting my experiences.
someguy wrote in Thu Mar 24, 2016 9:18 pm: In today's 2016.2.0 build, the chase view bug is fixed Thanks!
seeing as how James doesn't read the forums and he is the one behind the launcher integration etc, posting it here is not very helpful to James. In fact, a recent discussion on the development mailing list talked specifically about your problem. The two way communication you two have decided on is probably why it has taken this long to get fixed.