Hi Guys,

 

More a question than a problem but since installing UT2 into P3D Ver 3.2 when i start the sim i get the following message pop up

 

There was a problem starting D:\ Prepar3D

 

The specified module could not be found

 

clicking ok starts the sim with no apparent issues but when I close down again the message comes back.

 

Any idea's please??

I have the same exact issue after installing UT2 with P3D v3.2. Do you use Flight Estonia Migration Tool and did you figure out a fix?

Have you checked to see that the UT2Services.exe is started by having the entry added to your exe.xml file.

 

Also be sure to use the correct exe.xml which is in your C:\Users\<username>\AppData\Roaming\Lockheed Martin\Prepar3D v3

 

Here's mine as an example.

 

   <Launch.Addon>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Name>UT2</Name>
    <Path>your UT2 install location\\Flight One Software\Ultimate Traffic 2\UT2Services.exe</Path>
    <NewConsole>True</NewConsole>
  </Launch.Addon>

 

 Be sure to have the correct path set to where your UT2Services.exe is located.
 

Tried your suggestion but it seems not related to exe.xml. Completely removed UT2 entry from exe.xml to test but error still occurred without UT2 services loading.

 

Have you checked to see that the UT2Services.exe is started by having the entry added to your exe.xml file.

 

Also be sure to use the correct exe.xml which is in your C:\Users\<username>\AppData\Roaming\Lockheed Martin\Prepar3D v3

 

Here's mine as an example.

 

   <Launch.Addon>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Name>UT2</Name>
    <Path>your UT2 install location\\Flight One Software\Ultimate Traffic 2\UT2Services.exe</Path>
    <NewConsole>True</NewConsole>
  </Launch.Addon>

 

 Be sure to have the correct path set to where your UT2Services.exe is located.
 

Did you ever resolve this?

No still have this issue, I just ignore error for now.

Resolved issue, figured it out from creating dumpfile of rundll in windows which led me to figuring out the dll file that it was looking for. Removed following from dll.xml and issue is fixed.

 

  <Launch.Addon>

    <Name>Migration Tool Plugin</Name>

    <Path>MigTool.dll</Path>

    <DllStartName>module_init</DllStartName>

    <DllStopName>module_deinit</DllStopName>

  </Launch.Addon>