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 bugman » Wed May 18, 2016 3:52 pm

It's confusing because we are in the middle of a release process that takes a few days ;) A little patience is required.

Regards,
Edward
bugman
Moderator
 
Posts: 1700
Joined: Thu Mar 19, 2015 9:01 am
Version: next

Re: 2016.2.0

Postby someguy » Wed May 18, 2016 5:42 pm

News flash: like Generalissimo Francisco Franco (old SNL joke), 2016.2.1 is still dead. Same plug-in error as every release since mid-April.
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 elgaton » Wed May 18, 2016 9:25 pm

Update from the -devel mailing list: James Turner (one of the core developers - he works on the Mac platform) is aware of the issue, he is (however) having some trouble finding its cause (especially because the builds seem to work fine on his machine). I'll keep you updated.
NIATCA 2nd admin, regular ATC at LIPX and creator of the LIPX custom scenery
elgaton
 
Posts: 1107
Joined: Tue Mar 19, 2013 4:58 pm
Callsign: I-ELGA/LIPX_TW
Version: Git
OS: Windows + Arch Linux

Re: 2016.2.0

Postby someguy » Thu May 19, 2016 12:19 am

Thank you, elgaton. Perhaps, as a Plan B, James might consider uploading a functioning build of 2016.2.1 to a server from which Mac users could download it. It appears the recent push for automation is not working all that well.

A DOA release version on the main download page will not speak well for the project. Honestly, I'm just trying to prevent that embarrassment.
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 jaxsin » Thu May 19, 2016 12:15 pm

someguy wrote in Thu May 19, 2016 12:19 am:A DOA release version on the main download page will not speak well for the project. Honestly, I'm just trying to prevent that embarrassment.


The mac builds have been renamed afaik, Torsten has done so knowing they are broken. Not to fear! Announced on mailing list...

I have renamed the 2016.2.1 installer for mac at https://sourceforge.net/projects/flight ... se-2016.2/ as it is obviously broken.


Regards

Torsten

jaxsin
 
Posts: 396
Joined: Mon Dec 28, 2015 3:54 pm

Re: 2016.2.0

Postby wkitty42 » Thu May 19, 2016 3:22 pm

we're apparently still waiting on someone to take the info that patrice asked to be posted to the list and confirm if moving the files in the package takes care of the problem... if it does, it would seem to indicate that there's been a change in packaging layout... the question is what is the boundary line between the mac oses... at what version of mac os does the package layout change IF that is the problem...
"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: 5644
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 jaxsin » Thu May 19, 2016 3:51 pm

what patrice described was moving the OSG 3.4 out of the way and going back to OSG 3.2. AFAIK that is the difference between the versioning. IE osg100* versus osg130*
Last edited by bugman on Thu May 19, 2016 4:01 pm, edited 1 time in total.
Reason: Please do not quote the entire previous post.
jaxsin
 
Posts: 396
Joined: Mon Dec 28, 2015 3:54 pm

Re: 2016.2.0

Postby wkitty42 » Thu May 19, 2016 4:08 pm

yes but there was also this part...
I had to change also the "fgfs executable" from the "Contents/MacOs" folder and the entire "osgPlugins" folder found in the "Contents/PlugIns" folder
and the program runs perfectly again, including Thorsten new (experimental) night vision or infrared vision !

and that's the part i'm looking at... i don't know what he means by "had to change" the executable from the folder and if he means he moved it, which folder was it moved to... same thing with the osgplugins stuff... i can understand the different between osg 3.2 and 3.4... i have both here since i build everything myself but i've not attempted osg 3.4 at this time... i've written patrice another email asking for further clarification...
"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: 5644
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 jaxsin » Thu May 19, 2016 4:43 pm

I didn't understand that part either. It's why someone with a mac build who participates in the development builds needs to test these things. My hands are tied with that
Last edited by bugman on Thu May 19, 2016 5:41 pm, edited 1 time in total.
Reason: Please do not quote the entire previous post.
jaxsin
 
Posts: 396
Joined: Mon Dec 28, 2015 3:54 pm

Re: 2016.2.0

Postby wkitty42 » Thu May 19, 2016 5:09 pm

patrice is just a user like you and me... apparently he went into the installed package and moved things around... if he changed from osg 3.4 to osg 3.2, that would indicate that he had another older installation... if his changing of the executable was copying it over from the old installation then he is apparently now running an older version (before Mar 24 2016) with the new fgdata... i'm waiting on his reply for clarification and hopefully he will include a screen shot of the help->about dialogue...
"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: 5644
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 jaxsin » Sat May 21, 2016 12:37 pm

James posted he found the problem on the mailing list. Said he posted a hack to next branch and will work on a proper fix and backport to release branch in time.

edit:
Found a work around, release branch and nightly are building now. Fingers crossed.


@someguy Maybe you can verify and report back if this works for you?
jaxsin
 
Posts: 396
Joined: Mon Dec 28, 2015 3:54 pm

Re: 2016.2.0

Postby VicMar » Sat May 21, 2016 3:48 pm

@ Someguy,

I downloaded 2016.3 nightly (dated 21st) and it seems to be working OK.

I haven't tried anything apart from opening it and flying the ufo, but it does seem to be providing scenery as required.

Vic
Time flies like an arrow
Fruit flies like a banana
User avatar
VicMar
 
Posts: 2057
Joined: Sun Apr 06, 2008 5:53 pm
Location: Lancing. UK (EGKA)
Callsign: VicMar
Version: 2018.3.1
OS: OS X 10.12.6

Re: 2016.2.0

Postby someguy » Sat May 21, 2016 5:54 pm

2016.3 does start. But I can't get it to find my existing Terrasync scenery (outside the data folder). It insists on trying to download everything anew, but then fails due to errors. Also, fgfs still has to be force-quit.
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 » Sat May 21, 2016 6:20 pm

@someguy: are you using an explicit --terrasync-dir=/path/to/my/private/ts/dir in your launcher additional parameters section?

what specific errors are you seeing when it tries to download the scenery data and failures are reported?

the "force-quit" thing is still a problem that hasn't been tracked down... there's numerous paths of the code that appear to be shutting down before other path are finished with them...
"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: 5644
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 » Sat May 21, 2016 8:33 pm

wkitty42 wrote in Sat May 21, 2016 6:20 pm:@someguy: are you using an explicit --terrasync-dir=/path/to/my/private/ts/dir in your launcher additional parameters section?


No, I'm specifying it in the launcher's Add-ons pane, as the download location. However, it's not really clear from the pane's instructions what that means, so maybe that was a bad idea. In previous versions, I could specify aircraft and scenery source folders in separate places, and it worked. My aircraft folder appears correctly.

wkitty42 wrote in Sat May 21, 2016 6:20 pm:what specific errors are you seeing when it tries to download the scenery data and failures are reported?


I cannot copy text from the Scenery Download dialog's Log pane, but there are a lot of 'failed to update entry path "" code 6' and 'sync taking a long time.' I finally did get TNCM to load, but after 5 minutes of flying that log is still adding new lines, so scrolling back won't work. I can see good rates in the Downloading Scenery line on the splash screen before spawn.

Every time I spawn at the same airport, Terrasync starts downloading everything again. EDIT: If I disable Terrasync in the launcher, FG will load my stored scenery...slowly.

Good news: I see the Urban shader is fixed. Some aircraft and some random buildings still present as large black triangles if the Model shader is enabled at all.
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 2 guests