Did anybody succeed in installing FlyTampa's Amsterdam outside of Prepar3D v4 directory? Then using add-on.xml method?

I tried to install Amsterdam in a directory outside of Prepar3D v4, but had some xml errors and weired folder structure, whereas the installer created additional Prepar3D v4 Add folder and many other problems.

For what it matters Aerosoft's Heathrow Prof did install very well outside of Prepar3D with add-on.xml and Lorby's AddonOrganizer.

Thanks,

 

Did they update the installers for v4 ? I still have the old installer which requires the folders to be added manually. I prefer to add the FlyTampa sceneries manually to the scenery library as the Amsterdam_LC folder needs to be below the Amsterdam folder. 

16 minutes ago, ninerwhiskey9W said:

Did they update the installers for v4 ? I still have the old installer which requires the folders to be added manually. I prefer to add the FlyTampa sceneries manually to the scenery library as the Amsterdam_LC folder needs to be below the Amsterdam folder. 

Not yet, they are recompiling and updating their airports for v4 rather than just creating a new installer. At least that’s what they’re doing with Montreal and it is assumed that it will be the same for the rest of their sceneries.

35 minutes ago, ninerwhiskey9W said:

Did they update the installers for v4 ? I still have the old installer which requires the folders to be added manually. I prefer to add the FlyTampa sceneries manually to the scenery library as the Amsterdam_LC folder needs to be below the Amsterdam folder. 

Sorry question

Did you add Amsterdam_LC in the library as add-on.xml if I do it the afcad goes below the scenery so the aircraft is below the terrain.

 

9 minutes ago, simbio said:

Sorry question

Did you add Amsterdam_LC in the library as add-on.xml if I do it the afcad goes below the scenery so the aircraft is below the terrain.

 

I'm not sure how the add-on.xml works with sceneries that require multiple layer, If you are using a common add-on.xml, I would suggest reversing the order,

Otherwise, You can add the <layer>xxx</layer> tag to the add-on.xml entry to specify the exact layer number, but this causes the problem if you need to add sceneries below this layer as you will have to edit the xml file each time. Which is why I use the direct method whenever dealing with such scenery. Makes moving them around much easier.

If the problem is not fixed, you could post the content of your addon.xml here and someone can correct it.

I have my P3D installed to c:\ drive and all my addon scenery installed to d:\addon and here is what my FlyTampa add-on.xml looks like.  Notice how the library entry and various LC entries are ordered.  In general, objects are loaded in order read so first read is on "bottom."

<SimBase.Document Type="AddOnXml" version="4,0" id="add-on">
	<AddOn.Name>FlyTampa</AddOn.Name>
	<AddOn.Description>FlyTampa AddOn Sceneries</AddOn.Description>
	
	<AddOn.Component>
		<Name>FlyTampa Libraries</Name>	
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Libraries</Path>
	</AddOn.Component>	
	
	<AddOn.Component>
		<Name>EHAM Amsterdam Schiphol - LC</Name>	
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Amsterdam_LC</Path>
	</AddOn.Component>	
	<AddOn.Component>
		<Name>EHAM Amsterdam Schiphol - Airport</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Amsterdam</Path>
	</AddOn.Component>

	<AddOn.Component>
		<Name>LGKR Corfu - LC</Name>	
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Corfu_LC</Path>
	</AddOn.Component>		
	<AddOn.Component>
		<Name>LGKR Corfu - Airport</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Corfu</Path>
	</AddOn.Component>

	<AddOn.Component>
		<Name>YSSY Sydney Kingsford Smith - LC</Name>	
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Sydney_LC</Path>
	</AddOn.Component>		
	<AddOn.Component>
		<Name>YSSY Sydney Kingsford Smith - Airport</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Sydney</Path>
	</AddOn.Component>

	<AddOn.Component>
		<Name>EKCH Copenhagen Kastrup - LC</Name>	
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Copenhagen_LC</Path>
	</AddOn.Component>			
	<AddOn.Component>
		<Name>EKCH Copenhagen Kastrup - Airport</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Copenhagen</Path>
	</AddOn.Component>

	<AddOn.Component>
		<Name>CYUL Montreal Pierre Elliott Trudeau</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Montreal</Path>
	</AddOn.Component>
	
	<AddOn.Component>
		<Name>OMDB Dubai - LC</Name>	
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Dubai_LC</Path>
	</AddOn.Component>	
	<AddOn.Component>
		<Name>OMDB Dubai - Airport</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Dubai</Path>
	</AddOn.Component>

	<AddOn.Component>
		<Name>TNCM St Maarten Princess Juliana</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\StMaarten</Path>
	</AddOn.Component>
	
	<AddOn.Component>
		<Name>KMDW Chicago Midway</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Midway</Path>
	</AddOn.Component>

	<AddOn.Component>
		<Name>KBUF Buffalo Niagara</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Buffalo</Path>
	</AddOn.Component>

</SimBase.Document>

Hope this helps.

Thanks for help both of you

1 hour ago, downscc said:

I have my P3D installed to c:\ drive and all my addon scenery installed to d:\addon and here is what my FlyTampa add-on.xml looks like.  Notice how the library entry and various LC entries are ordered.  In general, objects are loaded in order read so first read is on "bottom."

<SimBase.Document Type="AddOnXml" version="4,0" id="add-on">
	<AddOn.Name>FlyTampa</AddOn.Name>
	<AddOn.Description>FlyTampa AddOn Sceneries</AddOn.Description>
	
	<AddOn.Component>
		<Name>FlyTampa Libraries</Name>	
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Libraries</Path>
	</AddOn.Component>	
	
	<AddOn.Component>
		<Name>EHAM Amsterdam Schiphol - LC</Name>	
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Amsterdam_LC</Path>
	</AddOn.Component>	
	<AddOn.Component>
		<Name>EHAM Amsterdam Schiphol - Airport</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Amsterdam</Path>
	</AddOn.Component>

	<AddOn.Component>
		<Name>LGKR Corfu - LC</Name>	
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Corfu_LC</Path>
	</AddOn.Component>		
	<AddOn.Component>
		<Name>LGKR Corfu - Airport</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Corfu</Path>
	</AddOn.Component>

	<AddOn.Component>
		<Name>YSSY Sydney Kingsford Smith - LC</Name>	
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Sydney_LC</Path>
	</AddOn.Component>		
	<AddOn.Component>
		<Name>YSSY Sydney Kingsford Smith - Airport</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Sydney</Path>
	</AddOn.Component>

	<AddOn.Component>
		<Name>EKCH Copenhagen Kastrup - LC</Name>	
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Copenhagen_LC</Path>
	</AddOn.Component>			
	<AddOn.Component>
		<Name>EKCH Copenhagen Kastrup - Airport</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Copenhagen</Path>
	</AddOn.Component>

	<AddOn.Component>
		<Name>CYUL Montreal Pierre Elliott Trudeau</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Montreal</Path>
	</AddOn.Component>
	
	<AddOn.Component>
		<Name>OMDB Dubai - LC</Name>	
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Dubai_LC</Path>
	</AddOn.Component>	
	<AddOn.Component>
		<Name>OMDB Dubai - Airport</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Dubai</Path>
	</AddOn.Component>

	<AddOn.Component>
		<Name>TNCM St Maarten Princess Juliana</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\StMaarten</Path>
	</AddOn.Component>
	
	<AddOn.Component>
		<Name>KMDW Chicago Midway</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Midway</Path>
	</AddOn.Component>

	<AddOn.Component>
		<Name>KBUF Buffalo Niagara</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\FlyTampa\Buffalo</Path>
	</AddOn.Component>

</SimBase.Document>

Hope this helps.

Dan, how about those root folders outside FlyTampa folder(namely Autogen, effects, scenery), where the installer also puts files necessary for the scenery to work properly?

Thanks,

1 hour ago, Dirk98 said:

Dan, how about those root folders outside FlyTampa folder(namely Autogen, effects, scenery), where the installer also puts files necessary for the scenery to work properly?

Thanks,

Either way..., if the installer puts files in <p3d>\Autogen or \Effects then I don't disturb.  If the installer puts the files in Addon\Autogen, \Effects or \Scenery then that is covered with this add-on.xml, which I put in a Prepar3D v4 Addon Documents folder named "aaGlobal" to be read first:

<SimBase.Document Type="AddOnXml" version="4,0" id="add-on">
	<AddOn.Name>Global Data</AddOn.Name>
	<AddOn.Description>AddOn Scenery Global Elements</AddOn.Description>
	
	<AddOn.Component>
		<Category>Autogen</Category>
		<Path>D:\Addon\Autogen</Path>
	</AddOn.Component>
	<Addon.Component>
		<Category>Effects</Category>
		<Path>D:\Addon\effects</Path>
	</Addon.Component>
	<AddOn.Component>
		<Name>AddOn Scenery World</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\scenery\world</Path>
		<Layer>3</Layer>
	</AddOn.Component>
	<AddOn.Component>
		<Name>AddOn Scenery Global</Name>
		<Category>Scenery</Category>
		<Path>D:\Addon\scenery\Global</Path>
		<Layer>3</Layer>
	</AddOn.Component>
	<AddOn.Component>
		<Category>SimObjects</Category>
		<Path>D:\Addon\SimObjects\Boats</Path>
	</AddOn.Component>
	<AddOn.Component>
		<Category>Sound</Category>
		<Path>D:\Addon\Sound</Path>
	</AddOn.Component>
	
</SimBase.Document>

The next to last component is specifically for FlyTampa, which puts simobjects in a subfolder of simobjects so note the path goes down one layer.  The P3D process will automatically look below Addon\SimObject\Boats for the 13 different FlyTampa simobjects.

4 hours ago, downscc said:

Either way..., if the installer puts files in <p3d>\Autogen or \Effects then I don't disturb. 

Thanks, your scripts are VERY helpful. I didn't get this part above though. Why wouldn\t you disturb? It's not much different from what you've done already. Generally the whole point of tinkering with add-on.xml-s is to have add-on sceneries completely out of Prepar3D v4 structure, so that a newer P3Dv4 update wouldn't disturb your add-on sceneries, isn't it?

Dirk,

PS: now I got it: root Autogen, Effects and other folders are out of add-on.xml structure. They are referred to in autogen.cfg, effects.cfg and other cfg files, so that you could still keep your Prepar3D v4 pristine. 

 

Thanks!

Edited December 9, 20178 yr by Dirk98

Ok, in case of current FlyTampa sceneries it's rather impossible to install them completely out of Prepar3D v4 folder as the installer writes something in default.xml residing in the root Autogen folder. And this file is coded, so you can't see what lines are added by FlyTampa with a regular xml viewer.

Dirk.

 

19 hours ago, Dirk98 said:

Ok, in case of current FlyTampa sceneries it's rather impossible to install them completely out of Prepar3D v4 folder as the installer writes something in default.xml residing in the root Autogen folder. And this file is coded, so you can't see what lines are added by FlyTampa with a regular xml viewer.

Dirk.

 

Exactly, that is why I said earlier that if the installer writes to <p3d>\autogen then I leave alone. The concept is to maintain uniformity without making it difficult.

So why bother doing a lot of work and still  you cannot install it completely outside the root folder ?

I choose the easy install way and use SCE for quick dis- and enabling of the sceneries..

After an install I take the addon and put it outside P3D . I only have to point to the new path with SCE.

In case of a complete reinstall I copy Texture , Autogen , Effects , Sounds and Modules to a save place.. After reinstall I copy them back.. That takes less than 5 minutes total.

It’s as easy as can be ...

regards, Gerard