Jonathan Dale Dowdy Posted March 22, 2014 Report Posted March 22, 2014 I have a registered copy of FSUIPC v4.929 and I am not able to get any response when trying to assign axis to the module. I have looked over the users guide and the advanced users guide and it says to press the rescan button and then move an axis. The axis that moves first is the one that will be picked up and displayed for it to be used. I have tried many times to assign different axes with no luck. I have removed the .dll file and started with a brand new install of FSUIPC and nothing. When I disable the controllers in FSX I can not use the joystick calibration tool in the module, but when the controllers are enabled I have the ability to calibrate. This is having me scratch my head a little and makes me want to throw my computer down a long hallway. I am currently running Windows 8 with FSX installed and working but losing the joystick rudder and throttle quadrant mid flight. All three products are Saitek (I know Mr. Dowson has issues with Saitek, did not know that when I bought them) but not sure what to do any ideas will be greatly appreciated. Attached is the .ini file from my modules folder if it helps at all. [AutoSave]AutoSaveEnabled=NoNext=1Interval=60Files=10SaveOnGround=No [GPSout]GPSoutEnabled=NoPort=COM0Speed=4800Interval=2000PosTo6Decimal=NoSimModeIndicator=NoSentences= [GPSout2]GPSoutEnabled=NoPort=<none set>Speed=4800Interval=2000PosTo6Decimal=NoSimModeIndicator=NoSentences= [WideServer]WideFSenabled=Yes [General]UpdatedByVersion=4929History=MLTSWGT8H1CT1DPLG5YJ9InitDelayDevicesToo=NoNewInterceptTextMenu=NoUseSystemTime=NoUseMidMouseBtn=YesMouseWheelMove=NoMouseWheelTrim=NoMouseWheelTrimSpeed=1JoystickTimeout=20PollGFTQ6=YesBlankDisplays=NoFixControlAccel=NoFixMachSpeedBug=NoDeleteVehiclesForAES=YesAutoScanDevices=YesVisibilityOptions=NoOneCloudLayer=NoCloudTurbulence=NoCloudIcing=NoGenerateCirrus=NoSuppressCloudTurbulence=NoMaxIce=3MinIce=-1UpperWindGusts=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=NoDelayedMouseLookZoom=NoAxesWrongRange=NoTCASid=FlightTCASrange=40AxisCalibration=NoDirectAxesToCalibs=NoShowMultilineWindow=YesSuppressSingleline=NoSuppressMultilineFS=NoAxisIntercepts=YesDontResetAxes=NoInitDelay=0GetNearestAirports=YesOOMcheck=YesWeatherReadFactor=2WeatherRewriteSeconds=1CustomWeatherModify=NoSimConnectStallTime=1LuaRerunDelay=66Console=NoFSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0SimConnectUsed=10.0.61259.0 [JoyNames]AutoAssignLetters=No0=Saitek Pro Flight Yoke0.GUID={D005F080-A6D2-11E3-8004-444553540000}1=Saitek Pro Flight Rudder Pedals1.GUID={D0021FF0-A6D2-11E3-8003-444553540000}2=Saitek Pro Flight Throttle Quadrant2.GUID={D00B47B0-A6D2-11E3-8006-444553540000} [buttons]ButtonRepeat=20,10 [sounds]Path=C:\FSX\Sound\Device1=Primary Sound DriverDevice2=Speakers / Headphones (IDT High Definition Audio CODEC)Device3=Digital Output (S/PDIF) (IDT High Definition Audio CODEC)Device4=AMD HDMI Output (AMD High Definition Audio Device) [JoystickCalibration]AllowSuppressForPFCquad=YesExcludeThrottleSet=YesExcludeMixtureSet=YesExcludePropPitchSet=YesSepRevsJetsOnly=NoApplyHeloTrim=NoUseAxisControlsForNRZ=NoFlapsSetControl=0FlapDetents=NoReverserControl=66292Reverser1Control=66422Reverser2Control=66425Reverser3Control=66428Reverser4Control=66431MaxThrottleForReverser=256AileronTrimControl=66731RudderTrimControl=66732CowlFlaps1Control=66162CowlFlaps2Control=66163CowlFlaps3Control=66164CowlFlaps4Control=66165SteeringTillerControl=0MaxSteerSpeed=60PropPitch=-16256,16256Mixture=-16256,16256LeftBrake=-16256,16256/16RightBrake=-16256,16256/16Throttle1=-16256,-512,512,16256/32Throttle2=-16256,-512,512,16256/32Throttle3=-16256,-512,512,16256/32Throttle4=-16256,-512,512,16256/32 Very Respectfully, Jonathan Dowdy
Pete Dowson Posted March 22, 2014 Report Posted March 22, 2014 I have a registered copy of FSUIPC v4.929 and I am not able to get any response when trying to assign axis to the module. I have looked over the users guide and the advanced users guide and it says to press the rescan button and then move an axis. The axis that moves first is the one that will be picked up and displayed for it to be used. I have tried many times to assign different axes with no luck. I have removed the .dll file and started with a brand new install of FSUIPC and nothing. Replacing a DLL with an identical DLL rarely achieves anything! Attached is the .ini file from my modules folder if it helps at all. Well, it certainly shows that the devices are identified from the Registry: [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight Yoke 0.GUID={D005F080-A6D2-11E3-8004-444553540000} 1=Saitek Pro Flight Rudder Pedals 1.GUID={D0021FF0-A6D2-11E3-8003-444553540000} 2=Saitek Pro Flight Throttle Quadrant 2.GUID={D00B47B0-A6D2-11E3-8006-444553540000} I see there's no [Axes] section at all, which is indeed most odd. I've never seen anyone have a result like this. It's as if the USB side of things is completely unresponsive. I know some folks have problems with USB devices on Windows 8, but this is a bit extreme! I notice that there are no buttons assigned either. Have you tried assigning buttons at all? You don't say. You didn't show me the Log file. Have you looked in there to see if any errors are shown? Maybe we can find out what is happening with more logging. Could you please edit the INI file, adding these lines to the [General] section: Debug=Please LogAxes=Yes LogButtonsKeys=Yes LogExtras=xA00008 Make sure controllers are disabled in FSX Then run FSX and go to FSUIPC options and move each axes a couple of times. Also go to the Buttons tab and see if it responds to button presses. Show me the resulting FSUIPC4.LOG file. Regards Pete
wedge Posted March 22, 2014 Report Posted March 22, 2014 Hello Pete. I might join on this thread as I'm facing quite a similar issue.I've been using FSX within Windows 8 since a good amount of time. and was using the X52 Pro until recently which always worked perfectly, and thanks to FSUIPC never lost the controler during flight, wether small or lengthy, while FS would lose them randomly, but usually very quickly. So I've wanted to upgrade my things a little and I've gone to get a X55, because I knew all the things around the saitek software and never had any trouble with their controlers ever since I started with an X45. And also have a rudder pedal set which works nicely. So the problem comes with the Rhino, but only a part of it, which is the stick part. I can get the throttle working just fine and assign it's axes without any problem. But as for the stick it's completely unseen within FSUIPC interface. I can move the stick all that I want it won't detect anything. While it works perfectly for the throttle part, and still work perfectly for the rudder too. So before making the test above I deleted the FSUIPC.ini file so I would make sure it would be clean, and it did not changed a thing so I did apply the logging option, and have placed the resulting file here : http://www.atlanteans.net/FSUIPC4.rar (the ini is included as well) I did try the controller on other sim like Take On Helicopter or DCS A10C and for neither there were an issue. Also as long as FS did not ditch the controlers, if I get in the FSX command options and try to assign an axis to this stick it works fine. I hope you might have tome pointers to sort the issue :) Cheers. Aurelien
Pete Dowson Posted March 22, 2014 Report Posted March 22, 2014 So the problem comes with the Rhino, but only a part of it, which is the stick part. I can get the throttle working just fine and assign it's axes without any problem. But as for the stick it's completely unseen within FSUIPC interface. I can move the stick all that I want it won't detect anything. While it works perfectly for the throttle part, and still work perfectly for the rudder too. The log is rather overfull with useless repeats of errors on unconnected devices, so I'm making a little interim FSUIPC update which doesn't repeat those. However, the log does certainly show that FSUIPC is successfully reading all three devices fine: 59531 Read joy 0, Buttons=x80000000, POV=-1 59531 Axes: X=65535,Y=65535,Z=33800,R=33284,U=37670,V=24252 59531 S=0,T=0,P=-1,Q=-1,M=-1,N=-1 59531 Read joy 1, Buttons=x00000000, POV=-1 59531 Axes: X=0,Y=0,Z=0,R=0,U=0,V=0 59531 S=0,T=0,P=-1,Q=-1,M=-1,N=-1 59531 Read joy 2, Buttons=x00000000, POV=-1 59531 Axes: X=0,Y=0,Z=0,R=0,U=0,V=32639 59531 S=0,T=0,P=-1,Q=-1,M=-1,N=-1 #0 is your throttle and has values on all 6 axes as you can see the 65535 values for X and Y are a standard indication for a missing axis). #1 seems to only be returning values 0 -- which are specifically returned values, not like 65535 for missing axes. #2, your rudder, has a value for axis V, which seems and dd axis for a rudder, but may be correct? You say you have the throttle and rudder working, but there are no assignments in your INI file, so I'm not sure what you mean by that. Can you clarify? You apear to have no button assignments either, and you haven't answered the question about whether your buttons are seen in FSUIPC or not. Did you actually move any of te axes during the time of the log? You only seemed to have it running for 19 seconds. Do you have some Saitek software installed? The log definitely shows that FSUIPC sees the device and is reading the values using the standard Windows interface without any problems. It's just that the values are stuck at zero. I'm thinking this is an incompatiblity between the Saitek drivers and Windows 8 -- possibly just a more extreme example of the problems n Windows 8 affecting all joystick users. I can only suggest trying to uninstall the devices including any drivers and rebooting so that they are re-discovered as ordinary USB devices without any special drivers. You might also check wth the Saitek support forum to see if there's any help there or others seeking the same. Regards Pete
Jonathan Dale Dowdy Posted March 22, 2014 Author Report Posted March 22, 2014 Mr. Dowson, Thank you for such a speedy reply. I have looked through the log from last night and did not see an error in that file. I have added the lines under general to allow the extra logging and there is more in the log file now. However when I try and copy and paste it locks up the web page as the file really long with a bunch on repeating errors. I have tried to push buttons on the buttons+keys page and did not get any feedback there either. I did not stay in the FSUIPC page a long time as there was not any response coming back from the module, done the test and got the log. I am running FSX in compatibility mode to Windows 7 and have it installed directly to the root folder instead of installed in the Program files area. Not sure if that makes a difference but thought it might be pertinent. Here is the Log file: ********* FSUIPC4, Version 4.929 by Pete Dowson *********Reading options from "C:\FSX\Modules\FSUIPC4.ini"Running inside FSX on Windows 7Module base=66040000User Name="Jonathan Dowdy"User Addr="pfcdowdy@yahoo.com"FSUIPC4 Key is providedWIDEFS7 not user registered, or expired 1092 System time = 22/03/2014 10:58:22 1092 FLT path = "C:\Users\pfcdo_000\Documents\Flight Simulator X Files\" 1138 Trying to connect to SimConnect Acc/SP2 Oct07 ... 1170 FS path = "C:\FSX\" 1544 #### Initialising Dlrectinput Axis Scanning ... 1544 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0BAC\Calibration\0" 1544 Found correct joystick Id 0 1544 ... and a "GUID" value 1560 DirectInput8Create failed, return = 80040154 1560 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0" 1560 Found correct joystick Id 1 1560 ... and a "GUID" value 1591 DirectInput8Create failed, return = 80040154 1591 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0" 1591 Found correct joystick Id 2 1591 ... and a "GUID" value 1606 DirectInput8Create failed, return = 80040154 1606 joyGetDevCaps for device 3 returned error 165 [000000A5] 1606 joyGetDevCaps for device 4 returned error 165 [000000A5] 1606 joyGetDevCaps for device 5 returned error 165 [000000A5] 1606 joyGetDevCaps for device 6 returned error 165 [000000A5] 1606 joyGetDevCaps for device 7 returned error 165 [000000A5] 1606 joyGetDevCaps for device 8 returned error 165 [000000A5] 1606 joyGetDevCaps for device 9 returned error 165 [000000A5] 1606 joyGetDevCaps for device 10 returned error 165 [000000A5] 1606 joyGetDevCaps for device 11 returned error 165 [000000A5] 1606 joyGetDevCaps for device 12 returned error 165 [000000A5] 1606 joyGetDevCaps for device 13 returned error 165 [000000A5] 1606 joyGetDevCaps for device 14 returned error 165 [000000A5] 1606 joyGetDevCaps for device 15 returned error 165 [000000A5] 1606 #### Completed Dlrectinput Axis Scanning 1653 N.B. All Axis Intercepts are enabled! 1653 LogOptions=50000000 0A000091 1653 SIM1 Frictions access gained 1684 Wind smoothing may be by ASN, not FSUIPC, if it is running 1684 Will switch smoothing action when ASN starts/stops 1684 G3D.DLL fix attempt installed ok 1684 SimConnect_Open succeeded: waiting to check version okay 1684 Trying to use SimConnect Acc/SP2 Oct07 1684 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 1684 Initialising SimConnect data requests now 1684 FSUIPC Menu entry added 1716 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 1716 C:\FSX\FLIGHTS\OTHER\FLTSIM.FLT 1716 C:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 3229 Memory in use: 862Mb, Avail=3234Mb 38392 C:\FSX\SimObjects\Airplanes\beech_baron_58\Beech_Baron_58.AIR 68890 Memory in use: 1007Mb, Avail=3089Mb 129075 Memory in use: 1013Mb, Avail=3083Mb 143271 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 144082 System time = 22/03/2014 11:00:45, Simulator time = 13:58:22 (18:58Z) 144098 Aircraft="Beech Baron 58" 144191 ASN Running? Smoothing is by ASN 145065 Starting everything now ... 145081 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 148715 Advanced Weather Interface Enabled 185142 KEYDOWN: VK=27, Waiting=0, Repeat=N, Shifts=0 185142 .. Key not programmed -- passed on to FS 185173 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 185173 Sim stopped: average frame rate for last 42 secs = 17.1 fps 189681 Memory in use: 1291Mb, Avail=2805Mb 189697 Weather Mode now = Theme 189697 C:\Users\pfcdo_000\AppData\Roaming\Microsoft\FSX\Previous flight.FLT 249851 Memory in use: 1307Mb, Avail=2789Mb 251504 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 302376 KEYDOWN: VK=102, Waiting=0, Repeat=N, Shifts=0 302376 .. Key not programmed -- passed on to FS 302376 KEYUP: VK=102, Waiting=0 310052 Memory in use: 1310Mb, Avail=2786Mb 358006 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 358006 Sim stopped: average frame rate for last 106 secs = 15.7 fps 372202 Memory in use: 1316Mb, Avail=2780Mb 432434 Memory in use: 1325Mb, Avail=2771Mb 432544 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 442715 ASN smoothing disconnected 446428 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 447863 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #0 is zero! 447863 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #1 is zero! 447863 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #2 is zero! 447863 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #3 is zero! 447863 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #4 is zero! 447863 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #5 is zero! 447863 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #6 is zero! 447863 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #7 is zero! 447863 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #8 is zero! 447863 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #9 is zero! 447863 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #10 is zero! 447863 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #11 is zero! 447863 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #12 is zero! 447863 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #13 is zero! 447863 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #14 is zero! 447863 *** JOY ERROR: The LPDIRECTINPUTDEVICE8 handle for Joy #15 is zero! (This repeats over and over, I believe it is put in every time I moved an axis. I don't think you want thousands of lines of this) 635158 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 670320 KEYDOWN: VK=27, Waiting=0, Repeat=N, Shifts=0 670320 .. Key not programmed -- passed on to FS 670352 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 670352 Sim stopped: average frame rate for last 35 secs = 17.2 fps 675110 Memory in use: 1330Mb, Avail=2766Mb Again thank you for all your Help. Very Respectfully, Jonathan Dowdy
Pete Dowson Posted March 22, 2014 Report Posted March 22, 2014 I have looked through the log from last night and did not see an error in that file. I have added the lines under general to allow the extra logging and there is more in the log file now. However when I try and copy and paste it locks up the web page as the file really long with a bunch on repeating errors. Yes, I'll be uploading an interim update to stop those repeating unnecessarily. Did you see the other report, above, about a similar (but different) problem, and my reply? Your case is certainly different. Windows DirectInput is returning an error, so that FSUIPC cannot read any of the devices: I am running FSX in compatibility mode to Windows 7 I don't see the point of doing that -- FSX was released before Windows 7 was thought of, so if you are going to run it in Compatibility Mode at all I would have thought XP more appropriate. The error returned by Windows is: DirectInput8Create failed, return = 80040154 for all three connected devices! I checked the number, it means "Class not registered", which is either a Regstry corruption, or a missing DLL, or an unregistered DLL. I'm afraid I don't know how to fix that other than bytrying to uninstall and reinstall the devices from scratch. Maybe there's help available in the Saitek forum? I notice it is only Saitek devices which seem to have these sorts of problems. Regards Pete
wedge Posted March 22, 2014 Report Posted March 22, 2014 Hello. Thanks for the answer here are the answers : You say you have the throttle and rudder working, but there are no assignments in your INI file, so I'm not sure what you mean by that. Can you clarify? You apear to have no button assignments either, and you haven't answered the question about whether your buttons are seen in FSUIPC or not. I've not reassigned things at all for the test as I deleted the FSUIPC ini file to make sure it was clean. What I mean by that is that axis from the rudder and throttle are detected in the axis assignment window in the FSUIPC options. And I've the same issue with the buttons, Throttle buttons push are detected by FSUIPC but those from the stick don't do a thing and are not detected in FSUIPC. On both case the Joy/Axes or Joy/button window stay empty for any stick action and do fill on throttle actions. Did you actually move any of te axes during the time of the log? You only seemed to have it running for 19 seconds. Yeah I move only the Stick having the issue in all direction for a few times up/down, a few left/right and a few twisting in both direction while being in FSUIPC options. Did not stayed longer than necessary, but could go for longer if needed. Do you have some Saitek software installed? The log definitely shows that FSUIPC sees the device and is reading the values using the standard Windows interface without any problems. It's just that the values are stuck at zero. Yes both drivers and softwares are installed. Just the same way as they are for the rudder and as I had done with my X52 Pro. I'll try your suggesion this evening, I think I had tried that but only then reinstalled drivers and software, so I should remove all the occurences of the hardware in the windows manager, removing the pilot for each, remove the software, unplug everything. Reboot and then plugin the stick and try to get it working without doing anything or installing anything. Is that correct ? Cheers
Jonathan Dale Dowdy Posted March 22, 2014 Author Report Posted March 22, 2014 (edited) Mr. Dowson, You said I don't see the point of doing that -- FSX was released before Windows 7 was thought of, so if you are going to run it in Compatibility Mode at all I would have thought XP more appropriate. The error returned by Windows is: DirectInput8Create failed, return = 80040154 So I searched for all Directinput8 files and found only one. It was found in the main FSX folder so I deleted it. I have no idea how it got there, my guess is it was tagged in with a freeware addon I installed at some point. I deleted it out and I can now get axis assignment information, as well as Button + Switches Assignments. Thanks for your help with this I am going to see if I can get things set up with all FSUIPC controls and get up in the air again. It seems the DirectInput8 file was blocking information from getting to the module. Relieved, Jonathan Dowdy Edited March 22, 2014 by Jonathan Dale Dowdy
Pete Dowson Posted March 22, 2014 Report Posted March 22, 2014 So I searched for all Directinput8 files and found only one. It was found in the main FSX folder so I deleted it. I have no idea how it got there, my guess is it was tagged in with a freeware addon I installed at some point. I deleted it out and I can now get axis assignment information, as well as Button + Switches Assignments. Thanks for your help with this I am going to see if I can get things set up with all FSUIPC controls and get up in the air again. It seems the DirectInput8 file was blocking information from getting to the module. Hmm. Interesting. I've heard of DX video modules in the FS folder messing things up on the graphics front. but this is a first for me with DirectInput. Thanks for letting me know! I'll bear this one in mind! Pete
wedge Posted March 23, 2014 Report Posted March 23, 2014 Ok I did try removing everything but it's still the same. Though I can't be sure it really properly deleted everything. I've tried to find a way to clean properly but did not find any I check the box to remove driver too on deleting items in the windows hardware manager, and so now when I plug they don't appear in the user interface part, and I have two hardwares that have the yellow exclamation mark which are Saitek Bus which I believe ust be the Throttle and the Stick. But that is still the samething as long as FS sees it there is no problem for FS axis assignement, but still invisible for FSUIPC. And as previously the throttle is here and working just fine and nothing from the stick.
Pete Dowson Posted March 23, 2014 Report Posted March 23, 2014 But that is still the samething as long as FS sees it there is no problem for FS axis assignement, but still invisible for FSUIPC. And as previously the throttle is here and working just fine and nothing from the stick. I'm pretty sure i must be a Windows problem somewhere -- registry or drivers. FSUIPC uses pretty much the same facilities in Windows as FSX, but probably a different version level - DX8 instead of DX9 I think. But all updates to DX are backwards compatible (else when DX10, DX11 etc came out and got installed FSX etc wouldn't work). With this in mind, I would have advised trying to repair Windows -- maybe update or reinstall the current DirectX package. But one thing which contradicts all this is that some devices are detected, which in turn points away from DirectX problems and straight back at the way the devices are defined to Windows -- i.e. registry. I don't know how you'd sort that out. Is there no help on the Saitek forum at all? FSUIPC can't really do anything unless it sees the devices, and it evidently doesn't see all of them. Pete
wedge Posted March 23, 2014 Report Posted March 23, 2014 I'll try and see things on staitek side, but there is very little activity on their forums. I've a ticket with support but no real answer yet, so gonna check on that. The DirectX websetup says everythign is up to date so nothing on that side either. I'll keep searching there must be something somewhere as just one is not visible and only in FSX and the Windows calibration. Inside any other sim I've tried they are both detected fine. And while testing I don't know why but I had once an opposite situation where the stick would work and the throttle would not be.
wedge Posted March 23, 2014 Report Posted March 23, 2014 Allright I might have made some progress though surprising enough, and that seemed both unrelated to either Saitek or DirectX. While searching for joystick test application, I did find a small application called JoyIDs which purpose is to change the device ids for the joysticks. in the last trials I had the throttle in #1, the joystick in #2 and the rudder pedal in #3. I have previously reinstalled the official drivers too, which was not fixing anything. Having only the stick not working I changed it's id to #12, not chose really specifically, just wanted to change, and surprisingly enough windows started to see the axis and button in the calibration menu, as well as FSUIPC within FSX. Not sure at all of what caused this though, but looks fixed, but interesting to keep in my mind. I tried rebooting the PC it worked ,as well as unplugging, rebooting and plugging again and it's still there, I believe I might have solved that issue.
Pete Dowson Posted March 23, 2014 Report Posted March 23, 2014 Having only the stick not working I changed it's id to #12, not chose really specifically, just wanted to change, and surprisingly enough windows started to see the axis and button in the calibration menu, as well as FSUIPC within FSX. I think that seems to prove a Registry problem, because it is the registry entries for a device which determine that joystick ID. The actual IDs were seen be FSUIPC before (hence the Joy stick identities in the INI file), but then they didn't respond using the associated data. Not sure at all of what caused this though, but looks fixed, but interesting to keep in my mind. I tried rebooting the PC it worked ,as well as unplugging, rebooting and plugging again and it's still there, I believe I might have solved that issue. Good. Let's hope so. Could you give me a link to that JoyIDs program, please? I'd be interested in seeing exactly what Registry changes that makes. It may also be worth me putting it as a link in a new FAQ subforum thread on the subject. Pete
wedge Posted March 23, 2014 Report Posted March 23, 2014 No problem here is the page on which I found the program http://www.wingmanteam.com/latest_software/gadgets.htm Just a little more tidbit that one is strange but I don't want to touch it since it is working, now when I look the JoyNames part of the inie file here is what there is : [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight X-55 Rhino Throttle 0.GUID={83E96F30-A6B2-11E3-8003-444553540000} 2=Saitek Pro Flight Rudder Pedals 2.GUID={AB9245C0-DFDE-11E2-8006-444553540000} 11=Saitek Pro Flight X-55 Rhino Stick 11.GUID={7DA742F0-A6B2-11E3-8002-444553540000} 14=Saitek Pro Flight X-55 Rhino Stick 14.GUID={7DA742F0-A6B2-11E3-8001-444553540000} It does detect things also on the log 250 #### Initialising Dlrectinput Axis Scanning ... 250 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_A215\Calibration\0" 250 Found correct joystick Id 0 250 ... and a "GUID" value 250 ... okay, Acquired device! 250 joyGetDevCaps for device 1 returned error 165 [000000A5] 250 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0" 250 Found correct joystick Id 2 250 ... and a "GUID" value 250 ... okay, Acquired device! 250 joyGetDevCaps for device 3 returned error 165 [000000A5] 250 joyGetDevCaps for device 4 returned error 165 [000000A5] 250 joyGetDevCaps for device 5 returned error 165 [000000A5] 250 joyGetDevCaps for device 6 returned error 165 [000000A5] 250 joyGetDevCaps for device 7 returned error 165 [000000A5] 250 joyGetDevCaps for device 8 returned error 165 [000000A5] 250 joyGetDevCaps for device 9 returned error 165 [000000A5] 250 joyGetDevCaps for device 10 returned error 165 [000000A5] 250 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2215\Calibration\0" 250 "Joystick Id" value = 14, not wanted this time 250 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2215\Calibration\1" 250 Found correct joystick Id 11 250 ... and a "GUID" value 250 ... okay, Acquired device! 250 joyGetDevCaps for device 12 returned error 165 [000000A5] 250 joyGetDevCaps for device 13 returned error 165 [000000A5] 250 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2215\Calibration\0" 250 Found correct joystick Id 14 250 ... and a "GUID" value 250 ... okay, Acquired device! 250 joyGetDevCaps for device 15 returned error 165 [000000A5] 250 #### Completed Dlrectinput Axis Scanning which is a little odd though as long as it works I don't really mind. Now I've another issue with the throttles and PMDG 777 as when the AT is arm and all the throttle still act on the controls and the blue position bar does not position correctly either, but that is not an issue with FSUIPC :)
Pete Dowson Posted March 23, 2014 Report Posted March 23, 2014 No problem here is the page on which I found the program http://www.wingmanteam.com/latest_software/gadgets.htm Thanks! 11=Saitek Pro Flight X-55 Rhino Stick 11.GUID={7DA742F0-A6B2-11E3-8002-444553540000} 14=Saitek Pro Flight X-55 Rhino Stick 14.GUID={7DA742F0-A6B2-11E3-8001-444553540000} Hmm. Very odd. I assume there is still only one of those? Evidently the same device now has two entries in the Registry -- and with two different GUIDs! Which does FSUIPC respond to, 11 or 14? Also odd no #12, when you said "I changed it's id to #12"! The original, according to the earlier INI you posted, was 1=Saitek Pro Flight X-55 Rhino Stick 1.GUID={7DA742F0-A6B2-11E3-8001-444553540000} which would equate it to #14 in your new configuration. Pete
wedge Posted March 23, 2014 Report Posted March 23, 2014 Yes don't kow what is going on but the stick is actually on the ID 11 both on the joyids program and on the FSUIPC axis assignement. I do wonder if there might not be some "virtual" device with the X55 as Saitek through it's new control panel allow a lot of alibration, deadband, saturation, curves and all. Maybe the 14 is the raw input that Saitek then takes and passes to Dx through the 11 ID, though it would do it only for the stick which would be strange. I've also fixed the throttle issue through one of your other post with the UseAxisControlsForNRZ=Yes option. Looks like I'm all set now. I hope it'll stay like this :) Thanks a lot for the support! :) Edit: just a little addition when checking on the DX Input page there are also two sticks listed which concurs with FSUIPC detections though th esecond one have 0 id, and I see the workign one with it's 11 id Edit 2: Made a thread on the AVSIM community forum on the hardware section so it might help others facing the issue : http://forum.avsim.net/topic/437639-x55-not-working-with-fsuipc-fsx-solution/
Andy Browne Posted November 19, 2014 Report Posted November 19, 2014 (edited) Hiya, and sorry to resurrect an older thread, but I just got a Saitek X55 HOTAS and I've run into the same problem with the stick not being recognised. It works fine in DCS World, but trying to program in FSX using FSUIPC has been impossible. I've opened a ticket with MadCatz Tech Support, but just found this in their knowledge-base: http://support.madcatz.com/Knowledgebase/Article/View/486/176/im-running-on-win81-and-when-i-go-to-the-game-controllers--settings-tab-in-the-control-panel-the-throttles-settings-say-it-needs-to-be-calibrated-whats-going-on It would appear that for FSUIPC to hook the inputs from the stick its necessary for Windows to do its jobs and pick up the inputs in the first place, and Saitek have missed something when creating the drivers. Its obviously an ongoing issue with them, and hopefully they get it sorted soon. Is everyone above everyone reporting trouble with the X55 and FSUIPC running Windows 8.1 as well? Edited November 19, 2014 by Andy Browne
benjiminus Posted November 30, 2014 Report Posted November 30, 2014 I'm running into the same problem. I just purchased the JetMax throttle quadrant and for the life of me can't get the axis assignment to work. I'm pretty new to FSUIPC and could use some help.
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