SODE SimObjectAnimationModule.dll

[Rafael M Silva 1]

I'm receiving this error message when starting the FSX, if I click ''Yes'' it crash the fsx to the desktop, if I click ''No'' SODE doesn't move the airport jetway, does anyone know how to fix this problem?

 

It began happen after I install an update to the Windows 10.

[Irishcurse 234]

Try uninstalling SODE and downloading a new version and reinstalling it.

[Rafael M Silva 1]

Try uninstalling SODE and downloading a new version and reinstalling it.

 

I did it, didn't work.

[Jim Young 2,356]

This is part of the FSDT program for your sim.  It is loaded via the dll.xml when you first startup FSX or P3D.  I am shocked that Windows10 would crash FSX because you said yes.  It means the dll.xml, which has the link to the module so it can be loaded at startup, may have two entries or the module is corrupted.  I would check the FSDT site for a solution.  I'm positive someone else had this issue.  You uninstalled and reinstalled but did you download and run the latest Addon Manager?  I believe there's a component missing in your dll.xml or exe.xml.  There's an entry in the exe.xml too but your message.  My version of the SimObjectAnimationModule is 1.3.3.  Yours is 1.3.4.  I thought I had the latest.  Perhaps there is something wrong with v1.3.4.

 

Best regards,

Jim

[Rafael M Silva 1]

This is part of the FSDT program for your sim.  It is loaded via the dll.xml when you first startup FSX or P3D.  I am shocked that Windows10 would crash FSX because you said yes.  It means the dll.xml, which has the link to the module so it can be loaded at startup, may have two entries or the module is corrupted.  I would check the FSDT site for a solution.  I'm positive someone else had this issue.  You uninstalled and reinstalled but did you download and run the latest Addon Manager?  I believe there's a component missing in your dll.xml or exe.xml.  There's an entry in the exe.xml too but your message.  My version of the SimObjectAnimationModule is 1.3.3.  Yours is 1.3.4.  I thought I had the latest.  Perhaps there is something wrong with v1.3.4.

 

Best regards,

Jim

 

I reinstalled the Addon Manager and the GSX and it's now working again, Thank you very much