Scnenary add on crash with xml

[cannow]

I have been using the xml method of adding scenery using Lorby Si tool . Have hit a problem installed last night  orbx eu freeware airports last night and it crashed after the scenario window .Uninstalled and all worked reported on forum and no one has had an issue . Today I installed naples from aerosoft same issue . After hours of head scratching I disabled all xml add ons . Sim loaded fine. I found if I disabled any two xml add ons all was good in the world again. Added the disabled xml scenery's manually the old way and all scenery's . Almost as if there is a cap on how many .xml addons you can have . 
Anybody else had this before .

[LRW]

I've been dealing with the same issue today.  When trying to start a scenario with the PMDG 747, 777, or TFDi 717, I get either 1) CTD from api.dll, 2) CTD from ntdll.dll, or 3) P3D exiting with no error message. The exceptions were all the normal 0xc0000005, except for one 0xc0000094 (divide by zero). 

I found that the problem went away when I disabled the UK2000 Heathrow and LatinVFR San Juan (TJSJ), both installed with their P3D v4 installers.  I have the latest v4 hotfix installed.  

I next deleted the prepar3d.cfg and, when I tried to start a scenario with the 747, I got an error I haven't seen before: 0xc0000374 in ntdll.dll, a heap corruption exception.

Log Name: Application
Source: Application Error
Date: 7/8/2017 5:59:25 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: i5-3570K
Description:
Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255
Faulting module name: ntdll.dll, version: 10.0.15063.0, time stamp: 0xb79b6ddb
Exception code: 0xc0000374
Fault offset: 0x00000000000f775f
Faulting process id: 0xd8
Faulting application start time: 0x01d2f83d956346c7
Faulting application path: P:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: bcc44bd2-94a4-4810-ae0f-e0db0695ee86
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-07-08T22:59:25.796398200Z" />
<EventRecordID>8662</EventRecordID>
<Channel>Application</Channel>
<Computer>i5-3570K</Computer>
<Security />
</System>
<EventData>
<Data>Prepar3D.exe</Data>
<Data>4.0.28.21686</Data>
<Data>594a7255</Data>
<Data>ntdll.dll</Data>
<Data>10.0.15063.0</Data>
<Data>b79b6ddb</Data>
<Data>c0000374</Data>
<Data>00000000000f775f</Data>
<Data>d8</Data>
<Data>01d2f83d956346c7</Data>
<Data>P:\Lockheed Martin\Prepar3D v4\Prepar3D.exe</Data>
<Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data>bcc44bd2-94a4-4810-ae0f-e0db0695ee86</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

[Ffm888]

I have the exact same problems here. Certain combinations of sceneries lead to instant CTDs right after the scenerio setup screen. And it is only a certain combination that leads to a problem. Just to give you an example: I installed Pacsim KSLC with a proper P3Dv4 installer today and got the above mentioned CTD right after the scenario setup. BUT: When I de-activate the Orbx CRM and NRM region, I can startup the sim without getting a crash (which appeared after the installation of Pacsim KSLC). When I activate the Orbx CRM and NRM regions and de-activate Pacsim KSLC then the sim also works without problems. It is only the combination of the the add-ons which doesn't work. This is completely strange and I am pretty confident that it must be a problem of P3D as the add-ons themselves work without any problem if not combined with other add-ons.

Edit: The error is reproducable even without using a single add-on via the add-on xml procedure. Only using scenery.cfg produces the same error.

[Ffm888]

Quick update: I followed the advice given by someone in the Orbx forum and de-activated all add-on.xml files. Now Orbx CRM and NRM work just fine together with Pacsim KSLC. So this seems to really boil down to a problem with the add-on.xml functionality of P3D.

[Rob McCarthy]

Thanks for your continued updates on the issue. We will look into a fix.

Regards,
Rob McCarthy

[honanhal]

I am seeing this same problem, which is also fixed by disabling the Latinvfr TJSJ addon.xml entry. Is there a fix in the works for this addon.xml problem?

[Clifton Crane]

Hello,

We believe we have resolved this issue. The fix will be available in the next release.

Thanks!