Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

PDGMoptions DLL v Wilco Products

Featured Replies

Having recently reinvented my interest in FSX, I encountered the dreaded dll.xml bug having installed a Wilco product BEFORE my PMDG 747 and MD11. Needless to say, that ended up in disaster on many levels. I have recovered from that debacle with a complete wipe and reinstall of FSX and have NOT installed any Wilco product yet.My question is the order of installation. I will be installing PMDG 747 and MD11 FIRST, then my Wilco product(s). Now, should I buy PMDG's latest fine looking commuter turboprop (those are "turbo" are they not? LOL) and at that, after my Wilco stuff, am I going to run into that dll installation problem as with the MD11 and 747, or will I be safe and install the newest PMDG product without that hassle? (or must I uninstall anything from Wilco first?)Randy Jura, KPDX

The JS41 and all newer products will not be using the pmdgoptions.dll but I can't predict what the Wilco product might do.. simply because I've avoided their stuff.

Dan Downs KCRP

Having recently reinvented my interest in FSX, I encountered the dreaded dll.xml bug having installed a Wilco product BEFORE my PMDG 747 and MD11. Needless to say, that ended up in disaster on many levels. I have recovered from that debacle with a complete wipe and reinstall of FSX and have NOT installed any Wilco product yet.My question is the order of installation. I will be installing PMDG 747 and MD11 FIRST, then my Wilco product(s). Now, should I buy PMDG's latest fine looking commuter turboprop (those are "turbo" are they not? LOL) and at that, after my Wilco stuff, am I going to run into that dll installation problem as with the MD11 and 747, or will I be safe and install the newest PMDG product without that hassle? (or must I uninstall anything from Wilco first?)Randy Jura, KPDX
Randy, I have the Wilco/Feel There Citation X (which is ok, BTW, but not great). That was installed before any of the PMDG stuff I have, and have no problems. YMMV.

PMDGAirbus.gif

Doug Orvis

PP-ASEL-IA (USA), Based at KHEF

 

Picture courtesy of Kyle Rodgers

I have used the Wilco 737 PIC for some time with the J41 and had no trouble. I don't have any other PMDG products though, so I'm not sure about that. I do know I will be installing the PMDG 747X, and I sure hope I will not run into the problem you described...

Benjamin van Soldt

Windows 10 64bit - i5-8600k @ 4.7GHz - ASRock Fatality K6 Z370 - EVGA GTX1070 SC 8GB VRAM - 16GB Corsair Vengeance LPX @ 3200MHz - Samsung 960 Evo SSD M.2 NVMe 500GB - 2x Samsung 860 Evo SSD 1TB (P3Dv4/5 drive) - Seagate Barracuda 2TB 7200RPM - Seasonic FocusPlus Gold 750W - Noctua DH-15S - Fractal Design Focus G (White) Case

I have used the Wilco 737 PIC for some time with the J41 and had no trouble. I don't have any other PMDG products though, so I'm not sure about that. I do know I will be installing the PMDG 747X, and I sure hope I will not run into the problem you described...
Ummmm ... that's exactly the situation that really screwed me up badly. I'd save your dll.xml file first (the same location as fsx.cfg file). When I installed my PDMG 747 after the Wilco 737, it screwed up the dll.xml file to the point I had to do a complete reinstall of FSX! Be careful! Install the 747 FIRST, then the Wilco. Apparently, the only other PMDG product that can also be affected is the MD11, make sure you get that in FIRST, before Wilco 737. If you've already put in the Wilco 737 before the PMDG 747? Well, maybe try to uninstall the Wilco 737, then check the dll.xml file to make sure any entry referring to the Wilco is gone, but if it is not, you're out of luck. I've tried to edit the dll.xml, but failed. Apparently the Wilco folk back then did some bad coding that cannot be undone. Anyone else knowing different on how to edit out the bad stuff, please enlighten me, it was a pain to re-install my entire FSX because of Wilco's stuff!Randy Jura, KPDX

Great -.-If I save the original dll.xml, before I install the PMDG 747X, and then simply install the PMDG 747X, can't I simply edit the dll.xml file that was the original, by adding the required entries as used by the PMDG 747X? Because, what is it that happens to the dll.xml file that is so bad? What happens when you do Wilco first and than PMDG 747X?Of course I could uninstall the Wilco 737 PIC first and reinstall it later, I can simply make a backup of the relevant aircraft.cfg files and add them in later after I reinstall it, so that's not the problem, but I'd like to understand what is the nature of the problem caused.EDIT: Never mind. It's all described here: http://ops.precisionmanuals.com/wiki/How_t...SX_DLL.XML_FileNow I have to decide what to do. I have checked the dll.xml file and everything seems to be okay. All tags are proparly closed, and installation of the MAddog 2008, which also edits the dll.xml file, was succesful and is in there without causing any problems. Can anybody advice me, in light of succesful edit of the dll.xml file despite the fact that I installed the Wilco 737X PIC, if I should install the PMDG 747X or do as is said in the link I posted, namely, make a completely new dll.xml file from scratch? I'd like to know what to do once my copy of the 747X arrives. Thanks for anybody trying to help!

Benjamin van Soldt

Windows 10 64bit - i5-8600k @ 4.7GHz - ASRock Fatality K6 Z370 - EVGA GTX1070 SC 8GB VRAM - 16GB Corsair Vengeance LPX @ 3200MHz - Samsung 960 Evo SSD M.2 NVMe 500GB - 2x Samsung 860 Evo SSD 1TB (P3Dv4/5 drive) - Seagate Barracuda 2TB 7200RPM - Seasonic FocusPlus Gold 750W - Noctua DH-15S - Fractal Design Focus G (White) Case

Install the 747 FIRST, then the Wilco. Apparently, the only other PMDG product that can also be affected is the MD11, make sure you get that in FIRST, before Wilco 737. If you've already put in the Wilco 737 before the PMDG 747? Well, maybe try to uninstall the Wilco 737, then check the dll.xml file to make sure any entry referring to the Wilco is gone
Gorgeous, Randy, that reminded me something from my favourite Monty Python's 'the Meanig of life':Now, before I begin the lesson, will those of you who are playing in the match this afternoon move your clothes down onto the lower peg immediately after lunch, before you write your letter home, if you're not getting your hair cut, unless you've got a younger brother who is going out this weekend as the guest of another boy, in which case, collect his note before lunch, put it in your letter after you've had your hair cut, and make sure he moves your clothes down onto the lower peg for you... :(

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.