• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

P3D v3 ANIMATION MODULE DLL XML COULD NOT BE READ

Messages
1,964
Country
unitedkingdom
I was trying to use Chase Plane in P3D v3, and it basically stopped working, and said it didn't support my version of P3D, despite it working before.

Anyway, it messed up my P3D, so it would crash when opening my most recent save file, perhaps made after this. Uninstalled chase plane, but noticed SODE stopped working, despite being able to reload the jetways, and them showing in the sim, the menu didn't open, or the DLL check box wouldn't display.

So I tried to deactivate it, and got this error message:

20621187_1914984705381514_3046710729091535995_n.jpg


And upon Reactivating it:

20621235_1914984702048181_678945384432152234_n.jpg


I uninstalled SODE completely, and deleted the 12bpilot folder.

Reinstalling it and trying to activate it in v3 gives the same problem. But FSX, FSX SE and v4 are fine.

Looks like I'll have to reinstall v3?
 
That window you see comes directly from Prepar3D.exe. It says that your DLL.xml file is invalid/corrupted and therefore can't add SODE to it.

Corruption of DLL.xml happens when add-ons try to insert their entries by directly editing the core config files and do mistakes during that process. That's why SODE uses the indirect approach of letting Prepar3D.exe do that file editing. But this safe approach is useless when the core config file is corrupted in the first place.

Most of the time, it is a simple syntax error or some xml element is missing.

The file in question is C:\ProgramData\Lockheed Martin\Prepar3D v3\dll.xml.
There are online xml validators available where you can copy-paste the contents of the dll.xml and run a test. It will then say what is wrong in your file syntax-wise.
 
Oh right, I haven't modified it. But it stopped working after Chaseplane ruined P3D v3.

I uninstalled and reinstalled v3, but think this corrupt dll.xml remained as SODE registers fine now but wont actually display the animations in v3, and crashes on "reload all" with

Problem signature:
Problem Event Name: APPCRASH
Application Name: SimObjectDisplayEngine.exe
Application Version: 1.5.3.0
Application Timestamp: 594a8194
Fault Module Name: SimObjectDisplayEngine.exe
Fault Module Version: 1.5.3.0
Fault Module Timestamp: 594a8194
Exception Code: c0000005
Exception Offset: 00068e71
OS Version: 6.3.9600.2.0.0.768.101
Locale ID: 2057
Additional Information 1: 1e5d
Additional Information 2: 1e5d0d2c6fec87d873489f072c940d92
Additional Information 3: d174
Additional Information 4: d174c6a6ebdbaf7ba8db5e4f2fa654dd

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=280262

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-GB\erofflps.txt

I'll have a look and see whats wrong with dll.xml.

Thanks!
 
I get an error at, can't see it's relationship to SODE though.

17 <SimBase.Document Type="Launch" version="1,0">

..................................................................................................................................

1 <?xml version="1.0" encoding="Windows-1252"?>
2
3 <SimBase.Document Type="AceXML" version="3,0" id="dll">
4 <Descr>AceXML Document</Descr>
5 <Filename>dll.xml</Filename>
6 <Launch.Addon>
7 <Name>Flight Recorder</Name>
8 <Disabled>False</Disabled>
9 <ManualLoad>False</ManualLoad>
10 <Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path>
11 </Launch.Addon>
12 </SimBase.Document>
13
14
15
16
17 <SimBase.Document Type="Launch" version="1,0">
18
19 <Descr>Launch</Descr>
20
21 <Filename>dll.xml</Filename>
22
23 <Disabled>False</Disabled>
24
25 <Launch.ManualLoad>False</Launch.ManualLoad>
26
27 <Launch.Addon>
28
29 <Name>FSUIPC 4</Name>
30
31 <Disabled>False</Disabled>
32
33 <Path>Modules\FSUIPC4.dll</Path>
34
35 </Launch.Addon>
36
37
38
39 <Launch.Addon>
40
41 <Name>A2A Feel</Name>
42
43 <Disabled>False</Disabled>
44
45 <Path>Modules\A2A_Feel.dll</Path>
46
47 <DllStartName>module_init</DllStartName>
48
49 <DllStopName>module_deinit</DllStopName>
50
51 </Launch.Addon>
52
53 <Launch.Addon>
54
55 <Name>AccuFeelMenu</Name>
56
57 <Disabled>False</Disabled>
58
59 <ManualLoad>False</ManualLoad>
60
61 <Path>Modules\AccuFeelMenu.dll</Path>
62
63 </Launch.Addon>
64
65
66
67 </SimBase.Document>
 
With a general XML syntax problem reported by the Prepar3D.exe, there doesn't have to be a relation to SODE at all.
Without having your original dll.xml, I can't tell you what ominous character hides in line 17, but as you already found out, there is the bad boy that renders your dll.xml invalid!

Just fix that incorrect xml manually and re-register SODE.
 
I checked an old backed up copy of dll.xml, and it's exactly the same.

I guess it's nothing to do with this. Chaseplane did some real damage to this installation. When I uninstalled v3, I should have deleted everything here in the v3 program data folder.
 
Back
Top