Jump to content
The simFlight Network Forums
chrishayes001

Help please to use FSUIPC$

Recommended Posts

Hello everyone


 


I bought FSUIPC4 yesterday through SimMarket. I have attempted to run FSUIPC but get these messages:


 


FXSUIPC4.DLL version 4.949p:


Installed in FSX okay/


Please see the “FSUIPC4 User Guide file. In the FSX-SE\Modules folder.


 


Problem! Cannot edit the FSX-SE DLL.XML file to activate FSUIPC


Please assure you run FSE-SE at least once before installing FSUIPC


 


MY path is C:>Program Files (x86)>Steam>Steamapps>comomon>FSX. Am using FSX STEAM, Rex 4 Texture Direct and Rex Soft Clouds. I have also recreated appache in >Steam.


 


Can any one kindly help me chrishayes


 


Share this post


Link to post
Share on other sites

This is a support request, moved from User Contributions subforum. Please always post support questions here, not in the specialised subforums which are for the purpose implied in their titles.

 

Can any one kindly help me chrishayes

 

You have a Regstry problem with your installed FS. To help resolve that I need to see the Install log. That's why one is made. That will contain all the details. You'll find it saved in the FSX modules folder, and also in the folder where you ran the Installer. It is a text file -- you can paste it in its entirety in a reply here.

 

Pete

Share this post


Link to post
Share on other sites

I attach a copy of the log for the above problem. Thank you.

 
Installer for FSUIPC4.DLL version 4.949p
 
Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
     SetupPath=D:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\
 
Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX
     Parameter"Install_Path"
... >>>  OK! FOUND FSX-SE!  <<< ...
     SetupPath=C:\Program Files (x86)\Steam\steamapps\common\FSX
 
Looking in registry for Prepar3D v1 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\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\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"AppPath"
... NOT found! ...
 
Looking in registry for Prepar3D v3 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"AppPath"
... NOT found! ...
===========================================================
 
INSTALLATION FOR FSX:
SetupPath="D:\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:
       D:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL
... Version 4.949p found.
FSX Modules folder already exists.
Okay -- installed FSUIPC4 into "D:\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\Chris Hayes\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\Chris Hayes\AppData\Roaming"
Found FSX.CFG in "C:\Users\Chris Hayes\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.
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
"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 "Offset Mapping for PMDG 777X.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
===========================================================
 
INSTALLATION FOR FSX-SE:
SetupPath="C:\Program Files (x86)\Steam\steamapps\common\FSX\"
Checking version of the FSX-SE EXE:
... Version 10.0.62615.0  (Need at least 10.0.62607.0)
Checking compatibility with installed SimConnect:
    Found SimConnect build 60905 (Original)
    Found SimConnect build 62615 (Steam)
    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)\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL
... Version 4.949p found.
FSX-SE Modules folder already exists.
Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Chris Hayes\AppData\Roaming"
Now finding \Microsoft\FSX-SE\FSX_SE.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Chris Hayes\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX_SE.CFG there
Cannot edit the DLL.XML file to activate FSUIPC.
"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 "Offset Mapping for PMDG 777X.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
===========================================================
 
All installer tasks completed.
Registration dialog 'not now' selected
*************** End of Install Log ***************

Share this post


Link to post
Share on other sites

You have a good FSX installation, and FSUIPC4 installed fine there, as shown:

 

INSTALLATION FOR FSX:
SetupPath="D:\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)
 
with the DLL.XML file being found and updated too:
 
Found FSX.CFG in "C:\Users\Chris Hayes\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
 
So, your FSX is fine.
 
However, your FSX-SE installation needs an FSX_SE.CFG file (if it was a standalone installation, with no FSX also installed, it would be named FSX.CFG, but that is not the case here).
 
FSUIPC4 has been installed okay into FSX-SE:
 
INSTALLATION FOR FSX-SE:
SetupPath="C:\Program Files (x86)\Steam\steamapps\common\FSX\"
Checking version of the FSX-SE EXE:
... Version 10.0.62615.0  (Need at least 10.0.62607.0)
 
But because you have no correct FSX_SE.CFG file, the FSUIPC4 Installer does not know where to place your DLL.XML. Without a DLL.XML file telling FSX-SE to load FSUIPC4.DLL, it cannot operate.
 
Maybe you have not yet run FSX-SE?  The CFG file is not made until you do.
 
Pete
 

Share this post


Link to post
Share on other sites

Than you very much for your reply. I have clearly made a mistake as I am actually using the Steam version of FSX. I presume I should be running from FSX-SE. Do I have to start again with FSX-SE and re-install everything anew?

Thanks 

Chris

Share this post


Link to post
Share on other sites

Than you very much for your reply. I have clearly made a mistake as I am actually using the Steam version of FSX. I presume I should be running from FSX-SE. Do I have to start again with FSX-SE and re-install everything anew?

 

No you shouldn't have to. did you already have FSX installed when you installed FSX-SE, because that's how it looks. If you didn't, and installed FSX AFTER FSX-SE, that might explain the mess.

 

If you have already run FSX-SE (you didn't actually answer that part), then you need to find out where the CFG file it is usding is stored. If it is FSX.CFG then that's actually wrong and an indication perhaps that FSX-SE didn't realise that FSX was installed when you installed it.

 

If you can find the CFG file it is using, and it is "FSX-CFG" then you could make a copy of it called "FSX_SE.CFG" to fool the FSUIPC4 installer to generating the correct DLL.XML. Look in

 

C:\Users\Chris Hayes\AppData\Roaming\Microsoft\FSX-SE

and

C:\Users\Chris Hayes\AppData\Roaming\DoveTail Games\FSX

or

C:\Users\Chris Hayes\AppData\Roaming\DoveTail Games\FSX-SE

 

I'm guessing a little here with those names.

 

 

However, even then, I'd be concerned also about other ramifications -- in particular where FSX-SE is storing its flights and plans. normally with a dual FSX + FSX-SE installation FSX-SE would use a folder in Your Documents called "Flight Simulator FSX-SE Files" (or similar), to keep them separate from FSX Files, but when it is installed as the only FSX it uses the same name as FSX -- Flight Simulator X Files. This difference will affect some of the things FSUIPC can do (as well as other applications, I'm sure).

 

The first thing to do is try to explain and understand what you did to have both FSX and FSX-SE installed if you only intended to have FSX-SE. Can you do that? Did you think you had uninstalled FSX?

 

Pete

Share this post


Link to post
Share on other sites

 

The first thing to do is try to explain and understand what you did to have both FSX and FSX-SE installed if you only intended to have FSX-SE. Can you do that? Did you think you had uninstalled FSX?

--------------------------------------------------------------------------------

Hello Pete

 

Thank you very much for your replies. I am most grateful..

 

I have realized I have made problems for myself.! I bought through STEAM but called it FSX when I couldn't work out what FSX:SE was. I did have an old boxed FSX version on another drive before that just to see the effect of Windows 10 - it was a bit flaky! But I never had the stand-alone FSX on the same drive.

 

Now I have realised another thing. When I got the steam version on this new computer I automatically went for the drive that had Program Files (x86) on it - like we used to years ago. But that drive is nearly full now so I am going to scrub everything and start again on the D: drive. Luckily I only have a couple of addons plus your FSUIPC4. I will try and not bother you any more - at least for a few weeks -  as I have to go to work in Manchester and can't play with this away from home.

 

I appreciate your help. 

 

Thanks again

 

Chris

Share this post


Link to post
Share on other sites

I have realized I have made problems for myself.! I bought through STEAM but called it FSX when I couldn't work out what FSX:SE was.

 

Not sure how you can call it FSX yourself. Is renaming an option in Steam?

 

I did have an old boxed FSX version on another drive before that just to see the effect of Windows 10 - it was a bit flaky! But I never had the stand-alone FSX on the same drive.

 

Things being on different drives is completely irrelevant. They are installed on your system. 

 

Now I have realised another thing. When I got the steam version on this new computer I automatically went for the drive that had Program Files (x86) on it - like we used to years ago.
 
It also isn't really a good idea these days, because the "Program Files" folders are protected from writing (since Vista days). FSUIPC's Installer makes the Modules folder (only) read/write, but the other folders can give other applications problems. This is why many folks have to run FSX or FSX-SE"as administrator" -- to give them enough provilege.
 
 But that drive is nearly full now so I am going to scrub everything and start again on the D: drive. 
 
Okay. Are you reformatting both drives and reinstalling Windows? If not, before your simply delete anything make sure you use Windows' Control Panel, "Programs and Features", and uninstall FSX, FSX-SE and Steam.  You may need to run a Registry Cleaner too, because the uninstall leaves traces in the Registry.
 
Pete
 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • 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.