23 minutes ago, simbol said:

having all add-on's on a single XML is a way around for this problem

That may be a misunderstanding, I didn't claim that anyone should do this at all. It was just an extreme example to drive home the point that you don't need individual XML files for evey single addon.

Why I like XML configurations (apart from it being (a) standard in IT) - there are so many things that you can do with them, without having to buy additional config software or simulator licenses. My pet example: I have an add-on.xml for ORBX, another for Ultimate Terrain, and a third with my photoreal scenery. I can switch to three different simulator flavors with little effort by activating one and deactivating the other two. One could add different shader settings, different aircraft libraries, different textures, different everything into the mix. Or think of one sim running aircraft, scenery and AI from the 1960s and another sim with current fare - on one single P3D installation, only a few mouse clicks away.

Best regards

Combining addons into less xml files surely does help. I have xml files combined after the manufacturer ie Aerosoft, FlyTampa, FSDG, T2G and so on. But even with combined xml entries i started seeing texture coruption. Then i have removed texture entries from xml, leaving only scenery entries of every addon and now it works okay.

3 hours ago, Johnny19 said:

Then i have removed texture entries from xml, leaving only scenery entries of every addon and now it works okay.

This is very interesting. Sounds like one very probable source of grief - too many lookup paths for a specific simulator resource lead to increased load times?? That would explain a lot, and it would imply that it is indeed better to add scenery as a scenery area (= targeting the top folder that contains \Scenery and \Texture) instead of adding \scenery and \texture separately.

Best regards

1 hour ago, Lorby_SI said:

This is very interesting. Sounds like one very probable source of grief - too many lookup paths for a specific simulator resource lead to increased load times?? That would explain a lot, and it would imply that it is indeed better to add scenery as a scenery area (= targeting the top folder that contains \Scenery and \Texture) instead of adding \scenery and \texture separately.

Best regards

Yeah, my entries look like this

.....

<AddOn.Component>
    <Category>Scenery</Category>
    <Path>E:\Prepar3D v4 Add-ons\Ecosystem\Aerosoft\Mega Airport Oslo 2.0\scenery</Path>
    <Name>Aerosoft - Oslo Gardemoen scenery</Name>
  </AddOn.Component>
  <AddOn.Name>Aerosoft - LIRF</AddOn.Name>
  <AddOn.Description>Aerosoft - Rome Int'l Airport for Prepar3D</AddOn.Description>
  <AddOn.Component>
    <Category>Scenery</Category>
    <Path>E:\Prepar3D v4 Add-ons\Ecosystem\Aerosoft\Rome2015\scenery</Path>
    <Name>Aerosoft - Rome scenery</Name>
  </AddOn.Component>

.....

Two additions:

1. AddOn.Name, AddOn.Description should appear only once in every XML, but AddOn.Component tags there can be many.

2. You should target "E:\Prepar3D v4 Add-ons\Ecosystem\Aerosoft\Rome2015", "E:\Prepar3D v4 Add-ons\Ecosystem\Aerosoft\Mega Airport Oslo 2.0" - lose the "\scenery".

Best regards

 

LM are planning an update soon I have seen posts listing some bugs are fixed in the coming update. I hope they fix this xml limit and scenery.cg corruption soon then. I'll stop adding scenery until then!

18 minutes ago, 777200lrf said:

LM are planning an update soon I have seen posts listing some bugs are fixed in the coming update. I hope they fix this xml limit and scenery.cg corruption soon then. I'll stop adding scenery until then!

Link?