Jump to content
The simFlight Network Forums

Problems with Axis Assignment


Recommended Posts

Hi,

 

i have a Problem. I have bought a serialkey of FSUIPC today, because i had problems with my Saitek Cyborg Evo with WIndows 8.1. Some users in a Forum recommend me to buy FSUIPC. 

But now i can't assign the axis in FSUIPC.

 

It looks like this in the Picture.

 

Please help!!!

 

post-700-0-94126100-1390329578.png

Link to comment
Share on other sites

But now i can't assign the axis in FSUIPC.

 

It looks like this in the Picture.

 

It will look exactly like that until you move an axis which it can recognise. If it doesn't see any axes then you have some driver which is preventing it, or your device doesn't actually have any real DirectInput axes.

 

Does FS recognise any axes? FSUIPC is only using the same DirectInput facilities as FS.

 

Pete

Link to comment
Share on other sites

The Problem is, FUSIPC detected the Joystick, when i use it via FSX... But under Windows 8.1 the Joystick will disconnect after a while, so some users recommend to use FSUIPC.

 

If FSUIPC detects the joystic it will show the axes.

 

Sorry, I may be misunderstanding you. Perhaps you can give more information?

 

Pete

Link to comment
Share on other sites

The Problem ist...

 

When I have calabrate the Joystick via FSX, then it shows in Joystick Calabration Menu the Moving of the axis. But I have configure the Joystick via FSUIPC; because I use Windows 8.1 and  under Windows 8.1 the Joystick will disconnect in FSX after a while.

 

I use the Saitek Cyborg Evo.

 

Flo

Link to comment
Share on other sites

When I have calabrate the Joystick via FSX, then it shows in Joystick Calabration Menu the Moving of the axis. But I have configure the Joystick via FSUIPC; because I use Windows 8.1 and  under Windows 8.1 the Joystick will disconnect in FSX after a while.

 

FSUIPC uses the same DirectInput system to read the joysticks as FSX, so I would have thought the results would be the same.

 

Does FSUIPC list your joystick, with its allocated number (0-15) and its "GUID", in the FSUIPC4.INI file? It'll be in a section like this:

 

[JoyNames]

AutoAssignLetters=No

0=Saitek Pro Flight Throttle Quadrant

0.GUID={B0ABDEC0-6DA5-11E0-8001-444553540000}

 

Pete

Link to comment
Share on other sites

here is the Entry in my FSUIPC:

 

[JoyNames]

AutoAssignLetters=No

0=Saitek Cyborg USB Stick

0.GUID={FFD83740-5D49-11DF-8005-444553540000}

 

Okay. That's good. Now in the FSUIPC Axes tab, when you move the levers sufficiently (from one extreme to the other), they should be recognised and you can assign them.

 

Regards

Pete

Link to comment
Share on other sites

I just tried it and it does not work :(

 

Hmm. Sounds like there's a Saitek driver blocking it. Are its buttons recognised in the Buttons & Switches tab?

 

Try this: add these two lines to the [General] saection of the FSUIPC4.INI file:

 

Debug=Please

LogExtras=x200008

 

Then run FSX and try again in the Axes tab.

 

Then close FSX, and paste both your FSUIPC4.INI and FSUIPC4.LOG files back into a message here.

 

Regards

Pete

Link to comment
Share on other sites

********* FSUIPC4, Version 4.928 by Pete Dowson *********
Running inside FSX on Windows 8
Module base=598B0000
User Name="Florian Herrmann"
User Addr="florian-herrmann@t-online.de"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
      281 System time = 22/01/2014 17:57:44
      281 FLT path = "C:\Users\Florian Herrmann\Documents\Flight Simulator X-Dateien\"
      328 Trying to connect to SimConnect Acc/SP2 Oct07 ...
      344 FS path = "C:\FSX\"
      625 #### Initialising Dlrectinput Axis Scanning ...
      625    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0464\Calibration\0"
      625    Found correct joystick Id 0
      625    ... and a "GUID" value
      625    DirectInput8Create failed, return = 80040154
      625    joyGetDevCaps for device 1 returned error 165 [000000A5]
      625    joyGetDevCaps for device 2 returned error 165 [000000A5]
      625    joyGetDevCaps for device 3 returned error 165 [000000A5]
      625    joyGetDevCaps for device 4 returned error 165 [000000A5]
      625    joyGetDevCaps for device 5 returned error 165 [000000A5]
      625    joyGetDevCaps for device 6 returned error 165 [000000A5]
      625    joyGetDevCaps for device 7 returned error 165 [000000A5]
      625    joyGetDevCaps for device 8 returned error 165 [000000A5]
      625    joyGetDevCaps for device 9 returned error 165 [000000A5]
      625    joyGetDevCaps for device 10 returned error 165 [000000A5]
      625    joyGetDevCaps for device 11 returned error 165 [000000A5]
      625    joyGetDevCaps for device 12 returned error 165 [000000A5]
      625    joyGetDevCaps for device 13 returned error 165 [000000A5]
      625    joyGetDevCaps for device 14 returned error 165 [000000A5]
      625    joyGetDevCaps for device 15 returned error 165 [000000A5]
      625 #### Completed Dlrectinput Axis Scanning
      641 LogOptions=00000000 02000091
      641 SIM1 Frictions access gained
      641 Wind smoothing fix is fully installed
      641 G3D.DLL fix attempt installed ok
      641 SimConnect_Open succeeded: waiting to check version okay
      641 Trying to use SimConnect Acc/SP2 Oct07
      656 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)
      656 Initialising SimConnect data requests now
      656 FSUIPC Menu entry added
      672 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
      672 C:\FSX\FLIGHTS\OTHER\FLTSIM.FLT
      672 C:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR
     2187 Memory in use: 787Mb, Avail=3309Mb
    37469 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
    37906 Aircraft="Aircreation582SL red"
    37906 System time = 22/01/2014 17:58:22, Simulator time = 17:57:41 (01:57Z)
    40844 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
    42375 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #0 is zero!

Link to comment
Share on other sites

[General]
UpdatedByVersion=4928
History=NLXKDKXC95UA4CO5GA3O2
AxesWrongRange=No
TCASid=Flight
TCASrange=40
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
InitDelay=0
GetNearestAirports=Yes
OOMcheck=Yes
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
LuaRerunDelay=66
Console=No
InitDelayDevicesToo=No
NewInterceptTextMenu=No
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
PollGFTQ6=Yes
BlankDisplays=No
FixControlAccel=No
FixMachSpeedBug=No
DeleteVehiclesForAES=Yes
AutoScanDevices=Yes
VisibilityOptions=No
OneCloudLayer=No
CloudTurbulence=No
CloudIcing=No
GenerateCirrus=No
SuppressCloudTurbulence=No
MaxIce=-4
MinIce=-4
UpperWindGusts=No
SuppressWindTurbulence=No
SuppressWindVariance=No
WindTurbulence=No
TurbulenceRate=1.0,5.0
TurbulenceDivisor=20,20,40,40
SuppressAllGusts=No
MaxSurfaceWind=0
WindLimitLevel=200
WindDiscardLevel=400
WindAjustAltitude=No
WindAjustAltitudeBy=2000
SmoothBySimTime=No
WindSmoothing=No
WindSmoothness=2
WindSmoothAirborneOnly=Yes
PressureSmoothness=0
TemperatureSmoothness=0
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
OwnWeatherChanges=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=No
Debug=Please
LogExtras=x200008
FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0
SimConnectUsed=10.0.61259.0

[JoyNames]
AutoAssignLetters=No
0=Saitek Cyborg USB Stick
0.GUID={FFD83740-5D49-11DF-8005-444553540000}

[WideServer]
WideFSenabled=Yes

[sounds]
Path=C:\FSX\Sound\
Device1=Primärer Soundtreiber
Device2=Lautsprecher (Realtek High Definition Audio)
Device3=Realtek Digital Output (Realtek High Definition Audio)

[buttons]
ButtonRepeat=20,10

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No

[GPSout]
GPSoutEnabled=No

[GPSout2]
GPSoutEnabled=No

[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60

[Profile.FlorianH]
1=Aircreation582SL red
 

Link to comment
Share on other sites

      625 #### Initialising Dlrectinput Axis Scanning ...

      625    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0464\Calibration\0"

      625    Found correct joystick Id 0

      625    ... and a "GUID" value

      625    DirectInput8Create failed, return = 80040154

 

Aha. There's the problem:

 

DirectInput8Create failed, return = 80040154

 

There's another thread featuring a Saitek device with the exact same problem. See here:

 

http://forum.simflight.com/topic/76089-directinput8create-failed-return-80040154/

 

FSUIPC is reporting an error occurring in Windows when it tries to access the device as a DirecInput device.

 

I am now suspecting an incompatibility between Win8.1 and certain Saitek devices. You could try uninstalling the device (frm the Windows Control Panel-System-Device Manager list), ensuring you also remove its driver if possible, then re-booting the PC and letting it be found again.

 

Pete

Link to comment
Share on other sites

SLtill net working :(

 

I'm strongly suspecting a Win8.1 bug here. FSUIPC cannot actually manufacture such an error -- "class not registered". FSUIPC doesn't need to register classes itself, that part of the systems job, classifying devices and the like. It seems some incompatibility between Win8.1 and Saitek.

 

Pete

Link to comment
Share on other sites

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.