Jump to content
The simFlight Network Forums

Recommended Posts

Good day Pete,

FSUIPC was  running very well, then I got the above mentioned problem.

I could solve it by installing the latest version of FSUIPC.

That was 4 weeks ago. Now the same problem. But there is no newer version ( 4.974 ).

So I deleted the installed FSUIPC an installed the same again.

When starting FSX, there in now no warning by Windows 10.

But FSUIPC is not working,  FSX crashes when using the FSUIPC.

There is no logfile in the FSUIPC-folder,

but here is the DLL:

<?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>Object Placement Tool</Name>
        <Disabled>True</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
        <Name>Traffic Toolbox</Name>
        <Disabled>True</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
        <Name>Visual Effects Tool</Name>
        <Disabled>True</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
        <Name>VistaMare Core</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>VistaMare\ViMaCoreX.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
        <Name>AirbusNewHUD</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>Addon Modules\AirbusNewHUD.dll</Path>
        <DllStartName>module_init</DllStartName>
        <DllStopName>module_deinit</DllStopName>
    </Launch.Addon>
  <Launch.Addon>
        <Name>IvAp</Name>
        <Disabled>False</Disabled>
        <Path>C:\Program Files (x86)\IVAO\IvAp v2\ivap_fsx_bootstrap.dll</Path>
        <Commandline/>
    </Launch.Addon>
  <Launch.Addon>
        <Name>SODE Animation Module</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>C:\Program Files (x86)\12bPilot\SODE\SimObjectAnimationModule.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
        <Name>Navigraph Simlink</Name>
        <Disabled>False</Disabled>
        <Path>Gauges\NavigraphSimlink.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
    <Name>FSUIPC 4</Name>
    <Disabled>False</Disabled>
    <Path>Modules\FSUIPC4.dll</Path>
  </Launch.Addon>
</SimBase.Document>

 

Link to comment
Share on other sites

15 hours ago, simflieger said:

But FSUIPC is not working,  FSX crashes when using the FSUIPC.

There is no logfile in the FSUIPC-folder,

The failure of FSUIPC to start is probably because Windows has marked it not to be loaded. This must be due to a previous FSX crash either blamed on FSUIPC or when FSUIPC was the last DLL running. The latter can happen simply because something else caused FSX to crash and FSUIPC has many threads, for Lua plug-ins, WideFS and the like.

You say it was okay for 4 weeks and then suddenly did this. That can't happen without something changing -- so what changed? That's what you need to identify.

Seeing the DLL.XML file is not much use to me, except for showing several other add-ons which could also be causing the original crash.

What I need to see is the crash data. Open Event Viewer, find the Application Logs, and scroll down the Event List til you find a Red icon labelled Error, and identifying FSX as the culprit. Then copy the text data in the lower panel and paste that into a message here.

15 hours ago, simflieger said:

So I deleted the installed FSUIPC an installed the same again.

There's absolutely no point in deleting it, but using the FSUIPC4 Installer to re-install usually fixes the Registry entry which tells Windows not to allow FSUIPC to load.

One other thing to do is to remove / rename your DLL.XML file, then re-run the FSUIPC4 Installer. that will create a new DLL.XML file which only loads FSUUIPC. If that works okay then there's a problem with one of the other programs being loaded. 

Pete

 

Link to comment
Share on other sites

Hallo Pete

I found this:

      fsx.exe
      10.0.61637.0
      46fadb14
      ivap_fsx.dll
      2.0.2.2773
      50d58c4a
      c0000005
      0006baf0
      18b8
      01d3e6330e4c7df6
      C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
      C:\Program Files (x86)\IVAO\IvAp v2\ivap_fsx.dll
      8027083c-c60f-400a-9056-3ee0e08faf5d
       
       
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.