must have screwed up

[jmuzz]

I have had to try to re-install fsuipc several times in order to run asn. When I did this, the add-on screen on fsx showed that the version number of fsuipc was older than the one I installed. Now, after cleaning out the modules file and re-doing the fsuipc installation again, there is no fsuipc listed in the add-on screen in fsx.  I think I must have deleted something I shouldn't.

[Pete Dowson]

I have had to try to re-install fsuipc several times in order to run asn.

 

You don't actually need to install or reinstall FSUIPC at all to run ASN. ASN does not use FSUIPC. What's all this about "several times"? All the installer does is update documentation and the FSUIPC4.DLL itself. nothing else is ever changed by the Installer. Re-running it does nothing at all.

 

When I did this, the add-on screen on fsx showed that the version number of fsuipc was older than the one I installed.

 

The installer cannot overwrite a later version, so you must have deleted something for some strange reason and then run an older installer.

 

Now, after cleaning out the modules file and re-doing the fsuipc installation again, there is no fsuipc listed in the add-on screen in fsx.  I think I must have deleted something I shouldn't.

 

Two things:

 

1. You NEVER EVER have to delete ANYTHING at all when updating or installing FSUIPC. There is no point. It is futile.

2. Apart from the presence of FSUIPC itself there is nothing in the Modules folder which will in any way affect whether FSUIPC appears in the add-ons menu. That is simply dictated by whether FSUIPC is running or not. If it is not running, there will be no menu.

 

Check whether you even have a DLL in the modules folder!

 

Pete

[jmuzz]

Pete,  let me be a little more specific. I have had trouble getting ASN to run. Their people told me (among other things) that if I had FSUIPC that I needed to download version 4.927b. When I downloaded and ran this version, the version number in the add-on tab of FSX showed a version about 2 years old. Thinking that I had somehow messed up the download or execute file, I tried it twice again, with the same result. I then cleared out all the FSUIPC entries in the modules file and downloaded and executed once again. This time, although there is a DLL file, there is no FSUIPC listed in the 'add-on' tab of FSX.

[jmuzz]

I also have no log file. Here is the dll.xml:

 

<?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>Level-D Simulations</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>Modules\LVLD.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>as_connect</Name>
    <Disabled>False</Disabled>
    <Path>as_srv\as_btstrp.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
        <Name>FSUIPC 4</Name>
        <Disabled>False</Disabled>
        <Path>Modules\FSUIPC4_Loader.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
        <Name>FSCopilot</Name>
        <Disabled>False</Disabled>
        <Path>Modules\FSCopilot.dll</Path>
    </Launch.Addon>
</SimBase.Document>
 

[Pete Dowson]

Pete,  let me be a little more specific. I have had trouble getting ASN to run. Their people told me (among other things) that if I had FSUIPC that I needed to download version 4.927b. When I downloaded and ran this version, the version number in the add-on tab of FSX showed a version about 2 years old.

 

Where did you go to get this bad download? there's no whaere I know of. the best source s are here, in the Download Links subforum, or over in the Schiratti.com page. Both links point ot the correct downloads. I don't know anywhere you can get 2 year old versions, but if you remember where you went please let me know!

 

Thinking that I had somehow messed up the download or execute file, I tried it twice again, with the same result. I then cleared out all the FSUIPC entries in the modules file and downloaded and executed once again.

 

As I said, there is never any need to delete the contents of the Modules folder -- FSUIPC's installer simply replaces anything unless it is LATER in date.

 

This time, although there is a DLL file, there is no FSUIPC listed in the 'add-on' tab of FSX.

 

So either your DLL.XML is corrupt, or Simconnect is hosed.

 

I also have no log file. Here is the dll.xml:

 

That looks fine. Can you show me the FSUIPC4 Install log? That might be very relevant.

 

Pete

[jmuzz]

Here is the install log:   (I downloaded from your download site).

 

Installer for FSUIPC4.DLL version 4.927a

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="D:\FSX\"
Checking version of the FSX EXE:
... Version 10.0.61472.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:
       D:\FSX\Modules\FSUIPC4.DLL
... No previous valid version found.
FSX Modules folder already exists.
Okay -- installed FSUIPC4 into "D:\FSX\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\Owner\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\Guest\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Jerry\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Owner\AppData\Roaming"
Found FSX.CFG in "C:\Users\Owner\AppData\Roaming\Microsoft\FSX\FSX.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4_Loader section already exists but will be replaced.
     (with FSUIPC4_Loader entry)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\TEMP\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\TEMP.Owner-PC\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\TEMP.Owner-PC.000\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\TEMP.Owner-PC.001\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\TEMP.Owner-PC.002\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\UpdatusUser\AppData\Roaming"
 ... No FSX.CFG there
"Modules\FSUIPC Documents" folder created okay!
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 "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
===========================================================

All installer tasks completed.
Registration for FSUIPC4 was successful! (result code 00)

*************** End of Install Log ***************
 

[Pete Dowson]

Here is the install log:   (I downloaded from your download site).

 

I don't have any "download site" apart from the Download Links subforum injust above.

 

It looks like you've installed the FSUIPC4 Loader DLL. Why did you do that? As mentioned in the Instructions it is just a possible way round certain very unusual clashes which cause FSX to crash on loading. It has no bearing at all on cases where FSUIPC is not even being loaded.

 

Please remove that and run the Installer again.

 

If it stil doesn't load we need to find out why. Try to get a SimConnect log -- see instructions in the thread in the FAQ subforum. Also check the [Trusted] section of your FSX.CFG file and delete any FSUIPC4 or FSUIPC4_Loader entries -- you may have denied Trust at some point, and this is remembered in the CFG file.

 

Pete

[jmuzz]

I installed 4,972a and b after deleting the loader file. This time FSUIPC appears in the add-on section of FSX, however, as before when I look at the version information  that appears in the FSUIPC box (after pressing the add-on button), the version is 4.823 and the date is 12 Apr. 2012.  I have no idea how the loader.dll file got in the modules folder.

[Pete Dowson]

I installed 4,972a and b after deleting the loader file. This time FSUIPC appears in the add-on section of FSX, however, as before when I look at the version information  that appears in the FSUIPC box (after pressing the add-on button), the version is 4.823 and the date is 12 Apr. 2012.

 

I don't know what sort of mess your system is in, but there is no way any recent Installer will be able to put an 20 month old version into your FSX folders. It sounds either as if you have more than one FSX installation and you aremixing the two up, or you are using the wrong installer altogether. I suggest you do a search of your system for old copies of the FSUIPC4 installer and delete them , for starters. Then see about sorting out the FSX folders.

 

I note you've not bothered to show the Install log.

 

I have no idea how the loader.dll file got in the modules folder.

 

The only way it can possibly get there is if you, or someone else using your PC, put it there from the Installer ZIP file. There are three or four files there, the Installer, the installation instruction document, often a "changes" document, and the Loader DLL. You probably blindly unzip and copy everything without reading the instructions.

 

Pete