Jump to content
Sign in to follow this  
Flyboy

SODE & GSX install XML Runtime error

Recommended Posts

Evening folks...

Below are the errors I get when trying to install GSX to P3D V3 after having installed SODE.

My initial install was "Tropical Sim" SAEZ 2016 which comes SODE ready.

Downloaded and installed the latest version of SODE

Alls well, Have SODE Jetways at SAEZ 2016

Install three FS DREAMTEAM Airports....

All is good....

Install GSX.... Boom.

These are what happened

Interesting thing is that when I tried to uninstall the FS Dreamteam products along with COATI addon installer....

The same errors came up..

Somewhere I read it has to do with a DLL.XML?

I havent the faintest and thought someone else might have had this issue,,,,

Anything stand out in the images?

 

Image 1: Just after closing SODE Registration window.... 

http://fsfiles.org/flightsimshotsv2/image/GmIt

 

Image 2: Closing thge runtime error popup

http://fsfiles.org/flightsimshotsv2/image/GmIQ

 

Image 3: After closing the last error.. Leaves my instalation window frozen as in image.

http://fsfiles.org/flightsimshotsv2/image/GmIa

 

Share this post


Link to post
Share on other sites

 

 


Somewhere I read it has to do with a DLL.XML?

 

Whenever you install GSX and SODE and FSDT airports, part of the installation will be to place entries in your dll.xml and exe.xml.  There are currently two folders that could contain the dll.xml and exe.xml and the required entries for FSDT and SODE.  One is in the same folder as where your P3D.cfg is located.  The other is the same folder as where your scenery.cfg is located for P3D.  Both are hidden folders.  On page 5 of the AVSIM CTD Guide, I show the location of these hidden folders.  Rob Ainsworth just published the AVSIM P3D Guide and he has the location of these folders and entries too.  The standard installation folder FSDT uses for the dll.xml is the folder where the scenery.cfg is located (which is the new location for P3D).  You want to make sure you do not have the entries in the dll.xml and exe.xml in the folder where your p3d.cfg is located and also in the dll.xml and exe.xml where your scenery.cfg is located.

 

If the entries are not in the dll.xml or exe.xml then you can try to fix it by downloading the latest Standalone Addon Manager.  Just go to the Products and select GSX and then click on Addon Manager and install it.  It will make sure your installation was properly done.  According to Image 1, SODE is properly installed.  Image 2 - List index out of bounds - see the following link at FSDT Forums - http://www.fsdreamteam.com/forum/index.php?topic=14306.0.  Image 3 - Adding Addon Manager to dll.xml file, indicates to me it is adding the file or checking for the file.  Again, just run the Standalone Addon Manager again.

 

These issues are not really P3D issues.  If you cannot get it resolved with my suggestions above, I would go to the FSDT Forums, sign in and post your problem there.  The developer is extremely helpful IMHO.

 

Best regards,

Jim


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

Jim.. Thanks so much...

Interesting that I can spend hours on the internet looking for error codes and similar issues and give up finally to post something about it as I did....

I hate depending on others and am a problem solver by nature...

I found the fsdreamteam post about the dll.xml

That was the issue...

Some how someway, my dll.xml go modified with a w at the end....

 

This is the last entry.... And some installation put that there....

my first guess is the last install I did which was ejets....

For what its worth...

 

This wont work....

-------------------------------------------------

<Launch.Addon>
    <Name>FeelThere EJetX Helper</Name>
    <Disabled>False</Disabled>
    <Path>FeelThere\E170\EJetH.dll</Path>
  </Launch.Addon>
</SimBase.Document>
W
------------------------------------
I took out the W, saved and wala!
 
Anyhow, thank you again for the advice....
It aint the first and wont be the last but somehow it is a pattern that as soon as I post it... I end up figuring it out..\
All my best...
 
Flyboy53

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...