Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hi I have recently installed FSUIPC into FSX and the installer said it was successfully installed. But it is not in the add ons drop down box. Can someone help?

 

 

I'd need to see the Installer log -- which would be in your FSX\Modules folder. Also see if there is an FSUIPC4 log file. Both files are plain text, and you can paste them into a reply here. Use the <> button above the edit area.

 

 

Pete

Posted

Installer for FSUIPC4.DLL version 4.853

 
Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
Looking in registry for ESP install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\ESP
     Parameter"AppPath"
... NOT found! ...
Looking in registry for Prepar3D install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\Prepar3D
     Parameter"AppPath"
... NOT found! ...
===========================================================
 
INSTALLATION FOR FSX:
SetupPath="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X"
Checking version of FSX.EXE:
... Version 10.0.61637.0  (Need at least 10.0.60905.0)
Checking compatibility with installed SimConnect:
    Found SimConnect build 60905 (Original)
    Found SimConnect build 61242 (SP1 May07)
    Found SimConnect build 61259 (Acc/SP2 Oct07)
Checking if there's already a version of FSUIPC4 installed in:
       C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL
... No previous valid version found.
FSX Modules folder already exists.
Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Zack\AppData\Roaming"
Now finding \Microsoft\FSX\FSX.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Zack\AppData\Roaming"
Found FSX.CFG in "C:\Users\Zack\AppData\Roaming\Microsoft\FSX\FSX.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
     (for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
"Modules\FSUIPC Documents" folder already exists.
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "List of FSX controls.pdf" okay
   Installed "GlobalSign Root.exe" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
FSUIPC4.DLL installed and signature checked out okay!
Deleted GlobalSign Root fix program ... no longer relevant
===========================================================
 
All installer tasks completed.
 
*************** End of Install Log ***************
 
 
 
 
That is the only one I have in there.
Posted

Installer for FSUIPC4.DLL version 4.853

 

4.853 is about two years old and well out of date. You need to download the currently supported version, 4.937. I cannot support old versions.

 

Pete

Posted

Installer for FSUIPC4.DLL version 4.937

 
Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
Looking in registry for ESP install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\ESP
     Parameter"AppPath"
... NOT found! ...
Looking in registry for Prepar3D install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\Prepar3D
     Parameter"AppPath"
... NOT found! ...
Looking in registry for Prepar3D v2 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\Prepar3D v2
     Parameter"AppPath"
... NOT found! ...
===========================================================
 
INSTALLATION FOR FSX:
SetupPath="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X"
Checking version of the FSX EXE:
... Version 10.0.61637.0  (Need at least 10.0.60905.0)
Checking compatibility with installed SimConnect:
    Found SimConnect build 60905 (Original)
    Found SimConnect build 61242 (SP1 May07)
    Found SimConnect build 61259 (Acc/SP2 Oct07)
Checking if there's already a version of FSUIPC4 installed in:
       C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL
... Version 4.937 found.
FSX Modules folder already exists.
Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Zack\AppData\Roaming"
Now finding \Microsoft\FSX\FSX.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Zack\AppData\Roaming"
Found FSX.CFG in "C:\Users\Zack\AppData\Roaming\Microsoft\FSX\FSX.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
     (for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
"Modules\FSUIPC Documents" folder already exists.
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "List of FSX and P3D controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
===========================================================
 
All installer tasks completed.
 
*************** End of Install Log ***************
 
 
 
 
This is what it said when i installed the newer one.
Posted

This is what it said when i installed the newer one.

 

Okay.  And when you ran FSX, was there no prompt to ask you to approve the running of FSUIPC4? Is there no FSUIPC4.LOG file in the FSX Modules folder?

 

If these things didn't occur, then the problem is that SimConnect isn't loading FSUIPC4 in the first place. This is usually because of a corrupted DLL.XML file. Maybe this was caused by some previous installer.

 

You can find this file in this folder:

 

C:\Users\Zack\AppData\Roaming\Microsoft\FSX

 

It is also a text file. If you'd like to paste it here I'll see if I can spot the problem. An alternative, as a test, is to rename it (rather than delete it) then try running the FSUIPC4 installer again. It will create a fresh copy with only FSUIPC4 being loaded.

 

Pete

Posted

No there were no prompts. Also, there is no FSUIPC4.LOG file in my modules folder. 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>Objectflow_CBB7.dll</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_CBB7\Scenery\Objectflow_CBB7.dll</Path>
</Launch.Addon>
  <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>SquawkBox Transponder</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files (x86)\SquawkBox\sbtrans10.dll</Path>
</Launch.Addon>
  <Launch.Addon>
<Name>SquawkBox AI Control</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files (x86)\SquawkBox\sbaicontrol10.dll</Path>
</Launch.Addon>
  <Launch.Addon>
<Name>SquawkBox Internal Version</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files (x86)\SquawkBox\sbmod10.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>FeelThere ERJX Helper</Name>
<Disabled>False</Disabled>
<Path>FeelThere\Erj\E145XH.dll</Path>
</Launch.Addon>
  <Launch.Addon>
<Name>PMDG HUD interface</Name>
<Disabled>False</Disabled>
<Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>
  <Launch.Addon>
<Name>PMDG Options</Name>
<Disabled>False</Disabled>
<Path>PMDG\DLLs\PMDGOptions.dll</Path>
</Launch.Addon>
  <Launch.Addon>
<Name>PMDG Events</Name>
<Disabled>False</Disabled>
<Path>PMDG\DLLs\PMDGEvents.dll</Path>
</Launch.Addon>
  <Launch.Addon>
<Name>PMDG Sounds</Name>
<Disabled>False</Disabled>
<Path>PMDG\DLLs\PMDGSounds.dll</Path>
</Launch.Addon>
  <Launch.Addon>
<Name>Mindstar Hypergauge</Name>
<Disabled>False</Disabled>
<ManualLoad>Fasle</ManualLoad>
<Path>Modules\HyperGauge.dll</Path>
</Launch.Addon>
  <Launch.Addon>
<Name>Mindstar Hypergauge</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Modules\HyperGauge.dll</Path>
</Launch.Addon>
  <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>
  <Launch.Addon>
<Name>CMeteoXml</Name>
<Disabled>False</Disabled>
<Path>.\CMeteoXml.dll</Path>
</Launch.Addon>
  <Launch.Addon>
<Name>FeelThere EJetX Helper</Name>
<Disabled>False</Disabled>
<Path>FeelThere\E170\EJetH.dll</Path>
</Launch.Addon>
  <Launch.Addon>
    <Name>Flight Recorder</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
 <Name>Mindstar Hypergauge</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>Modules/HyperGauge.dll</Path>
</Launch.Addon>
  <Launch.Addon>
        <Name>FSUIPC 4</Name>
        <Disabled>False</Disabled>
        <Path>Modules\FSUIPC4.dll</Path>
    </Launch.Addon>
</SimBase.Document>
 
 
 
 
I will also try to rename the DLL.XML file.
Thanks for the continued help.
Posted

No there were no prompts. Also, there is no FSUIPC4.LOG file in my modules folder. Here is the DLL.XML file.

 

Wow! I've never seen so many add-in DLLs being requested. I wonder if the SimConnect DLL loader is choking? Do all those others load and work correctly?What's that, 22 DLLs with only the three default SDK ones disabled?

 

There is one error, in the first of the three entries (?!) for Mindstar Hypergauge, in this line:

 

<ManualLoad>Fasle</ManualLoad>

 

"Fasle" should be "False" of course. Whether this would stop the subsequent DLLs loading I don't know -- but if not, maybe trying to load Mindstar Hypergauge three times causes the entries following to fail -- i.e. FSUIPC4  and maybe others?

 

The entries following the erroneous line are trying to load these:

 

Mindstar Hypergauge (the second time)

PMDG Interface
RAASPRO
CMeteoXml
FeelThere EJetX Helper
Flight Recorder
Mindstar Hypergauge (the third time)
FSUIPC 4
 
I will also try to rename the DLL.XML file.

 

 

Try correcting it first. Delete the entire first two entries for Mindstar Hypergauge. i.e. this part:

 

<Launch.Addon>
<Name>Mindstar Hypergauge</Name>
<Disabled>False</Disabled>
<ManualLoad>Fasle</ManualLoad>
<Path>Modules\HyperGauge.dll</Path>
</Launch.Addon>
  <Launch.Addon>
<Name>Mindstar Hypergauge</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Modules\HyperGauge.dll</Path>
</Launch.Addon>
  
Pete
Posted

I renamed it and it worked. Thanks for the help.

 

Yes, but now you won't have all those other DLLs running, which presumably you need? Best to correct the original file as I suggested above.

 

Pete

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.