Moving KBSO to outside folder

[wegerlee]

Hi guys. First of all congrats to the again oustanding scenery. I had been looking forward to it. Here comes the question. I know you can move the complete scenery to an outside folder (which I generyl do) and just add it with the XML add feature. What about the config library?? I now have AMS and the old sceneries in one Library, Vienna and Toronot in another and Boston in a third one?? Can we have a quick hint on how and where to move them. Thanks Elmar

[martin[flytampa]]

What about the config library?? I now have AMS and the old sceneries in one Library, Vienna and Toronot in another and Boston in a third one?? Can we have a quick hint on how and where to move them. Thanks Elmar

By Library you mean the old scenery.cfg / add-ons.cfg stuff right? All older FSX/P3D installers with ZIP patches (viewtopic.php?f=1&t=10302) can be added using the old scenery.cfg (Add Area) method. New Installers, currently CYYZ, LOWW and KBOS add themselves using the add-ons.cfg in /user/appdata/roaming/....

Not sure what you mean by "third one"? There is also a add-ons.cfg in /program data/, but we aren't using that one, although you could use that file as well (instead of user/appdata/roaming/, never use both for the same entry).

So If you move the whole FlyTampa folder containing both old and new airports, the old ones you can Edit the Scenery Library using the P3D Menu, World, Scenery Library GUI and select them and press Edit to point to the new folder locations. The new ones (CYYZ, LOWW, KBOS) you need to use one of the following methods, quoting PDF manual:

This Addon cannot be added via the traditional Scenery Library. Instead it must be
added to Prepar3D’s “add-ons.cfg”. Normally our Installer will do this automatically
but if it fails to do so you can add it by using one of the three methods described
below. Note that if the Addon is added using the traditional Scenery Library
method, there will be problems such as ground textures not loading, among other
issues
.
1. Go to the Prepar3D folder, subfolder /FlyTampa/Airport/ and run the file
labeled “Add-to-P3D.cmd”.

2. Run the following command line within the Prepar3D main folder, replacing
the path at the end according to where you installed the FlyTampa Addon:

Prepar3D.exe “-Configure: Category=Add-on Package,
Operation=Add, FileLocation=Roaming, c:\Prepar3D
v4\FlyTampa\Airport\”

3. Edit the “add-ons.cfg” in Notepad manually by loading the file:
C:\users\USERNAME\Appdata\Roaming\Lockheed
Martin\Prepar3D v4\ add-ons.cfg
Add an entry to this file similar to the following:

[Package.1]
PATH=C: \Prepar3D v4\FlyTampa\Airport
ACTIVE=true
REQUIRED=false

[wegerlee]

Hi Martin

My apologies for not being clear in my first post. I currently have the old sceneries (with zip files) installed the updated ones for Toronto and Vienna and KBOS.

I moved all the old sceneries into a folder called Airports and manually wrote the XML addon file and it works great. I also moved Vienna and Toronto to Airport/New Flytampa and added them with the xml cmd command...works fine. KBOS is still within the sim but I will move it. What I am trying to say is that I now have 3 Library config exe files for each one- the old sceneries - the Vienna /Toronto - and KBOS. All three are added in the SIM with XML. Is there anyway I can just have one library config or at least two - one for the old scenries and one for the new ones by simply moving VIE and Toronto scenery plus images plus scripts and libraries for example together with the KBOS folder? I could try and I have now idea if that would mess up my sim??

[wegerlee]

Martin

Meantime I played around with the scenery (after backung it up) and answered my own questions:

I moved KBSO into the New folder which contains Toronto and Vienna. I also moved the library, scripts aand images. I also copies the Fly-Tampa Configurator.exe file over and overwrote the other one. Added via CMD both to the SIM and it seems to work fine. I know have BOS VIE and Toronot in one configurator. So far so good. If I can get Dubai AMS and the rest in there using the same method I should have only one Conigurator???? I hope

Your thoughts

Thanks Elmar

[martin[flytampa]]

Understood now... The Config Tool EXE reads the /scripts/ and /images subfolders. What Airports you can see in the Config Tool depends on what files it finds in/scripts/. If you have a look at any of the XML files in /script/ you maybe able to figure out how it work. Because it uses relative paths in the XML, like "Vienna\scenery\people_ramp.bgl" the airport Folders themselves cannot be renamed and need to be subfolders under where the Config Tool exe is. If you were to edit the XML files with absolute paths for example, like "d:\addons\Vienna\scenery\people_ramp.bgl" you could in theory also use the config tool from any other location, without it needing to be in relation to the Airport folder.

[kenthom]

. Go to the Prepar3D folder, subfolder /FlyTampa/Airport/ and run the file
labeled “Add-to-P3D.cmd”.

I put my airports in my E: drive HDD. So to be clear; I can simply run the above file after moving the complete FlyTampa file to the the E: drive and all will be well?

By the way, love the airport! Waiting impatiently for KLAS.

Thanks,

Ken

[martin[flytampa]]

. Go to the Prepar3D folder, subfolder /FlyTampa/Airport/ and run the file
labeled “Add-to-P3D.cmd”.

I put my airports in my E: drive HDD. So to be clear; I can simply run the above file after moving the complete FlyTampa file to the the E: drive and all will be well?

By the way, love the airport! Waiting impatiently for KLAS.

Thanks,

Ken

Correct, you move the whole FlyTampa folder to E and afterwards run /FlyTampa/Airport/Add-to-P3D.cmd

A note on that. If you also have other, older, patched FlyTampa Airports in the /FlyTampa/ folder that will get moved to E as well, those you will have to manually edit (after moving) using the Scenery Library within P3D. Only the new releases (KBOS, LOWW, CYYZ) have the Add-to-P3D.cmd. Note2: If the Add-to-P3D.cmd fails, do not despair, there are other methods of re-adding the entry described in the PDF manual.

[kenthom]

Thanks Martin,
Yes, I have had the older airports in my E: drive for a long time. Not wanting to confuse everything I named the file FlyTampa Old. So hopefully the move of the newer FlyTampa airports to the FlyTampa folder will work.

[martin[flytampa]]

Thanks Martin,
Yes, I have had the older airports in my E: drive for a long time. Not wanting to confuse everything I named the file FlyTampa Old. So hopefully the move of the newer FlyTampa airports to the FlyTampa folder will work.

Oh, it will work for sure. Moving these new releases around is much better then the old ones because they are self-contained including all the Effects etc that were previously in the Sim's default /effects/ etc folders. Worst case if the Add-to-P3D.cmd fails, all you have to do is edit the add-ons.cfg in notepad and write 3 lines pointing to the new E location... which is very similar to editing the old scenery.cfg

Only issue if you keep them in separate FlyTampa-Old and FlyTampa-New type folders, is the Config Tool. If you don't use the Tool nevermind. If you do, just know you would need to have a copy of the Config Tool EXE (as well as scripts and images folders) in each FlyTampa folder and then you have to look in each /scripts/ folder and check that only the corresponding airport XMLs are in there.

[kenthom]

Hi Martin,

It worked perfectly. Thanks.

Ken