Board index FlightGear Release candidates

2016.2.0

Release candidate testers are encouraged to post their feedback here. Please read the introduction topic for details.
Forum rules
Please read the introduction topic for details.

Re: 2016.2.0

Postby someguy » Fri Mar 25, 2016 3:38 am

I tried that, in multiple locations. It works perfectly with every aircraft, including the uninstalled catalog in Aircraft/org.flightgear.official, except for the c172p. Something is evidently different about that model, I know not what. Also something is obviously different about the Mac build that you aren't seeing in linux.

Tomorrow, I'll fetch an older version of the 172 from a Time Machine backup, and see if it's the model or the app.
User avatar
someguy
 
Posts: 1653
Joined: Tue Nov 25, 2008 5:54 am
Location: USA
Version: 2016.2.1
OS: Mac OS X 10.11

Re: 2016.2.0

Postby wkitty42 » Fri Mar 25, 2016 3:14 pm

you do have the c172p's directory in your custom area named properly, right? it is "c172p" in both fgdata and your custom location...

eg:
Code: Select all
/home/myuser/flightgear-dev/fgdata-ng/Aircraft/c172p
/home/myuser/myflightgear/Aircraft/c172p
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 5501
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: 2016.2.0

Postby someguy » Fri Mar 25, 2016 7:09 pm

Yes, I do. I tried an older, known-good version of the c172p. Same result. I tried launching default fgfs (with no arguments) from the Terminal: same thing, c172p not found.

I cannot imagine why this only affects one model, and the default one at that.

Edit: more data. I can't choose to fly the c172p, but in MP I can see them being flown by other users. I assume that means fgfs has no problem finding the model, just the launcher.
User avatar
someguy
 
Posts: 1653
Joined: Tue Nov 25, 2008 5:54 am
Location: USA
Version: 2016.2.1
OS: Mac OS X 10.11

Re: 2016.2.0

Postby someguy » Sun Apr 03, 2016 1:18 am

There seems to be a new glitch with the Urban ALS shader. The center slider position looks normal, but the two highest notches lose the 3D effect.
User avatar
someguy
 
Posts: 1653
Joined: Tue Nov 25, 2008 5:54 am
Location: USA
Version: 2016.2.1
OS: Mac OS X 10.11

Re: 2016.2.0

Postby someguy » Wed Apr 06, 2016 6:19 pm

I downloaded the latest full 2016.2 package from 5 March. The C172P problem is fixed (or only existed on my previous installation for some reason, probably my fault). The crash-on-quit issue is still there. So is the Urban shader bug. Just an FYI, especially for Mac users.

The visual improvements are far too tasty to consider going back to a release version!
User avatar
someguy
 
Posts: 1653
Joined: Tue Nov 25, 2008 5:54 am
Location: USA
Version: 2016.2.1
OS: Mac OS X 10.11

Re: 2016.2.0

Postby wkitty42 » Wed Apr 06, 2016 7:24 pm

the crash-on-quit problem is because the subroutines are not being shut down in the proper order... something is being shut down and removed while other code is expecting that data and routines to still be in memory and operational... they'll find it soonish ;)
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 5501
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: 2016.2.0

Postby someguy » Wed Apr 13, 2016 9:36 pm

The last couple of builds, including today's full package, crash immediately on launch. Here's the relevant portion of the Console log:

Code: Select all
Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib           0x00007fff97451f06 __pthread_kill + 10
1   libsystem_pthread.dylib          0x00007fff84fbf4ec pthread_kill + 90
2   libsystem_c.dylib                0x00007fff96ed66e7 abort + 129
3   org.qt-project.QtCore            0x0000000104d84d29 0x104d62000 + 142633
4   org.qt-project.QtCore            0x0000000104d861e1 QMessageLogger::fatal(char const*, ...) const + 161
5   org.qt-project.QtGui             0x000000010482a0b7 QGuiApplicationPrivate::createPlatformIntegration() + 6359
6   org.qt-project.QtGui             0x000000010482a0db QGuiApplicationPrivate::createEventDispatcher() + 27
7   org.qt-project.QtCore            0x0000000104f9f8e1 QCoreApplication::init() + 113
8   org.qt-project.QtCore            0x0000000104f9f857 QCoreApplication::QCoreApplication(QCoreApplicationPrivate&) + 39
9   org.qt-project.QtGui             0x000000010482754e QGuiApplication::QGuiApplication(QGuiApplicationPrivate&) + 14
10  org.qt-project.QtWidgets         0x00000001041edaae QApplication::QApplication(int&, char**, int) + 206
11  org.flightgear.FlightGear        0x000000010289e757 flightgear::initApp(int&, char**) + 263
12  org.flightgear.FlightGear        0x0000000101db30bb flightgear::Options::setupRoot(int, char**) + 683
13  org.flightgear.FlightGear        0x0000000101db1846 flightgear::Options::init(int, char**, SGPath const&) + 1814
14  org.flightgear.FlightGear        0x0000000101d82f0e fgInitConfig(int, char**, bool) + 414
15  org.flightgear.FlightGear        0x0000000101da9f2e fgMainInit(int, char**) + 2110
16  org.flightgear.FlightGear        0x0000000101d75800 main + 256
17  org.flightgear.FlightGear        0x0000000101d756f4 start + 52
User avatar
someguy
 
Posts: 1653
Joined: Tue Nov 25, 2008 5:54 am
Location: USA
Version: 2016.2.1
OS: Mac OS X 10.11

Re: 2016.2.0

Postby wkitty42 » Thu Apr 14, 2016 3:24 am

some of these things, like this, should be posted to the developer's list so that james can see them... most developers do not frequent these forums and can easily miss things like this...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 5501
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: 2016.2.0

Postby someguy » Thu Apr 14, 2016 1:21 pm

It's a shame someone would go to the trouble of writing code, then not be interested in whether or not it worked.
User avatar
someguy
 
Posts: 1653
Joined: Tue Nov 25, 2008 5:54 am
Location: USA
Version: 2016.2.1
OS: Mac OS X 10.11

Re: 2016.2.0

Postby Thorsten » Thu Apr 14, 2016 2:43 pm

It's a shame someone would go to the trouble of writing code, then not be interested in whether or not it worked.


I'm pretty sure he tested it after compiling :-) Anyway, it's assumed that problems with the core get reported on the mailing list where core development is discussed. And there's a big statement here in the forum that core development is discussed on the mailing list and not here.

If you have trouble with your internet provider, it's also not really useful to post this in this forum in the hope that he reads it - you have to post it to the hotline. You may not like that, but as a rule the world expects you to say what you say in certain places and doesn't go looking for wherever else people say something.
Thorsten
 
Posts: 10693
Joined: Mon Nov 02, 2009 8:33 am

Re: 2016.2.0

Postby someguy » Fri Apr 15, 2016 8:03 pm

In the remote event that anyone here cares, when I tried launching fgfs from the Terminal, it threw this message:

This application failed to start because it could not find or load the Qt platform plugin "cocoa".

If no developer cares, fine. I'm just warning other Mac users not to expect it to work.
User avatar
someguy
 
Posts: 1653
Joined: Tue Nov 25, 2008 5:54 am
Location: USA
Version: 2016.2.1
OS: Mac OS X 10.11

Re: 2016.2.0

Postby wkitty42 » Fri Apr 15, 2016 9:33 pm

@someguy: now that's an error report that someone can work with!

if i'm reading properly, you are running OSX 10.11... is that correct?

i've posted this to the developer's list where it really should be ;) let's see what james and others have to say, ok?
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 5501
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: 2016.2.0

Postby someguy » Mon Apr 25, 2016 1:34 pm

For everyone's information, the development server is still cranking out Mac builds that will not launch, containing improvements that no Mac user will see.
User avatar
someguy
 
Posts: 1653
Joined: Tue Nov 25, 2008 5:54 am
Location: USA
Version: 2016.2.1
OS: Mac OS X 10.11

Re: 2016.2.0

Postby wkitty42 » Mon Apr 25, 2016 3:45 pm

@someguy: here's james response (on 2015 Apr 16) to the last message i posted to the dev list...
> On 15 Apr 2016, at 22:35, wkitty42@gmail.com wrote:
>
> this is from the forums...
> viewtopic.php?p=282581#p282581
>
> apparently he is running OSX 10.11... as i'm not a mac guy, i can only forward
> the information...

Thanks for the heads-up. I see the same thing when I download a nightly build, but of course my local build works fine, so it’s something in the packaging on the build server. But nothing changed in the packaging for months, and not in the Qt version either. Very odd.

And most confusing, the plugin it says it cannot find - is actually present in the correct location inside the bundle. So something really stupid is happening, I’ll investigate now.

Again, thank you for passing on this issue, and trying to encourage the poster to use the mailing list.

Kind regards,
James


my apologies for not getting it posted back here sooner... i had thought that the hint to join or at least read the dev list would be sufficient... in any case, i'll ask him what the results of his investigation are...

i have forwarded your latest comment to the list...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 5501
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: 2016.2.0

Postby someguy » Mon Apr 25, 2016 6:01 pm

Right now, I'm involved in a project that requires reading and evaluating around 250 emails per day, 7 days a week. I expect that number to double over the next month. I frankly don't need any more email traffic, so I hope you can understand my reluctance to join yet another mailing list, the contents of which are almost 100% over my head or otherwise irrelevant to me.

I do appreciate your intervention. I'm rather surprised that James doesn't routinely test his own output in the only form it's available to ordinary users. I'll refrain from asking any more obvious questions... :)
User avatar
someguy
 
Posts: 1653
Joined: Tue Nov 25, 2008 5:54 am
Location: USA
Version: 2016.2.1
OS: Mac OS X 10.11

PreviousNext

Return to Release candidates

Who is online

Users browsing this forum: No registered users and 1 guest