Developer's Backdoor > Los Angeles LAX Backdoor
LAX for P3Dv5??
virtuali:
--- Quote from: trisho0 on July 20, 2021, 07:30:59 am --- I think the Installer needs attention.
--- End quote ---
The installer doesn't need any attention and, in fact, it's doing you a favor: is showing your DLL.XML from FSX has a problem, and is prompting you EXACTLY how to fix it. As the message says:
The problem was caused by another installer ( not ours ), which changed the file encoding without changing also the XML *header*, making the XML illegal, since if the header doesn't match the actual encoding of the file, the file is basically lying about itself. It's not we made up this: we are not trying to verify the XML ourselves, we use the official MS XML parser that comes with Windows, and we run the XML files through it, to be sure they are fine because, trying to modify a corrupted XML will probably corrupt it even more, so we check the file BEFORE making any changes to it.
Again, the problem was caused by another installer, that changed it, maybe to UTF-8, but FORGOT to ALSO change the header of the file which indicates the encoding, creating an illegal file.
The message you saw from out installer gave you the precise, exact, solution that is proven to work:
- Use a text editor, for example the free Notepad++, open the DLL.XML and save it back in ANSI format, which is the default FSX use.
trisho0:
--- Quote from: virtuali on July 20, 2021, 09:24:09 am ---The message you saw from out installer gave you the precise, exact, solution that is proven to work:
- Use a text editor, for example the free Notepad++, open the DLL.XML and save it back in ANSI format, which is the default FSX use.
--- End quote ---
Then, Notepad++ is not saving the xml file as intended. I follow the Setup Installer to create a new DLL.xml then comparing both I don't see difference the error. Posting the created file ...
<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>D:\Microsoft Games\Addon Manager\bglmanx.dll</Path>
</Launch.Addon>
</SimBase.Document>
This content is present in the DLL.xml file posted earlier. Where is the error?
---------------------------------------------------------------------------------------------------
EDIT: I found the windows Notepad is able to save the DLL.xml file in ANSI and issue resolved. I didn't find a way to save in ANSI with Notepad++.
Many thanks to Virtuali.
CorbiniansBear:
"or Lockheed Martin Prepar3D ( the latest version of every supported major release, for example 3.4 in P3D4 or 4.4 in P3D4 )"
I respectfully submit that this language is a bit ambiguous. especially since v4 scenery is not compatible with v5. I don't know about other people, but I'm very careful about avoiding anything not explicitly supported in v.5+ I know I have not bought LAX because of this. Yes, it could be read that it would work in v5.2, but using v4 as an example raises a question. Just saying, an update to the description might help sales. And yes, I'm a lawyer, so I am very sensitive to "statutory construction." :-) Merry Christmas and best wishes for a prosperous P3D New Year (especially with a v5 PHNL; if ORBX Vector is an issue, I think there is general agreement that it is not useful in v5, anyway, and FWIW I have deleted it without noticing any difference). I am continually amazed at the cleverness and sheer artistry (can't imagine the coding) for the pax. Keep up the great work!
virtuali:
--- Quote from: CorbiniansBear on December 23, 2021, 05:25:36 pm ---"or Lockheed Martin Prepar3D ( the latest version of every supported major release, for example 3.4 in P3D4 or 4.4 in P3D4 )"
--- End quote ---
--- Quote ---I respectfully submit that this language is a bit ambiguous.
--- End quote ---
No, it's just a web page that hasn't been updated after P3D V5 came out. But strictly speaking, if we wanted to replace it with an ACCURATE description of what really is our general approach to supporting various version, which should say something like:
the scenery is compatible with every version of the LAST major version of each supported simulator, but only with the latest version of previous major versions of the supported simulators.
Which really means:
- On FS9, we only support 9.1
- On FSX, we only support FSX SP2 or FSX:Steam, not FSX RTM or FSX SP1.
- On P3D 1, we support only 1.4 for V1, 2.5 for V2, 3.4 for V3, 4.4+ for V4 and every version of V5.
So, it's still not *totally* accurate, since we are support the latest *two* versions of P3D V4 and the latest *two* version of FSX, but it's "mostly" accurate. A "proper" accurate description should be some kind of product grid...
--- Quote ---especially since v4 scenery is not compatible with v5
--- End quote ---
I don't know why you are saying that. A native V4 scenery is very likely to work very well in V5, and lots of FSX sceneries work too. But that's only in general, the reality is more on a case-by-case and yes, in THIS case, KLAX DOES WORK IN P3D V5.
Our sceneries are quite different than the others so, any general rule you might have learn from other products, might not apply to us.
That's because part of what the scenery does, is handled in code, both in GSX ( they don't really work without ), but also specific code that, for example, when the scenery loads, displays dynamically different objects depending on the simulator used. KLAX is one of them, is able to self-modify the scenery files, even if you run FSX first and then run P3D, files are changed/updated/loaded differently in real-time depending on the simulator they run under. Some of them have their GSX/YouControl adapting to the version of the sim, and in P3D it changes if you are in Avatar mode.
--- Quote --- I don't know about other people, but I'm very careful about avoiding anything not explicitly supported in v.5+ I know I have not bought LAX because of this. Yes, it could be read that it would work in v5.2, but using v4 as an example raises a question.
--- End quote ---
You are making it far too complex than it really is. First, we have what I think is more clear sentence here, the one labeled with a big "IMPORTANT" sign, on the P3D 4/5 DOWNLOAD PAGE:
http://www.fsdreamteam.com/products_p3d.html
--- Quote ---IMPORTANT
This page indicates only those products that have a P3D4/5 Native version and don't work in FSX or older version of P3D ( 1, 2 and 3 ). On the FSX Products page, you'll find many other products that were originally made for FSX, but the installer supports all P3D version, including P3D V5.x
--- End quote ---
So, we are not just HONESTLY representing the products, saying that it was originally made for FSX (on that page you'll find only products *native* for P3D4/5 made using the P3D SDK that CANNOT work other than P3D4 or 5 ), but we are ALSO saying they have been tested to work in P3D V5 as well, and their installer fully supports it.
But that's besides the point.
The real point is, with our FSX/P3D products, the site Description and the System Requirements are not so important. That's because ALL PRODUCTS ARE SOLD IN TRY-BEFORE-BUY!. I'm sure nobody other than yourself is able to judge how well/bad they work in your simulator of interest.
CorbiniansBear:
Not trying to start an argument. It was really a suggestion for your benefit. Even after reading your post I'm still not sure if PHNL will work or not since the system requirements are the same and neither mention v5. I have tried both PHNL and KLAX and both crashed my vanilla P3D 5.2 setup. On the other hand, I have Chicago V2 and it works beautifully. And GSX2 is superb. Having bought one v4 scenery (from someone else) and it not working, I suppose I'm just careful. Best wishes for a happy and prosperous new year.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version