Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hi Peter,

I saw that there is a similar topic in this forum but I don't want to interrupt the solution finding there.

My problem is the same but I have Acceleration Pack installed.

These are my files:

FSUIPC4.log

********* FSUIPC4, Version 4.60a by Pete Dowson *********

Reading options from "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"

Trying to connect to SimConnect Acc/SP2 Oct07 ...

User Name="robert heiss"

User Addr="robert@minzeband.com"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

Running inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=15

1233 System time = 24/11/2010 20:27:58

1248 FLT UNC path = "\\RAMPAGEII\Users\Robert\Documents\Flight Simulator X-Dateien\"

1248 FS UNC path = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"

2075 LogOptions=00000000 00000001

2075 SimConnect_Open succeeded: waiting to check version okay

5351 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

5351 Initialising SimConnect data requests now

5351 FSUIPC Menu entry added

5382 \\RAMPAGEII\Users\Robert\Documents\Flight Simulator X-Dateien\Chicago.FLT

5382 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR

404199 System time = 24/11/2010 20:34:41

404199 *** FSUIPC log file being closed

Memory managed: 2 Allocs, 2 Freed

FSUIPC4Install.log

Installer for FSUIPC4.DLL version 4.634

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\SOFTWARE\Microsoft\Microsoft ESP\1.0

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\SOFTWARE\LockheedMartin\Prepar3D

Parameter"AppPath"

... NOT found! ...

===========================================================

INSTALLATION FOR FSX:

AppPath="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

... Version 4.634 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\Robert\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\Petra\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Public\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Robert\AppData\Roaming"

Found FSX.CFG in "C:\Users\Robert\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.

... FSUIPC4 section of DLL.XML written okay

Now checking for a SimConnect.XML file ...

... There is a SimConnect.XML, checking for "local" section.

... "local" section already exists, file not modified.

"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 "Example LUA plugins.zip" okay

FSUIPC4.DLL installed and signature checked out okay!

Deleted GlobalSign Root fix program ... no longer relevant

===========================================================

All installer tasks completed okay!

Registration check for FSUIPC4 was successful! (result code 00)

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

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>FSUIPC 4</Name>

<Disabled>False</Disabled>

<Path>Modules\FSUIPC4.dll</Path>

</Launch.Addon>

</SimBase.Document>

Could you please help me finding a solution?

Cheers, Myata

Posted

I saw that there is a similar topic in this forum but I don't want to interrupt the solution finding there.

My problem is the same but I have Acceleration Pack installed.

Sorry, your problem is the same as what? you don't mention a problem except "no modules dropdown", and the files you provided show everything is running fine! There never is a "modules dropdown" in FSX -- that was FS9 and before.

Could you please help me finding a solution?

A solution to what? I see no problem in the files and you don't described one.

Regards

Pete

Posted (edited)

Sorry Peter, looks like I am far too deep in this so i miised some informations. First of all I thought there is a module dropmenu in FSX aswell. If there isn't. I am fine.

How can i then use the tuning functions for my comtrolls of FSUIPC? I could not find any informations about this in the manuals or maybe I just read the wrong ones.

Thanks for your patience.

BTW: this was the topic I was talking about ..

Edited by Myata
Posted

... I thought there is a module dropmenu in FSX aswell. If there isn't. I am fine.

How can i then use the tuning functions for my comtrolls of FSUIPC?

You use the FSUIPC entry in the AddOns menu, exactly as described in the documentation.

BTW: this was the topic I was talking about ..

It's a bit late now referring to a specific thread. Best always, in any case, to describe your own problem in your own thread. Obviously your problem was different, maybe reading FSUIPC3 documentation (relevant to FS9 and before) instead of the correct FSUIPC4 user documentation installed for you into your Modules\FSUIPC Documents folder?

Regards

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.