swwon wrote in Wed Sep 28, 2016 10:14 am:Part of a big problem is, there is no set format that every developer is following for the custom scereries and each one is installed a different way, it would be so nice if all we had to do is click and drag and drop a new folder in the scenery section and it would all work. Some are just THAT easy, but many other arent...
swwon wrote in Wed Sep 28, 2016 10:14 am:but anyways....After you have placed the folders in the appropriate scenery folders,
swwon wrote in Wed Sep 28, 2016 10:14 am:you must then point fgrun to the omdb custom scenery folder and make a new line for each folder in it individually. With the project 300 in one line by itself then osm2city in another and so on until the omdb is the last of the string of seperate lines you put in order for fgrun to show it the way you want. You also must make sure that the standard fg scenery line and terrasync line is AFTER those command lines for OMDB custom scenery. Thats how I have it set and it works fine. I dont have the jetways though but Im okay with that.
Lydiot wrote in Thu Sep 29, 2016 3:48 am:Thanks for the replies!swwon wrote in Wed Sep 28, 2016 10:14 am:but anyways....After you have placed the folders in the appropriate scenery folders,
Ok, let me just stop right there so I understand:
- Are you saying that I need to copy/move the folders from the downloaded folder into some other folders? If so, which ones? Which "scenery folders" are you referring to? My understanding was that if I place it in my terrasync folder then when it's on it'll overwrite custom files. So instead I should use a custom folder and point to it.
swwon wrote in Wed Sep 28, 2016 10:14 am:you must then point fgrun to the omdb custom scenery folder and make a new line for each folder in it individually. With the project 300 in one line by itself then osm2city in another and so on until the omdb is the last of the string of seperate lines you put in order for fgrun to show it the way you want. You also must make sure that the standard fg scenery line and terrasync line is AFTER those command lines for OMDB custom scenery. Thats how I have it set and it works fine. I dont have the jetways though but Im okay with that.
Lydiot wrote in Thu Sep 29, 2016 3:48 am:That is partially what I did at first. I pointed to the "300" folder first, then "OSM", and then the entire folder that enclosed them and "terrain" etc. I now tried pointing to all of the folders individually with the same starting order. In either case I get the newish terminals, but without the new jetways. A380 planes don't show up.
pommesschranke wrote in Tue Sep 27, 2016 1:14 pm:I noticed that AI Jetways are broken in 2016.3.1
here is a bugfix:
https://sourceforge.net/p/flightgear/ma ... /35381005/
Users browsing this forum: No registered users and 5 guests