Hofer Posted January 21, 2014 Report Posted January 21, 2014 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!!!
Pete Dowson Posted January 21, 2014 Report Posted January 21, 2014 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
Hofer Posted January 21, 2014 Author Report Posted January 21, 2014 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.
Pete Dowson Posted January 21, 2014 Report Posted January 21, 2014 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
Hofer Posted January 22, 2014 Author Report Posted January 22, 2014 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
Pete Dowson Posted January 22, 2014 Report Posted January 22, 2014 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
Hofer Posted January 22, 2014 Author Report Posted January 22, 2014 Okay thanks. I will take a look and i'll Keep you inform...
Hofer Posted January 22, 2014 Author Report Posted January 22, 2014 Hi, here is the Entry in my FSUIPC: [JoyNames]AutoAssignLetters=No0=Saitek Cyborg USB Stick0.GUID={FFD83740-5D49-11DF-8005-444553540000}
Pete Dowson Posted January 22, 2014 Report Posted January 22, 2014 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
Hofer Posted January 22, 2014 Author Report Posted January 22, 2014 I just tried it and it does not work :(
Pete Dowson Posted January 22, 2014 Report Posted January 22, 2014 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
Hofer Posted January 22, 2014 Author Report Posted January 22, 2014 ********* FSUIPC4, Version 4.928 by Pete Dowson *********Running inside FSX on Windows 8Module base=598B0000User Name="Florian Herrmann"User Addr="florian-herrmann@t-online.de"FSUIPC4 Key is providedWIDEFS7 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!
Hofer Posted January 22, 2014 Author Report Posted January 22, 2014 [General]UpdatedByVersion=4928History=NLXKDKXC95UA4CO5GA3O2AxesWrongRange=NoTCASid=FlightTCASrange=40AxisCalibration=NoDirectAxesToCalibs=NoShowMultilineWindow=YesSuppressSingleline=NoSuppressMultilineFS=NoAxisIntercepts=NoDontResetAxes=NoInitDelay=0GetNearestAirports=YesOOMcheck=YesWeatherReadFactor=2WeatherRewriteSeconds=1CustomWeatherModify=NoSimConnectStallTime=1LuaRerunDelay=66Console=NoInitDelayDevicesToo=NoNewInterceptTextMenu=NoUseSystemTime=NoUseMidMouseBtn=YesMouseWheelMove=NoMouseWheelTrim=NoMouseWheelTrimSpeed=1JoystickTimeout=20PollGFTQ6=YesBlankDisplays=NoFixControlAccel=NoFixMachSpeedBug=NoDeleteVehiclesForAES=YesAutoScanDevices=YesVisibilityOptions=NoOneCloudLayer=NoCloudTurbulence=NoCloudIcing=NoGenerateCirrus=NoSuppressCloudTurbulence=NoMaxIce=-4MinIce=-4UpperWindGusts=NoSuppressWindTurbulence=NoSuppressWindVariance=NoWindTurbulence=NoTurbulenceRate=1.0,5.0TurbulenceDivisor=20,20,40,40SuppressAllGusts=NoMaxSurfaceWind=0WindLimitLevel=200WindDiscardLevel=400WindAjustAltitude=NoWindAjustAltitudeBy=2000SmoothBySimTime=NoWindSmoothing=NoWindSmoothness=2WindSmoothAirborneOnly=YesPressureSmoothness=0TemperatureSmoothness=0DisconnTrimForAP=NoZeroElevForAPAlt=NoThrottleSyncAll=NoWhiteMessages=NoShowPMcontrols=NoSpoilerIncrement=512MagicBattery=NoRudderSpikeRemoval=NoElevatorSpikeRemoval=NoAileronSpikeRemoval=NoReversedElevatorTrim=NoClockSync=NoClockSyncMins=5ClearWeatherDynamics=NoOwnWeatherChanges=NoTimeForSelect=4LoadFlightMenu=NoLoadPlanMenu=NoPauseAfterCrash=NoBrakeReleaseThreshold=75SaveDataWithFlights=NoZapSound=fireworkShortAircraftNameOk=SubstringUseProfiles=YesEnableMouseLook=NoDebug=PleaseLogExtras=x200008FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0SimConnectUsed=10.0.61259.0[JoyNames]AutoAssignLetters=No0=Saitek Cyborg USB Stick0.GUID={FFD83740-5D49-11DF-8005-444553540000}[WideServer]WideFSenabled=Yes[sounds]Path=C:\FSX\Sound\Device1=Primärer SoundtreiberDevice2=Lautsprecher (Realtek High Definition Audio)Device3=Realtek Digital Output (Realtek High Definition Audio)[buttons]ButtonRepeat=20,10[AutoSave]Next=1Interval=60Files=10SaveOnGround=NoAutoSaveEnabled=No[GPSout]GPSoutEnabled=No[GPSout2]GPSoutEnabled=No[JoystickCalibration]AllowSuppressForPFCquad=YesExcludeThrottleSet=YesExcludeMixtureSet=YesExcludePropPitchSet=YesSepRevsJetsOnly=NoApplyHeloTrim=NoUseAxisControlsForNRZ=NoFlapsSetControl=0FlapDetents=NoReverserControl=66292Reverser1Control=66422Reverser2Control=66425Reverser3Control=66428Reverser4Control=66431MaxThrottleForReverser=256AileronTrimControl=66731RudderTrimControl=66732CowlFlaps1Control=66162CowlFlaps2Control=66163CowlFlaps3Control=66164CowlFlaps4Control=66165SteeringTillerControl=0MaxSteerSpeed=60[Profile.FlorianH]1=Aircreation582SL red
Pete Dowson Posted January 22, 2014 Report Posted January 22, 2014 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
Pete Dowson Posted January 22, 2014 Report Posted January 22, 2014 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
Pete Dowson Posted January 29, 2014 Report Posted January 29, 2014 Okay. What do you recommend? I've avoided Win8 entirely. Win7 is the best version of Windows ever and I'm sticking with it. Sorry, I've no other answer. You could try repairing or reinstalling Windows, or rolling back to some previous restore point. Pete
Hofer Posted January 29, 2014 Author Report Posted January 29, 2014 Okay... May does it help when I use the FSUIPC_LOADER?
Pete Dowson Posted January 29, 2014 Report Posted January 29, 2014 Okay... May does it help when I use the FSUIPC_LOADER? You could try it. All that does is delay the startup a little, to avoid clashes with other add-in programs. Pete
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now