FSUIPC inexplicably causes a problem

[davebelsey]

I have been using FSUIPC for some considerable time without problems, but out of the blue I have a problem with it on my Vista 64-bit machine.

When I start FSX, I now get this message:

.

As I was using an old version, I installed the latest, but get the same error message.

If I answer 'no', FSX runs ok but without FSUIPC working. If I answer 'yes' FSX loads and runs ok, but on every subsequent restart FSX fails to start due to a Fatal Error. I have tried suggestions that I have found on this website, all to no avail.

I have also tried repairing Acceleration without success. I then tried uninstalling Acceleration and repairing FSX before reinstalling Acceleration, but that didn't work either.

Do you have any idea what else I can try?

Dave.

[Pete Dowson]

As I was using an old version, I installed the latest, but get the same error message.

By "latest" what version number do you mean, please? I always need version numbers.

If I answer 'no', FSX runs ok but without FSUIPC working. If I answer 'yes' FSX loads and runs ok, but on every subsequent restart FSX fails to start due to a Fatal Error. I have tried suggestions that I have found on this website, all to no avail.

Are there any logs? If FSUIPC produces a log (FSUIPC4.LOG) in the Modules folder I need to see it. Also please show the Insstall log.

Have you checked the error report in Windows logs? That will tell you the failing module, the error code and the offset.

Regards

Pete

[davebelsey]

Hi Pete,

Thanks for the prompt response :smile:

The version I have installed is 4.8.3.1

The FSUIPC4.LOG is as follows:

********* FSUIPC4, Version 4.831 by Pete Dowson *********

User Name=""

User Addr=""

FSUIPC4 not user registered

WIDEFS7 not user registered, or expired

Running inside FSX on Windows Vista

Module base=61000000

78 System time = 26/05/2012 10:31:07

78 FLT path = "C:\Users\Dave\Documents\Flight Simulator X Files\"

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

140 FS path = "F:\Flight Simulator X\"

The install log is as follows:

Installer for FSUIPC4.DLL version 4.827

Looking in registry for SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 install path:

HKEY_LOCAL_MACHINE\(null)

Parameter"SetupPath"

... >>> OK! FOUND FSX! <<< ...

Looking in registry for SOFTWARE\Microsoft\Microsoft ESP\1.0 install path:

HKEY_LOCAL_MACHINE\(null)

Parameter"SetupPath"

Not there, so looking in:

HKEY_CURRENT_USER\ESP

Parameter"AppPath"

... NOT found! ...

Looking in registry for SOFTWARE\LockheedMartin\Prepar3D install path:

HKEY_LOCAL_MACHINE\(null)

Parameter"SetupPath"

Not there, so looking in:

HKEY_CURRENT_USER\Prepar3D

Parameter"AppPath"

... NOT found! ...

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

INSTALLATION FOR FSX:

SetupPath="F:\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:

F:\Flight Simulator X\Modules\FSUIPC4.DLL

... Version 4.751a found.

FSX Modules folder already exists.

Okay -- installed FSUIPC4 into "F:\Flight Simulator X\Modules\FSUIPC4.DLL"

Looking for the current user's Application Data path:

... found as "C:\Users\Dave\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\Dave\AppData\Roaming"

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

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\UpdatusUser\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 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

FSUIPC4.DLL installed and signature checked out okay!

Deleted GlobalSign Root fix program ... no longer relevant

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

All installer tasks completed.

Registration for FSUIPC4 was cancelled or failed! (result code 40)

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

I hope this helps,

Dave.

[davebelsey]

Also,

Event Viewer has multiple instances of DINPUT.dll as well as API.dll, DSOUND.dll and NTDLL.dll as faulting modules.

Dave.

[Pete Dowson]

Event Viewer has multiple instances of DINPUT.dll as well as API.dll, DSOUND.dll and NTDLL.dll as faulting modules.

All for the FSX process? Wow.

The log shows only that FSUIPC4 is loading and starting okay but that it never gets further than asking for a SimConnect connection -- FSX is crashing before SimConnect returns.

The mention of DINPUT is interesting -- I'm wondering if the crash is occurring in one of the hardware drivers, from where FSUIPC is doing its scan of devices so it can identify them. Mind you, it's done that before it gets to trying a SimConnect connection. Still, it may show something. Try adding these lines to the [General] section of the FSUIPC4.INI file, and show me the resulting log:

Debug=Please

LogExtras=x200000

The other thing you could try, in case the crash is ccurring on a regular button scan, is to stop button scanning by setting:

PollInterval=0

in the [buttons] section.

Pete

[davebelsey]

Pete,,

I added the lines to the ini file,and this was the log:

********* FSUIPC4, Version 4.831 by Pete Dowson *********

User Name=""

User Addr=""

FSUIPC4 not user registered

WIDEFS7 not user registered, or expired

Running inside FSX on Windows Vista

Module base=61000000

47 System time = 26/05/2012 15:48:52

47 FLT path = "C:\Users\Dave\Documents\Flight Simulator X Files\"

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

110 FS path = "F:\Flight Simulator X\"

437 LogOptions=00000000 02000011

437 Wind smoothing fix is fully installed

437 G3D.DLL fix attempt installed ok

437 SimConnect_Open succeeded: waiting to check version okay

437 Trying to use SimConnect Acc/SP2 Oct07

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

4431 Initialising SimConnect data requests now

4431 FSUIPC Menu entry added

4462 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y

4462 c:\users\dave\documents\flight simulator x files\Lucy at Manston.FLT

4462 F:\Flight Simulator X\SimObjects\Airplanes\RealAir SF-260 Left Seat\SF-260.AIR

11108 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N

11435 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y

131541 System time = 26/05/2012 15:51:03, Simulator time = 15:48:56 (14:48Z)

165346 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N

FSX attempted to go straight to my default flight instead of the Create Flight screen, but still had a Fatal Error.

I did not have a [buttons] section in my ini file, so I added one with PollInterval=0, but still got a fatal error.

Dave

>

[Pete Dowson]

I added the lines to the ini file,and this was the log

Well, the logging additions made no difference in any case. Obviously it isn't related to FSUIPC's DirectInput scanning as it didn't get that far.

However, FSUIPC got a helluva lot further than the last log you showed. Simconnect did connect okay, and everything was going well except that FSUIPC never saw you exit from the selection menu and commence normal flight mode.

FSX attempted to go straight to my default flight instead of the Create Flight screen

You must have changed something to make that occur, because there is nothing in the world FSUIPC could do to change that. It's an option in your FSX.CFG file.

It is beginning to sound very much like you have some sort of hardware problem, probably bad memory.

... but still had a Fatal Error.

And what did the Windows log show this time?

Pete

[davebelsey]

Pete,

Event Viewer had :

Faulting application fsx.exe, version 10.0.61637.0, time stamp 0x46fadb14, faulting module dinput.dll, version 6.0.6000.16386, time stamp 0x4549bcd6, exception code 0xc0000005, fault offset 0x00013e3a, process id 0x13cc, application start time 0x01cd3b4fb0114f40.

Dave.

[Pete Dowson]

Faulting application fsx.exe, version 10.0.61637.0, time stamp 0x46fadb14, faulting module dinput.dll, version 6.0.6000.16386, time stamp 0x4549bcd6, exception code 0xc0000005, fault offset 0x00013e3a, process id 0x13cc, application start time 0x01cd3b4fb0114f40.

Okay. I am now of the opinon that the attribution to FSUIPC is actually wrong, that it is mere coincidence, possibly due to differences in memory arrangements and timing of events when it is loaded. I see that your FSUIPC installation is not actually registered, so FSUIPC is not in fact scanning buttons or joysticks at all, and is making no calls at all to DirectInput.

I'm not sure how you'd go about finding the true cause, but if DirectInput seems to be the most prevalent crash area I would certainly check all your USB connections and devices.

Regards

Pete

[davebelsey]

Pete,

Thank you so much for pointing me in the right direction :smile:

It appears that the cause was the adaptor for the Saitek Cyborg wireless joystick. Removing that and uninstalling the software has got FSX working properly again.

In appreciation of your help, I will be buying the registered version of FSUIPC.

Dave.

[Pete Dowson]

It appears that the cause was the adaptor for the Saitek Cyborg wireless joystick. Removing that and uninstalling the software has got FSX working properly again.

In appreciation of your help, I will be buying the registered version of FSUIPC.

Seems that device or its driver is not fully Win7 compatible! Thanks for the feedback. This might also help others!

Regards

Pete

[Ian P]

Saitek have just - within the last couple of weeks - released new drivers for the CyborgX USB stick that I use, which solved problems I was having, so it might be worth checking for a new version.

Ian P.

[Pete Dowson]

Saitek have just - within the last couple of weeks - released new drivers for the CyborgX USB stick that I use, which solved problems I was having, so it might be worth checking for a new version.

Thanks Ian. I'll copy this to the other similar thread, just in case.

Pete

[davebelsey]

Thanks for the input, Ian.

The stick I have is quite old now (Cyborg Evo wireless) and has seen better days, so I may well replace it.

Pete,

This was for Vista 64, not Win7.

Dave.

[Pete Dowson]

This was for Vista 64, not Win7.

Ah ... Vista64 had even more problems with drivers than Win7! Many avoided it just for that reason!

There are solutions for most Win7 driver problems now, but I doubt if many of the developers are backtracking to Vista64.

Pete