(This is a re-post that was deep in another thread. I thought it would help to post it as a new item.)
Hi everyone. I am new to FlightGear (2017.2.1 for Windows 10) and new to the forum, but not new to computer issues.
I'd like to throw in my 2 cents on the scenery/object issue as I believe I've found, although somewhat time consuming, solution.
It seems like a long read, but think you will find it worth it in the end.
First, I personally cannot use Terrasync, so I am using the 10x10 grid scenery downloads of the world.
Initially, I only went for the HD scenery, 2.0.1.
As I found, these 10x10 chunks do not have separate Terrain and Object folders as some of you have mentioned.
The new launcher in the "Add-Ons" page can unpack and dump them into a Scenery directory (eg. C:\Users\username\documents\FlightGear\Scenery
As many of you now know, when you start FlightGear and set the location for one of your new downloaded scenery, you get the "blue ocean" and no scenery or objects other than maybe other planes.
After much frustration, I started executing FlightGear from a command line window to see the execution and pointed it to the scenery directory.
(eg. - c:\Program Files\FlightGear 2017.2.1\bin\fgfs --launcher --fg-scenery c:\Users\username\documents\FlightGear\Scenery
After exiting the Launcher, the Command window was full of errors that specifically stated that scenery and object files were no longer supported
in a single folder (such as Scenery) and had to be loaded into sub-folders "Terrain" and "Object" within "Scenery".
FINALLY AN ANSWER. Although, it seems strange because it goes against what the Launcher scenery installer is trying to do.
So, I "reset" the program to it's defaults, which removed the added scenery directory and I manually deleted all the added scenery in c:\Users\username\documents\FlightGear\Scenery.
I took one of the new 2.0.1 chunks and unpacked it (7-zip) into the c:\Program Files\FlightGear 2017.2.1\data\Scenery\Terrain directory.
I started the launcher normally (from the desktop icon), pointed my location to the airport in that new chunk and low and behold, I had scenery!!
BUT, the airport terminal was missing (objects).
I put the same 10x10 chunk in the ...\Scenery\Objects\ directory and tried again. This had no effect.
Now I'm really agitated, because I'm so close.
Finally, I went to the 1.0.1 scenery download map and downloaded the SAME 10x10 chunk and unpacked it.
This 10x10 chunk, as you may know already, has the separate "Terrain" and "Object" folders.
I took ONLY the folder in the "Object" folder and copied it to the c:\Program Files\FlightGear 2017.2.1\data\Scenery\Objects folder.
When I loaded the next time....HAHA!! - Scenery with objects, including the airport terminal.
So, in the end, I am using a combination of both 2.0.1 and 1.0.1 10x10 chunks by unpacking:
a) 2.0.1 - 10x10 chunks into the c:\Program Files\FlightGear 2017.2.1\data\Scenery\Terrain folder
b) 1.0.1 - Contents of the 10x10 "Object" folder only chunks into the c:\Program Files\FlighGear 2017.2.1\data\Scenery\Objects folder
Note1; When unpacking using 7-zip, you may need to unpack into a temporary folder first due to some computer's Admin authorization. Then copy the unpacked folder to the appropriate directory.
Note2: The 2.0.1 10x10 grid download will unpack as a second compressed file. Unpack the second file revealing the folder to copy to ...data\Scenery\Terrain
The 1.0.1 10x10 grid download will unpack into it's separate "Terrain" and "Object" folders. Copy only the contents of the Object folder to ...data\Scenery\Object folder in the FlighGear directory.
It is painstaking, but for those who can't use Terrasync, it is worth the effort to get up and flying at other airports!
I hope that the Launcher scenery import can be adjusted in the future by those that can to fit the directory folders the main program expects.
And/or the 2.0.1 world scenery 10x10 download chunk files separated into their proper "Terrain" and "Object" folders (if the objects actually exist there.)
I HOPE this helps many others to get going....comments are welcome as I am continuing to learn more about the FlightGear world.