Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hello,

 

I have just purchased a registered version of FSUIPC to tackle the W8 joystick cutout problems.

Unfortunately, I currently (after spending € 42 for the use of FSUIPC and WideFS software) am unable to use the programme for this.

Although FSUIPC recognises the joystick (I checked in the fsuipc.ini file) when trying to assign buttons, keys as well as axis, there is no response at all.

Does anybody know what may cause this problem?

 

Some specs:

 

Windows 8.1, FSX acceleration, most recent FSUIPC and WideFS versions. I have a Saitek X52 as well as a Microsoft Sidewinder at my disposal. Both joysticks do not respond. They both respond in their Windows control panel pages to all inputs. The normal FSX functionality when enabeled, is also normal.

 

At the moment I am very distrought and disappointed...

 

greetings

 

Hajo

Posted

I have just purchased a registered version of FSUIPC to tackle the W8 joystick cutout problems.

 

I don't know of any reason why FSUIPC should be able to fix Win8 problems. It is certainly nothing promised by FSUIPC at all. I have heard some folks say this, but there's really no reason why, as FSUIPC's methods are perfectly standard, like FSX.

 

Perhaps you should have asked here before purchase? I would have said that I see no reason why it should be any different to fSX.

 

Although FSUIPC recognises the joystick (I checked in the fsuipc.ini file) when trying to assign buttons, keys as well as axis, there is no response at all.

Does anybody know what may cause this problem?

 

Some specs:

 

Windows 8.1, FSX acceleration, most recent FSUIPC and WideFS versions. I have a Saitek X52 as well as a Microsoft Sidewinder at my disposal. Both joysticks do not respond. They both respond in their Windows control panel pages to all inputs. The normal FSX functionality when enabeled, is also normal.

 

 

FSUIPC uses exactly the same methods to read joysticks as FS, so I cannot imagine what can be wrong. Perhaps first of all you could find the FSUIPC4 log file and paste its contents in a reply here? I cannot really help with no information, and that would be a start.

 

Pete

Posted

OK, here's the log file:

 

********* FSUIPC4, Version 4.934 by Pete Dowson *********
Reading options from "A:\Flightsim\Flight Simulator X\Modules\FSUIPC4.ini"
Running inside FSX on Windows 7
Module base=5FCF0000
User Name="Hajo Winia"
User Addr="**********@*********.com"
FSUIPC4 Key is provided
WideFS7 Key is provided
       16 System time = 24/05/2014 22:17:58
       16 FLT UNC path = "\\SLEEPY4\Users\Hajo\Documents\Flight Simulator X Files\"
       47 Trying to connect to SimConnect Acc/SP2 Oct07 ...
       78 FS UNC path = "\\SLEEPY4\Flightsim\Flight Simulator X\"
      438 LogOptions=00000000 00000001
      438 SIM1 Frictions access gained
      453 Wind smoothing fix is fully installed
      453 G3D.DLL fix attempt installed ok
      453 SimConnect_Open succeeded: waiting to check version okay
      453 Trying to use SimConnect Acc/SP2 Oct07
     2406 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
     2406 Initialising SimConnect data requests now
     2406 FSUIPC Menu entry added
     2453 \\SLEEPY4\Users\Hajo\Documents\Flight Simulator X Files\Default.FLT
     2453 \\SLEEPY4\Flightsim\Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR
    51813 Weather Mode now = Theme
    51813 \\SLEEPY4\Users\Hajo\AppData\Roaming\Microsoft\FSX\Previous flight.FLT
    55094 System time = 24/05/2014 22:18:53, Simulator time = 22:18:17 (20:18Z)
    55109 Aircraft="Cessna Skyhawk 172SP Paint2"
   126250 Starting everything now ...
   126266 AES Link established
   127563 Advanced Weather Interface Enabled
   355734 Sim stopped: average frame rate for last 163 secs = 29.8 fps
   404141 Sim stopped: average frame rate for last 36 secs = 28.8 fps
   447688 Sim stopped: average frame rate for last 32 secs = 29.6 fps
   609828 Sim stopped: average frame rate for last 134 secs = 29.9 fps
   627875 Aircraft="Cessna Skyhawk 172SP Paint2"
   630594 Aircraft="Cessna Skyhawk 172SP Paint2"
   648906 Aircraft="Cessna Skyhawk 172SP Paint2"
   840578 Sim stopped: average frame rate for last 21 secs = 29.7 fps
  1064422 Sim stopped: average frame rate for last 212 secs = 29.9 fps
  1107016 Sim stopped: average frame rate for last 34 secs = 29.9 fps
  1674453 Sim stopped: average frame rate for last 544 secs = 29.9 fps
  1735547 System time = 24/05/2014 22:46:54, Simulator time = 13:51:32 (11:51Z)
  1735547 *** FSUIPC log file being closed
Average frame rate for running time of 1214 secs = 29.8 fps
G3D fix: Passes 15964, Null pointers 0, Bad pointers 0, Separate instances 0
Memory managed: 598 Allocs, 598 Freed
********* FSUIPC Log file closed ***********

 

....and the Install Logfile:

 

Installer for FSUIPC4.DLL version 4.934

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="A:\Flightsim\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:
       A:\Flightsim\Flight Simulator X\Modules\FSUIPC4.DLL
... Version 4.934 found.
FSX Modules folder already exists.
Okay -- installed FSUIPC4 into "A:\Flightsim\Flight Simulator X\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\Hajo\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\Default.migrated\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Hajo\AppData\Roaming"
Found FSX.CFG in "C:\Users\Hajo\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 ...
... There is a SimConnect.XML, checking for "local" section.
... "local" section already exists, file not modified.
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Renske\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 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
===========================================================

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

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

 

I know that FSUIPC is not, and has never claimed to be "the final answer" to the W8 problems, but I don't know what else is, other than reverting back to W7, which at the moment isn't possible for me.

 

Hope this information helps.

 

greetings

 

Hajo

Posted

OK, here's the log file:

 

All that looks fine. Curiouser and curiouser.

 

We need more logging to see what might be happening. Also please show me the JoyNames section of the FSUIPC4.INI file.

 

For the extra logging, please edit the FSUIPC4.INI file, adding these lines to the [General] section:

 

Debug=Please

LogExtras=xA0000A

LogButtonsKeys=Yes

LogAxes=Yes

 

Run FS, waggle some joystick axes, press some buttons, then close FS. Show me the FSUIPC4.LOG file. If too big send to petedowson@btconnect.com.

 

Pete

Posted

Those extra logging parameters helped in the sense that it gave a lot of info:

 

********* FSUIPC4, Version 4.934 by Pete Dowson *********
Reading options from "A:\Flightsim\Flight Simulator X\Modules\FSUIPC4.ini"
Running inside FSX on Windows 7
Module base=5C450000
User Name="Hajo Winia"
User Addr="*****@******.com"
FSUIPC4 Key is provided
WideFS7 Key is provided
       62 System time = 25/05/2014 16:09:36
       78 FLT UNC path = "\\SLEEPY4\Users\Hajo\Documents\Flight Simulator X Files\"
      109 Trying to connect to SimConnect Acc/SP2 Oct07 ...
      140 FS UNC path = "\\SLEEPY4\Flightsim\Flight Simulator X\"
      484 #### Initialising Dlrectinput Axis Scanning ...
      500    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_045E&PID_001B\Calibration\0"
      500    Found correct joystick Id 0
      500    ... and a "GUID" value
      500    DirectInput8Create failed, return = 80040154
      500    joyGetDevCaps for device 1 returned error 165 [000000A5]
      500    joyGetDevCaps for device 2 returned error 165 [000000A5]
      500    joyGetDevCaps for device 3 returned error 165 [000000A5]
      500    joyGetDevCaps for device 4 returned error 165 [000000A5]
      500    joyGetDevCaps for device 5 returned error 165 [000000A5]
      500    joyGetDevCaps for device 6 returned error 165 [000000A5]
      500    joyGetDevCaps for device 7 returned error 165 [000000A5]
      500    joyGetDevCaps for device 8 returned error 165 [000000A5]
      500    joyGetDevCaps for device 9 returned error 165 [000000A5]
      500    joyGetDevCaps for device 10 returned error 165 [000000A5]
      500    joyGetDevCaps for device 11 returned error 165 [000000A5]
      500    joyGetDevCaps for device 12 returned error 165 [000000A5]
      500    joyGetDevCaps for device 13 returned error 165 [000000A5]
      500    joyGetDevCaps for device 14 returned error 165 [000000A5]
      500    joyGetDevCaps for device 15 returned error 165 [000000A5]
      500 #### Completed Dlrectinput Axis Scanning
      547 LogOptions=50000000 0A0000B1
      547 SIM1 Frictions access gained
      562 Wind smoothing fix is fully installed
      562 G3D.DLL fix attempt installed ok
      562 SimConnect_Open succeeded: waiting to check version okay
      562 Trying to use SimConnect Acc/SP2 Oct07
     3531 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
     3531 Initialising SimConnect data requests now
     3531 FSUIPC Menu entry added
     3640 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
     3640 \\SLEEPY4\Users\Hajo\Documents\Flight Simulator X Files\Default.FLT
     3640 \\SLEEPY4\Flightsim\Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR
     3812 Memory in use: 513Mb, Avail=3583Mb
    62906 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
    63453 System time = 25/05/2014 16:10:39, Simulator time = 16:09:39 (14:09Z)
    63468 Aircraft="Cessna Skyhawk 172SP Paint2"
    63484 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
    64187 Memory in use: 551Mb, Avail=3544Mb
   114093 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
   121687 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
   122609 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
   124390 Starting everything now ...
   124437 AES Link established
   124437 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
   124468 Memory in use: 1018Mb, Avail=3078Mb
   125578 Advanced Weather Interface Enabled
   127672 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
   129890 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
   131562 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
   132703 *** Entered Buttons option page ***
   132703 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #0 is zero!
   132703 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #1 is zero!
   132703 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #2 is zero!
   132703 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #3 is zero!
   132703 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #4 is zero!
   132703 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #5 is zero!
   132703 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #6 is zero!
   132703 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #7 is zero!
   132703 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #8 is zero!
   132703 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #9 is zero!
   132703 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #10 is zero!
   132703 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #11 is zero!
   132703 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #12 is zero!
   132703 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #13 is zero!
   132703 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #14 is zero!
   132703 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #15 is zero!
   140562 *** Exiting Buttons option page ***
   140578 *** Entered Keys option page ***
   145000 *** Exiting Keys option page ***
   153703 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
   156625 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
   165187 System time = 25/05/2014 16:12:21, Simulator time = 16:09:49 (14:09Z)
   165187 *** FSUIPC log file being closed
Average frame rate for running time of 17 secs = 25.4 fps
G3D fix: Passes 13646, Null pointers 0, Bad pointers 0, Separate instances 0
Memory managed: 8 Allocs, 8 Freed
********* FSUIPC Log file closed ***********

 

The joynames section of the FSUIPC.ini file:

 

[JoyNames]
AutoAssignLetters=No
0=As: 4 knop: 8 Joystick met kapschakelaar
0.GUID={301F9B70-B056-11E2-8001-444553540000}

 

As mentioned before, I also have an X52 available, which gives the same errors.

 

greets

 

Hajo

Posted

Those extra logging parameters helped in the sense that it gave a lot of info:

 

Yes, and it identified the problem:

 

 

      500    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_045E&PID_001B\Calibration\0"

      500    Found correct joystick Id 0

      500    ... and a "GUID" value

      500    DirectInput8Create failed, return = 80040154

 

The only times this has occurred before is with folks who have a non-standard DirectX module installed which FSX is picking up. It is evidently one which doesn't support the full range of Windows DirectX functions, hence the failure.

 

Searching on the error number 80040154 I found these threads:

 

http://forum.simflight.com/topic/76735-still-problems-to-assign-axis-in-fsx-for-fsuipc/?hl=%2Bdirectinput8create+%2Bfailed%2C+%2Breturn+%2B80040154#entry467162

http://forum.simflight.com/topic/76577-axis-assignment-not-responding/?hl=%2Bdirectinput8create+%2Bfailed%2C+%2Breturn+%2B80040154#entry466435

 

I'm confident one of these answers will answer your problem too.

 

Pete

Posted

Pete,

 

thanks for all your help, removing the culprit DLL file seems to have cured the problem.

Now all thats left is a lot of tinkering!

 

thanks a million

 

Hajo

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.