General Category > General Discussion

FSX-SE and Scenery/coualt problem **SOLVED**

<< < (2/2)

carl42:

Could this be in support of what you stated?  I used stand-alone add-on manger instead of FSDT live update and received the following:
“c: user\...\...\..\..\msft\FSX\dll.xml error on line 1. Position 46: switch from current encoding to specified coding not supported.  This error file has been with an encoding that doesn’t match the XML header and it’s usually caused by 3rd party installation with bugs. It should be fixed by opening with an editor like free notepad ++ and save it back in ANSI format. “

Next message: “since your dll.xml was corrupted before starting the installer, do you want to install a new one? yes or no”  I chose “no”.
I did not receive this message when using the FSDT live update.

I will wait before trying your suggestion earlier to see if they may change things. Maybe have two problems to work on?

Your help in solving this problem is greatly appreciated.

virtuali:

--- Quote from: carl42 on December 18, 2017, 05:16:42 pm ---Next message: “since your dll.xml was corrupted before starting the installer, do you want to install a new one? yes or no”  I chose “no”.
--- End quote ---

This might be or not a problem, depending if you had or not our software installed before getting this message. If you started from scratch, with no FSDT software installed, this error would result in our modules not even installed, but then it wouldn't be possible they would crash, as you reported it.

So, it seems you already had them installed before so, even if your XML has an illegal encoding, due to a defective installer of another product, or by having opened/saved with an editor without taking care of the encoding, it might not be sure the sim will reject it. It's just not XML standard, according to the Windows standard XML parsing routines which we use in the installer, but that doesn't mean the sim won't be able to use it anyway.

It's just that we don't try to touch what is not 100% XML standard, because if we tried to do that, since we DO use the Window standard XML routines to change it, if it wasn't 100% clean before, we'd end up corrupting it.


--- Quote ---I did not receive this message when using the FSDT live update.
--- End quote ---

The FSDT Live Update will just update FSDT files, but it won't care about your sim configuration files anymore. Those problems are only dealt with by the installers
, since it's assumed that you must have installed the full product once, to run the update.


--- Quote ---I will wait before trying your suggestion earlier to see if they may change things. Maybe have two problems to work on?
--- End quote ---

Possibly but, first try my suggestion of disabling everything except our modules and, while you are at it, follow the installer suggestion to fix your XML and save it as Ansi.

carl42:
Thanks Virituali for your helpful responses.

I have attached my XML files using your suggestions. Changing “false to true” did not indicate any changes to the FSDT problem.(That is assuming the changes were made correctly). I reverted back to original XMLs. All of the FSDT sceneries were installed on new laptop over the last three months with no problems.  After the install of Windows 10 update 1709 there are times when Couatl would not show up in the menu unless there are non-FSDT airports on start-up. If you change to a FSDT airport Couatl may or may not be shown active in the menu, thus FSDT airports would not show properly. If I change aircraft that will cause an installed FSDT airport to lose all buildings etc and Couatl to disappear. It’s like Couatl has a mind of its own. There have been no crashes to desktop with this problem. If FSDT airport has a problem I just switch to another non FSDT airport.
I do feel like a computer dummy since I am unable to understand what I should do to correct the possible problem stated below.
 “\dll.xml error on line 1. Position 46: switch from current encoding to specified coding not supported.  This error file has been with an encoding that doesn’t match the XML header and it’s usually caused by 3rd party installation with bugs. It should be fixed by opening with an editor like free notepad ++ and save it back in ANSI format. “
Would as a last resort uninstall all FSDT scenery and reinstall be a solution?
Hope this was not too confusing to what is going on. I am still able to use FSDT scenery on occasions which is a good thing.  

virtuali:

--- Quote from: carl42 on December 21, 2017, 09:01:40 pm ---I do feel like a computer dummy since I am unable to understand what I should do to correct the possible problem stated below.  “\dll.xml error on line 1. Position 46: switch from current encoding to specified coding not supported.  This error file has been with an encoding that doesn’t match the XML header and it’s usually caused by 3rd party installation with bugs. It should be fixed by opening with an editor like free notepad ++ and save it back in ANSI format. “
--- End quote ---

I'm not sure how I could explain it any better than what the error message says:


--- Quote ---It should be fixed by opening with an editor like free notepad ++ and save it back in ANSI format.
--- End quote ---


--- Quote ---Would as a last resort uninstall all FSDT scenery and reinstall be a solution?
--- End quote ---

You can try it, but it's best if you fix ALL your XML files first.

carl42:
Umberto,  Good news, the  problem has been fixed. Ran the stand alone addon manager again and no problem.  Still had the problems especially in the KCLT, KMEM, and KSDF with missing Couatl. Since I had not installed GSX  gave it a try and installed no problem.  Now all FSDT scenery are working.  
Thanks again for your help.  Learned a lot with this problem.

Kind regards,

Navigation

[0] Message Index

[*] Previous page