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 elgaton » Sun May 22, 2016 6:53 pm

The fixed Mac installer has now been released.

Regarding the scenery/aircraft locations, here's how they have been reorganized (I hope this clarifies things):
  • aircraft downloaded from the Aircraft Center and TerraSync scenery are saved in <download location>/Aircraft and <download location>/TerraSync, where <download location> can be set from the Add-ons tab of the Qt launcher (it's ~/.fgfs on Mac/Unix system and C:\Users\<your user name>\Documents\FlightGear on Windows, if I'm not mistaken). Thus, the download location you specify in the launcher is not just the TerraSync directory, but rather a directory containing both the TerraSync and the Aircraft download paths;
  • additional scenery and aircraft locations (which will be not automatically updated) can be specified in the Additional scenery locations and Additional aircraft locations panes, if needed.
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 » Sun May 22, 2016 11:29 pm

Ah, that clears up the ambiguity, and now Terrasync works, many thanks. However, now FG cannot find the C172P in my hangar folder (not inside the data folder). All the other aircraft in that folder were found. Do I need to delete some cache file?

BTW, for Mac OS, ~/.fgfs went away in FG 3.something.
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 » Mon May 23, 2016 7:40 am

someguy wrote in Sun May 22, 2016 11:29 pm:Ah, that clears up the ambiguity, and now Terrasync works, many thanks. However, now FG cannot find the C172P in my hangar folder (not inside the data folder). All the other aircraft in that folder were found. Do I need to delete some cache file?

That happens because, as the C172P is in FGData, FlightGear gets it from there before searching your hangar folders. Just rename the C172P folder in your FGData path to something else (unfortunately, I don't have a Mac, so I don't know what the FGData path is on that platform).

someguy wrote in Sun May 22, 2016 11:29 pm:BTW, for Mac OS, ~/.fgfs went away in FG 3.something.

Thanks (I assumed the path was the same as the one on Linux).
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 bugman » Mon May 23, 2016 8:56 am

someguy wrote in Sun May 22, 2016 11:29 pm:BTW, for Mac OS, ~/.fgfs went away in FG 3.something.


Simply for reference, see $FG_HOME (and for FGData on macs, see $FG_ROOT).

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

Re: 2016.2.0

Postby someguy » Mon May 23, 2016 3:29 pm

elgaton wrote in Mon May 23, 2016 7:40 am:That happens because, as the C172P is in FGData, FlightGear gets it from there before searching your hangar folders. Just rename the C172P folder in your FGData path to something else


I had moved the C172P folder completely out of fgdata into my hangar folder, which is in the same enclosing folder as fgdata. I tried moving it back, but the C172P still didn't appear in the launcher. I even tried adding a line to "Additional aircraft locations" to no avail. This happened in an earlier release, I don't recall which one, and then got fixed. Just another regression, I suppose.

EDIT: I bailed on 2016.3 and downloaded the new 2016.2.1. It found both the C172P in my hangar and the one in fgdata, and seems to run well. It still crashes on exit as expected...and I still haven't seen any of Thorsten's cotton-pickin' birdies. :P :)
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 Ambro » Thu May 26, 2016 5:58 pm

I noticed that the maxinum download speed for sceneries via TerraSync is 159 kb/s even if I use a 100Mb/s internet connection
User avatar
Ambro
 
Posts: 31
Joined: Sat May 31, 2014 4:27 pm
Location: EDDB

Re: 2016.2.0

Postby PINTO » Thu May 26, 2016 7:17 pm

That's a known issue, they think it's due to libcurl or something. Switching to http Terrasync solves the issue. There's a property you set at launch but I don't have it in front of me, sorry. You can search the mailing list for it though.
Actively developing the MiG-21bis (github repo) (forum thread) (dev discord) (fg wiki)

http://opredflag.com is an active flightgear dogfighting community (using a system that isn’t bombable)
User avatar
PINTO
 
Posts: 945
Joined: Wed Oct 21, 2015 6:28 pm
Callsign: pinto
Version: 2016.3.0
OS: Win10

Re: 2016.2.0

Postby wkitty42 » Thu May 26, 2016 8:50 pm

the property is
Code: Select all
--prop:/sim/terrasync/http-server=automatic
"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: 5654
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 Ambro » Fri May 27, 2016 4:44 pm

Thank you very much wkitty42 and PINTO :)
User avatar
Ambro
 
Posts: 31
Joined: Sat May 31, 2014 4:27 pm
Location: EDDB

Previous

Return to Release candidates

Who is online

Users browsing this forum: No registered users and 0 guests