May 12, 201313 yr After seeing others with issues after installing the new FSUIPC, I thought I had avoided any problems, I was wrong. I had a problem loading flight plans now that I never had before, and the ONLY thing I changed was to update the FSUPIC 2 days ago. In checking the DLL.xml file it seems that FSUIPC has changed the order of, and also split some entries, so without the original I have no idea how to rebuild it correctly. Of course if I had the slightest inkling that updateing FSUIPC would have affected the dll.xml I would have backed it up......man I hate programs that do this!! If you are having other issues after installing the new FSUIPC, I would suggest you check this file out, and if you havent updated yet, BACK IT UP Jay
May 12, 201313 yr I don't think there is any priority to the order of entries in the dll.xml. Can you post an example of a "split entry"? regards, Joe The best gift you can give your children is your time.
May 12, 201313 yr I don't think there is any priority to the order of entries in the dll.xml. Can you post an example of a "split entry"? regards, Joe I've read somewhere if you use fsinn, fscopilot must be the last entry in the DLL file. AJ Pongress
May 12, 201313 yr I'd post it to Pete's site. Gregg Seipp "A good landing is when you can walk away from the airplane. A great landing is when you can reuse it." i9 64GB RAM, GTX-5090
May 12, 201313 yr Commercial Member I don't think there is any priority to the order of entries in the dll.xml. Actually, there are. Some modules don't work well if they're loaded after others depending on what the others are. One example is FSINN (VATSIM Client), there are some modules from other programs that, when loaded afterwards will cause hangs when FSINN is started. This is no necessarily an FSINN issue, it's just that the programmers didn't coordinate (few if any ever do). The fix is to place FSINN at the very bottom of the DLL.XML. Several years ago, there was a problem with the Wilco PIC, and don't quote me but I think it was related to the Level-D. When you suffer such problems, you have to manually change the order of the modules to find out what works and what doesn't. That's all I remember, a Google search may turn up some interesting and helpful info. Dave Mine did too, but it was only missing one or more carriage returns (I don't know how many because I cheated by going down each line and adding one usign Notepad instead of Notepad 2007). It also placed entries below FSINN, so I moved that back down to the bottom of the list. Everything was fine afterwards. Dave Dave Hodges System Specs: I9-13900KF, NVIDIA 4070TI, Quest 3, Multiple Displays, Lots of TERRIFIC friends, 3 cats, and a wonderfully stubborn wife.
May 13, 201313 yr Author I've read somewhere if you use fsinn, fscopilot must be the last entry in the DLL file. Actually at least for me, it has to be the first entry, and that was the problem, FSUIPC moved it to the last entry and then I couldnt preload a flight plan, all fixed now, but stuff like this still aggravates me Jay
May 13, 201313 yr As far as FSX is concerned the order of entries in the dll.xml file is immaterial. If a user installs add-ons that require entries to be in a particular order the must handle that and not expect FSX or even FSUIPC to do it. FSUIPC can't be expect to cope with every requirement of every possible combination of add-ons. Gerry Howard
May 13, 201313 yr Thankfully, there's a utility that allows us to re-arrange the entries and re-create the DLL.xml. MSFS
May 13, 201313 yr As far as FSX is concerned the order of entries in the dll.xml file is immaterial. If a user installs add-ons that require entries to be in a particular order the must handle that and not expect FSX or even FSUIPC to do it. FSUIPC can't be expect to cope with every requirement of every possible combination of add-ons. Just a question since I've never even been aware of this file...why would an app rearrange it? Gregg Seipp "A good landing is when you can walk away from the airplane. A great landing is when you can reuse it." i9 64GB RAM, GTX-5090
May 13, 201313 yr Greg, When you install a plane with a module, the info about the module is placed in the dll.xml file. Some installs put the info at the top, middle, or bottom. This causes errors for fsx. Ex. Lvd 767 dll error at opening screen. MSFS
May 13, 201313 yr Commercial Member As far as FSX is concerned the order of entries in the dll.xml file is immaterial. Now, now Gerry. Asked and answered, with refernces. Please, stop saying this. It may be immaterial for you, or even for a lot of different modules, but often people take what they read here as Gospel and they don't bother to continue to reserach or even read an entire thread. This causes them grief if they have one of those difficult problems as it may steer them away from the right path to solve it. Now, please, respectfully, qualify your posts "it doesn't matter on my system" would be okay. Again, respectfully, I can tell you from personnel experience with fixings a LOT of FSX realted issues via remote desktop, that the order certainly CAN make a difference. Dave Just a question since I've never even been aware of this file...why would an app rearrange it? Gregg, The easy answer... Certain FSX and third party modules need to be run for them to interface with FSX correctly. So when you install some addons that need special files to run, FSX will know how and where to load them. Thus such third party addons write to the DLL.XML file, but how they do it sometimes isn't very nice and the formatting gets whigged. More info here: http://support.precisionmanuals.com/KB/a92/dllxml-information-and-troubleshooting.aspx Hope this has helped. Oh, sometimes, depending on what addons you have, the order may be important for a few of the addons. It's not always important, but when you have a loading issue after installing an addon that nothing else seems to resolve (including verifying a correctly formatted DLL.XML file), then the best bet is the order of the modules in the XML.DLL file is the culprit. Dave Dave Hodges System Specs: I9-13900KF, NVIDIA 4070TI, Quest 3, Multiple Displays, Lots of TERRIFIC friends, 3 cats, and a wonderfully stubborn wife.
May 13, 201313 yr Please, stop saying this. you should have read what I actually posted. The order doesn't matter to FSX but, as I said, some add-ons "require entries to be in a particular order." My point being that neither FSX nor FSUIPC can be expected to second guess what add-ons require. Gerry Howard
May 13, 201313 yr Yup - you are correct, Gerry: Let's not make a big deal of this, suffice to say that I've been guilty of this "mis-reading" business before, as it's often the case that someone is quite wrapped up in their own way of using words that they're written and posted before the brain kicks in, and one realises that the other party's words can be read with a different meaning, such as happened here. "FSX doesn't care". There is no mechanism for FSX to re-arrange the entry ordering system in the exe or the dll.xml files. It matters only to the individual addon at the time it's installed. At a later date, after a new app has been installed - that app may well have a conniption when it suddenly finds it's entry has been moved by some other entry! The nerve! So - let's not try to make unnecessary waves, over our toys... please! :Peace: i7 [email protected] | 32GB RAM | EVGA RTX 3080Ti | Maximus Hero VII | 512GB 860 Pro | 512GB 850 Pro | 256GB 840 Pro | 2TB 860 QVO | 1TB 870 EVO | Seagate 3TB Cloud | EVGA 1000 GQ | Win10 Pro | EK Custom water cooling.
May 15, 201313 yr Any software that depends on a certain order or position in the DLL.xml is one poorly written piece of code IMO. Paul
Create an account or sign in to comment