I am using P3d v4.4, with my favorite PMDG 737 NGXu, FSDT GSX, and RAASPRO. Everything was running fine, when suddenly one morning, when I tried to launch P3D, the loading screen appeared and then it vanished after sometime. I checked task manager and noticed that P3D.exe was running in the background using resources such as RAM (700 MB) and 20% of CPU. and 10 % of my hard drive. I deleted the generated files, the problem was solved! When I re-introduced the addons, I saw that the error occured again. When I disabled RAAS in dll.xml, then P3D loaded up nicely. When I enabled RAAS in dll.xml the problem occured again. So I can conclude there is a problem with RAASPRO. 

Here is the dll.xml 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>PMDG_Interface</Name>
    <Disabled>False</Disabled>
    <Path>PMDG\DLLs\PMDG_Interface.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <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>
</SimBase.Document>

 

I recently uninstalled MS Office and Skype, and all MS apps, Microsoft Office 365, and I installed Microsoft Access Database Engine 2016(x64 bit) from Microsoft, manually. But still RAASPRO causes P3D to run as a background process! It is frustrating, and I cannot continue with my flights!

 

Well it is the RAASPRO (UNLOCKED) 64bit version!

 

DebadritoRaj Chakrabarti

Please try again now.

Due to the web site switch, the version checker for RAAS got thrown off.

As far I know it only affected FSX users though, not P3D users.

We've since rectified the issue on our end however.

So I'm not sure that is connected to your issue.

When was the last time RAAS was working for you?

You read the trouble shooting page?

http://www.support.fs2crew.com/help/manuals/#pageid=help_and_trouble_shooting

 

Let me know.

 

1 hour ago, byork said:

Please try again now.

Due to the web site switch, the version checker for RAAS got thrown off.

As far I know it only affected FSX users though, not P3D users.

We've since rectified the issue on our end however.

So I'm not sure that is connected to your issue.

When was the last time RAAS was working for you?

You read the trouble shooting page?

http://www.support.fs2crew.com/help/manuals/#pageid=help_and_trouble_shooting

 

Let me know.

 

What can I try now?

RAAS was working fine till 22nd July 2021, when suddenly P3D decided not to launch. After I deleted the generated files, and re-introduced the addons, I isolated the problem to be RAAS. When I disable RAAS in the dll.xml P3D launches successfully. When I enable it, it loads and then runs as a background process. 

 

And yes, I followed the instructions in FS2Crew Manuals, and uninstalled Office and other MS office (thinking that they would be conflicting with RAAS) and the also uninstalled the Access Database engine, and re-installed RAAS. RAAS installed the 2010 Spanish Access Database Engine. Then I tried to launch P3D, but it continued to run in the background, after loading! 

 

What should I do now?

I guess it was working fine till the day before yesterday. I do not remember actually, but this happened in this week, and it is annoying, I like RAAS, but cannot use it because it crashes P3D! What is the solution, and let me inform you, this has happened recently!

Okay, so I tried launching P3D now, and guess what, it launched! Thank you so much! And yeah, for me being a P3D user, it also affected me!

Thank you so much for the quick replies! Actually, the log file had stopped on attempting version check, and then P3D crashed!!! Now, it is working fine! 

Glad you got it sorted 🙂

It was due to the IPs switching switch for the new website.  

The version check failed during the website IP switch.

Cheers,