<calm down>Folks, no idea what went wrong but all PMDG aircraft (747-8, MD11 and J41) stopped working today after a failed attempt to install the LDS767. Anyway, all PMDG aircraft complain they cannot find the pmdgoptions.dll. Funny enough because the file sits in :\FSX\PMDG\dlls. Should it go anywhere else? I first tried to repair my installations. No cure. Then I deinstalled all PMDG and re-installed the 747 and still it asks for the options.dll?!? When I confirm this error FSX crashes and I get a funny error message like 'this requires smartassembly'. Hey, something goes terribly wrong. Any idea what. Needless to say that I rebooted the PC after installation.help me, plsPhil

Phil, your problem may be the FSX file called dll.xml, which points FSX to where these addon modules are and how to treat them. There is an article in the knowledge base on repairing this file, or you can open a trouble ticket at the pmdg support portal in their web site. Also, you might see the error if you open the file and look for a misplaced or extra slash character.

Phil, your problem may be the FSX file called dll.xml, which points FSX to where these addon modules are and how to treat them. There is an article in the knowledge base on repairing this file, or you can open a trouble ticket at the pmdg support portal in their web site. Also, you might see the error if you open the file and look for a misplaced or extra slash character.

Thanks, Dan. Will check that. Just hope I can avoid a full FSX reinstall...Phil

Yeah, it's definitely dll.xml related...http://support.precisionmanuals.com/KB/a80...llxml-file.aspx

Yeah, it's definitely dll.xml related...http://support.precisionmanuals.com/KB/a80...llxml-file.aspx

Thanks, Tabs, for reactivating my copies. I am just re-installing my PMDG a/c from day to day from scratch and it works that way, too (honestly, did not know where to look for the dll.xml). Just flying a short hop in the 747-8 from LIML to EDDF... Hey, France is just loosing against Mexico ;-), so autopilot is set..

Hi gang, just wanted to bump this post up in case anyone else is struggling with the smartassembly issue.Not sure what caused it in my case, but the most likely culprit seems to have been a certain Embraer add-on. (no disrespect to the devs, it's a nice plane) Reinstalling .NET had no impact, I finally found this post and discovered two erroneous characters in my DLL.XML file. Removed them and the problem was solved!</annoyance>(Oh man, did I just make an XML joke there? shoot me right now...)So yeah, I would strongly advise people to check this out if they are having similar trouble.

I have had the same problem and it is frustrating when things go pear-shaped. All I can suggest to others before this happens that when you do a periodic backup-up of files (you do do that of course :( ) is that you include everything in the folder where the fsx.cfg file lives, depending on the OS you are using. I use Synctoy and save to an external HD.

Mark,This wouldn't be the first time that particular company has caused errors in the dll.xml - their 737 did it as well...