August 28, 201411 yr I just started experiencing not able to open FSUIPC with my PMDG aircraft. Also, the RAAS is not there as well in the Add On Drop down menu. Any suggestions? Lyle Jayma
September 1, 201411 yr What antivirus are you using MSE ? (Microsoft Security essentials?) Jude BradleyBeech Baron: Uh, Tower, verify you want me to taxi in front of the 747?ATC: Yeah, it's OK. He's not hungry. X-Plane 12 and MSFS2020 🙂 System specs: Windows 11 Pro 64-bit, Ubuntu Linux 20.04 i7-13700KF Gigabyte Z790 RTX-4060-Ti , 32GB RAM 1X 2TB M2 for X-Plane 12, 1x256GB SSD for OS. 1TB drive MSFS2020
September 2, 201411 yr Restart FSX. http://fs2crew.com/banners/Banner_FS2Crew_MJC_Supporter.png Wayne HART
September 2, 201411 yr Commercial Member A reinstall is order at this point..thanks That should really be your last option... Kyle Rodgers
September 2, 201411 yr Hi Lyle, same thing happened to me a couple of months ago. I remeber the issue was related to the dll.xml file.This file is located at the same folder where your fsx.cfg is. Edit the file and search for any inconsstency. It's prety easy: every addon that has to be executed/launched inside FSX will have a section like this one.... <Launch.Addon> <Name>RAASPRO</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>.\RAASPRO\RAASPRO.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> I found a line </Launch.Addon> that didn't have to be there that had been left there by error. I deleted it, saved the file and off we go, problem solved!!! Hope it helps. Good luck!! Jaime Homar.
September 2, 201411 yr Author Hi Lyle, same thing happened to me a couple of months ago. I remeber the issue was related to the dll.xml file.This file is located at the same folder where your fsx.cfg is. Edit the file and search for any inconsstency. It's prety easy: every addon that has to be executed/launched inside FSX will have a section like this one.... <Launch.Addon> <Name>RAASPRO</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>.\RAASPRO\RAASPRO.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> I found a line </Launch.Addon> that didn't have to be there that had been left there by error. I deleted it, saved the file and off we go, problem solved!!! Hope it helps. Good luck!! Jaime Homar. I will take a look at this..Appreciate it that Lyle Jayma
September 18, 201411 yr Author That should really be your last option... And I had to use this option..unfortunately.. thank for the help Lyle Jayma
September 18, 201411 yr Commercial Member And I had to use this option..unfortunately.. thank for the help So you legitimately exhausted all other options, to include the one Jaime posted, along with going through official support channels like support.precisionmanuals.com? Kyle Rodgers
September 18, 201411 yr Author Kyle Legitimately..I sifted slowly through my .dll/xml files 2x and then I reached out the guys at PMDG and also Peter@FSUIPC and it the ideas from both were great but nothing worked. Lesson learned..backup..backup..backup. I should know better. Lyle Jayma
September 19, 201411 yr Commercial Member Legitimately..I sifted slowly through my .dll/xml files 2x and then I reached out the guys at PMDG and also Peter@FSUIPC and it the ideas from both were great but nothing worked.Lesson learned..backup..backup..backup. I should know better. Ouch. Thanks for trying to help pin it down by trying the other options, though. And yeah - backups are crucial. Images can be great if you have the space, too. Kyle Rodgers
Create an account or sign in to comment