Thanks for all the help - still cannot get it to work. I have downloaded notepad++ then found the dll and exe XML files - choose convert to ANSI - and they still appear as XML files!!!
You are confusing file encoding, with file type. Of course the files will continue to be XML files. Do you know what file encoding is ? XML files, and any other file on your system can be encoded in many different ways, to support non-ANSI characters.
The error is caused by the fact that either you, or ANOTHER product defective installer, has CHANGED the file encoding from the default, which is Windows-1252, to another encoding, WITHOUT also changing the header, which likely still reads as follows:
<?xml version="1.0" encoding="Windows-1252"?>
Which is CORRECT, and it's how the file is shipped with in P3D. But, if the *actual* file encoding doesn't match what it has been indicated on the header, the file is now basically "lying about itself", because it starts saying the encoding is Windows-1252, when it's really not. This would obviously confuse the XML parsing routine built in Windows, since the file is now illegal.
I'm sure that, if you tried to open the file with Internet Explorer, it will not be able to open it because IT IS illegal! So, how do you expect we could work on that file with our installers, which obviously use the same XML parser routines that are included in Windows, when not even Internet Explorer *itself* can open the file ??
That's why, the solution is:
- Open the XML with Notepad++
- Change the encoding to ANSI
- Save it back. Yes, it will STILL an XML file, and that's correct: just the encoding will now match the header.
Repeat this for ALL the 4 XML files you have in the P3D folders, as I indicated in the previous post.
What gets me is that I only purchased this software last week - it said it was compatible with P3D
Of course it is.
and clearly there are some known issues
There are no "issues" with it. If you are still getting *that* message about the wrong file encoding when installing, it's because your XML file IS an illegal XML and this is caused by either:
- A defective installer of ANOTHER product, which mistakenly changed the encoding without changing the XML header, making it an illegal XML file, that even Internet Explorer itself cannot open
OR
- Having hand-edited with with an editor that changed the encoding on saving.
which would have been good to know beforehand.
Since the error caused by your corrupted XML files happens when installing, it would be clear when installing the Trial version so yes, you COULD have known beforehand, if you did what you are supposed to do for any product sold as a Try-Before-Buy: installing it and THEN purchasing it.
Not that this doesn't change anything, since this is NOT a "GSX issue", it's an already existing problem in your XML files that doesn't normally happens on a normal P3D install, since the sim doesn't obviously come with corrupted files.
I now have software that does not work with my setup of P3D. Does anyone know if a patch is going to be released
No patch is needed on our side since, of course, this is NOT a problem we should fix, since it's caused by your XML files being corrupted. In fact, the installer is doing you a useful service, telling the file are already corrupted, and it would be wrong if it would try to "fix" them, since trying to fix an-already corrupted file would likely cause even more problems.
The installer won't dare to touch corrupted files: it will just indicating they are, so you can take the appropriate course of action.
