gmcraib

Renaming SaiD0BAC.PRO as instructed, I can confirm that after doing this and restarting I had button functions again.

Tried the additional logging, this was the result: 512401 Button changed: bRef=0, Joy=1 (B), Btn=1, Pressed 512401 [Buttons] 102=CP(+B,8)(-B,11)B,1,C66483,0 512401 .... Condition (+B,8) = FALSE 512401 [Buttons] 103=CP(+B,8)(+B,11)B,1,C66483,0 512401 .... Condition (+B,8) = FALSE 512401 [Buttons] 202=CP(+B,9)B,1,C65580,0 512401 .... Condition (+B,9) = FALSE 512401 [Buttons] 302=CP(+B,10)(-B,11)B,1,C65567,0 512401 .... Condition (+B,10) = FALSE 512401 [Buttons] 303=CP(+B,10)(+B,11)B,1,C66153,0 512401 .... Condition (+B,10) = FALSE 512401 Monitor IPC:03C4 (U32) = 2 512635 Button changed: bRef=0, Joy=1 (B), Btn=1, Released 512651 Monitor IPC:03C4 (U32) = 0 It was the same in all three positions of the mode switch.

Will also try this John, for trouble shooting but not overly keen on implementing as a permanent solution in case it causes an issue with the Saitek drivers. I mean renaming this: SaiD0BAC.PRO

Spoke too soon, the issue is back! Will continue from where we left off.....

Hello chaps, well good news and bad news..... After some extensive testing, I cannot recreate the issue. So its good news (perhaps) in that the issue seems to have gone away (hopefully) but bad news in the sense of troubleshooting. In fact, in the world of fault finding there is nothing worse than this scenario!!

HI Pete, I think FSUIPC is seeing the buttons, certainly is seeing the individual button presses but not so sure about the compound button presses at least when the gamer controller properties is not open. I know it picks up individual button presses as it reports this in the menu, but it refers you back to the .ini file as they are compound functions. So you can't tell from that alone if it has detected the compound presses. In the 736855 event 1 of commands 102 OR 202 OR 302 must be true, but it has reported false for all 3. So there is an issue there. I know the buttons are functioning in windows (including the mode select) but its not clear if this is being detected in FSUIPC. The mode select switch can only be set at 1, 2 or 3 (which is button 8, 9, 10). (button 11 is shift operator and it was = 0). From the log file it looks like FSUIPC detects press of button 0 (as was also seen in the menu) but given the FLASE state reported for 102-202-302 it must also be detecting buttons 8-9-10 as 0 whereas one of them is always = 1 (in this case it was button 9 = 1 ie mode 2). But this goes away when the game controller properties box is open in windows so I am completely stumped! So I guess to answer your question specifically, in the example above for event 736855, command line 202 should have been TRUE as button 9 was = 1 when button 0 was pressed. Then later in 773562 it did return TRUE with the same button operations, but the only difference was the game controller properties box open in windows. So there maybe is an issue somewhere either between windows (ie hardware reporting) and FSUIPC, I don't think there is an issue between hardware and windows as windows reports the button states correctly. I'm not sure what to try next, I have a couple of ideas but will await suggestion.

Actually the power management setting was still ticked for the yoke when I double checked! But went back into FSX and same results.

Also for the yoke quad and additional quads, same as previous. Log entries for button 14 (yoke quad) 115160 Button changed: bRef=0, Joy=1 (B), Btn=14, Pressed 115160 [Buttons] 114=CP(+B,8)B,14,C66718,0 115160 .... Condition (+B,8) = FALSE 115160 [Buttons] 313=CP(+B,10)(+B,11)B,14,C65826,0 115160 .... Condition (+B,10) = FALSE 115160 [Buttons] 314=CP(+B,10)(-B,11)B,14,C65825,0 115160 .... Condition (+B,10) = FALSE 115301 Button changed: bRef=0, Joy=1 (B), Btn=14, Released and for additional quad (plugged in USB via yoke): 129310 Button changed: bRef=0, Joy=2 (C), Btn=4, Pressed 129310 [Buttons] 22=PC,4,C65595,0 129310 FS Control Sent: Ctrl=65595, Param=0 129310 *** EVENT: Cntrl= 65595 (0x0001003b), Param= 0 (0x00000000) FLAPS_UP 129528 Button changed: bRef=0, Joy=2 (C), Btn=4, Released Then with game controller properties box open; For button 15 (yoke quad): 194970 Button changed: bRef=0, Joy=1 (B), Btn=15, Pressed 194970 [Buttons] 115=CP(+B,8)B,15,C66719,0 194970 .... Condition (+B,8) = FALSE 194970 [Buttons] 215=CP(+B,9)B,15,C65853,0 194970 .... Condition (+B,9) = TRUE 194970 FS Control Sent: Ctrl=65853, Param=0 194970 [Buttons] 315=CP(+B,10)B,15,C65824,0 194970 .... Condition (+B,10) = FALSE 194970 *** EVENT: Cntrl= 65853 (0x0001013d), Param= 0 (0x00000000) SPOILERS_ARM_TOGGLE It shows function for 202 as in mode 2. So I'm not sure whats happening, the only difference seems to be opening the game controllers dialogue box in windows. I already disabled the USB power saving as discussed previously. The additional quadrant (joy 2) and switch panels are plugged into the yoke USB inputs and they all work fine. It is the yoke buttons and the yoke quad that have the problem (ie joy 1). Also as a side note, is it possible to stop FSUIPC writing comments to the command lines in the config file. I already have my own comments there, although it is useful for troubleshooting.

Have updated FSUIPC and tried again. Checked axis and button inputs in: Windows/control panel (game controllers properties) - OK FSUIPC - OK (note compound settings so mapped to mode 3, eg 3XX series but detected button presses) FSX - not OK (works with game controllers properties dialogue box open). So issue still there. Have attached config, log & joyscan files. Also please see below for specific log entries. Pressing button 0: 736855 [Buttons] 102=CP(+B,8)(-B,11)B,1,C66483,0 736855 .... Condition (+B,8) = FALSE 736855 [Buttons] 103=CP(+B,8)(+B,11)B,1,C66483,0 736855 .... Condition (+B,8) = FALSE 736855 [Buttons] 202=CP(+B,9)B,1,C65580,0 736855 .... Condition (+B,9) = FALSE 736855 [Buttons] 302=CP(+B,10)(-B,11)B,1,C65567,0 736855 .... Condition (+B,10) = FALSE 736855 [Buttons] 303=CP(+B,10)(+B,11)B,1,C66153,0 736855 .... Condition (+B,10) = FALSE 737057 Button changed: bRef=0, Joy=1 (B), Btn=1, Released Commands 102, 202, 302 depend on mode setting 1-2-3 (eg button 8-9-10). 103, 303 fire in respective mode setting with a shift operator. Ignoring 103 & 303 (as shift operator not used) one of 102, 202 or 302 should result in TRUE as it can only be in one of those modes. Trying again with the controller properties box open in windows: 773562 Button changed: bRef=0, Joy=1 (B), Btn=1, Pressed 773562 [Buttons] 102=CP(+B,8)(-B,11)B,1,C66483,0 773562 .... Condition (+B,8) = FALSE 773562 [Buttons] 103=CP(+B,8)(+B,11)B,1,C66483,0 773562 .... Condition (+B,8) = FALSE 773562 [Buttons] 202=CP(+B,9)B,1,C65580,0 773562 .... Condition (+B,9) = TRUE 773562 FS Control Sent: Ctrl=65580, Param=0 773562 [Buttons] 302=CP(+B,10)(-B,11)B,1,C65567,0 773562 .... Condition (+B,10) = FALSE 773562 [Buttons] 303=CP(+B,10)(+B,11)B,1,C66153,0 773562 .... Condition (+B,10) = FALSE 773562 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER It has fired command 202 as the joystick is in mode 2 (button 9). Again 103 & 303 FALSE as shift operator not used (and was in mode 2 anyway). It was the same with a few other button presses but only listed with button 0 for sake of brevity. FSUIPC4.ini FSUIPC4.JoyScan.csv FSUIPC4.log

Hi, I haven't installed updated FSUIPC yet since we spoke last. Will hopefully do today or later this evening. Sorry if things are not clear but not sure how I can explain any clearer. The issue is that the button inputs on the yoke (and its quad) are not doing anything in FSX. Other controllers (eg HOTAS, additional quad and switch panels) are working fine. The axis movements work ok. If I remember correctly the button inputs were detected in FSUIPC but I will have to check everything again after installing updated FSUIPC. Everything works fine if the controller properties dialogue box is open in windows. The quad that isn't working is essentially part of the yoke and recognised as same joystick in FSUIPC, eg joystick B. So all issues appear to lie with joystick B. But if we start from clean slate should be clearer and I'll post up results later.

Ok, I am only doing a few button presses each time. But as they are compound each button has at least 3 functions and the length means they don't fit into a single text line. Will also try to avoid the repeating functions like pan view etc. That doesn't help.

Just noticed the bit about FSUIPC date being out of date. Ok will look into that. Have downloaded v4.975 do you want me to install it and start again or work with the info provided so far as a first step?

Yeah I looked at the log file after attaching them! The throttle was slightly in reverse on that axis. So I have made a new log file showing the events with the controller plugged in directly to PC then (after the pauses just before 319568) and opening the game controller dialogue box with the button presses and commands executed. You'll see the quad functions work in the first set. Also to make it easier the mode settings 1-2-3 reflect the command line eg 102, 202, 302 for that same button. Not sure why the config file didn't attach, it embedded instead? Anyways should be it now. FSUIPC4.ini FSUIPC4.log

Hi, I while back I posted about an issue I was having with FSX not recognising controller inputs apart from when I opened a game controller properties dialogue box (eg for calibration) in windows. It was some time ago and I think I solved the problem honestly can't remember as I have been away from FSX for some time - funny how lockdown brings us back to certain things... anyway, the problem is back - at least to some extent. Previous posts for reference: https://forum.simflight.com/topic/87518-fsuipc-throttle-axis-control/?tab=comments#comment-531701 https://forum.simflight.com/topic/87519-controller-inputs-not-detected/?tab=comments#comment-531654 So the problem is that I have no button input from my yoke (incl quad), I have an additional quadrant and that works fine (it is plugged in to the yoke USB hub). Also curiously all axis are recognised. As before the only way I can get FSX to recognise the button inputs is to open the controller dialogue box. I checked the power management box in device manager (connection view) and switched it off for the USB hub controller. I also have a HOTAS stick & throttle, these work fine. The connection is via a powered USB hub, which is connected to a USB 3.1 gen 1 port on the PC back panel. The HOTAS and yoke (hub) and rudder pedals are connected to this hub. There is a power supply to the yoke hub and it has the yoke quad, additional quad and two Saitek panels connected. There is never an issue in detecting control from the Saitek panels. I have connected rudder and pedals via extension USB leads, to make connecting and disconnecting a bit easier. This doesn't make any difference though. I've tried it as per original (ie into hub with HOTAS), via extension leads, or direct into PC USB ports. Same result each time. Switching off power management did help as I couldn't see these game controllers in the device window (but they were present when invoking properties/calibration via click on HOTAS stick or throttle). Since adjusting the power management settings for the hub they are shown along with the other devices. The buttons are programmed via the FSUIPC config file and include compound assignments (ie use of mode 1-2-3 and 'shift' operators). The joysticks are assigned letters, although they are usually plugged in to same port (I don't think the device ID's change anyways). When I checked the FSUIPC log file/console window it looks like it detects button input but returns FALSE status when assessing the compound functions so hence no command output. I'm stuck and have tried everything I can think of. The only other thing to note was when I programmed the HOTAS via FSUIPC. I think it worked fine before then but it was some time ago. maybe this was when it all started. But I'd like to have the HOTAS for combat jets and the yoke for pretty much everything else. The other sub question is the POV, the POV function is not as smooth using the yoke hat switch as it is with the HOTAS stick POV/hat. Appreciate one is an axis but can this be changed? Anyways dutifully attached log & config files, I'm not sure where to find the other file that is sometimes asked for? I can also provide an excel 'map' of my assignments if needed. Also whilst typing I thought to try with the HOTAS disconnected and to reboot windows! That may help, but obviously I typed all this now so....FSUIPC4.ini FSUIPC4.log

I see you are speaking about P3D not FSX, no idea about that sorry!

I stumbled upon this whilst away to start my own topic. Anyways as you say the FSUIPC.ini file is located in the modules folder. To save having to reprogram and remap (or indeed making mistakes) I save a backup copy of this in a separate area (along with other FSX config files). That way if you have to reinstall, you have the option of reinstating the old settings (either in whole or in part).

Hi John, I seemed to remember opening calibration screen and the controller position was on it, not a neutral starting value. But checked again and that's how it is. Must have been thinking about older PC's, maybe. I mean that I have set the controller up in FSUIPC, but the control inputs were not being picked up by FSUIPC. It has been suggested to look at power saving plan in windows, so I will try that. I do have Saitek drivers for the x-55, I don't use the Saitek software/profiles though. Controllers are disabled in FSX, all inputs via FSUIPC.

Thank you Pete, I did not think of that! Will read the FAQ and hopefully get some time to play with it after doing some work this evening. Thanks again, Graeme

Having recently isntalled windows and FSX I recently noticed that controller inputs had no effect in FSX. I checked the FSUIPC console and nothing was coming up, then checking the controller profile checked calibration etc and all ok. I did notice, however that the initial value did not reflect the controlelr position but quickly cleared. I then went to check this against FSX and with the properties dialogue open the controls were recognised in the sim. This remains the only way I can workaround this problem and I have no idea where to even start! Set-up is Saitek yoke with an extra throttle quadrant (ie so 6 x axis) plus X, Y of the yoke and Z of the rudder pedals. I also have set-up an X-55 stick and throttle. I don't remember having this problem before addint the X-55 to FSUIPC. All controls handled by FSUIPC.

I've been successfully enjoying FSUIPC for some time now and have gone all out and transferred all control to FSUIPC. This is part for ease of assigning keys and controls but also because I want to use multiple joysticks. Recently I have had to reinstall windows and FSX. Did a clean isntall so did not have saved profiles to transfer across, or at least they were minimal and have more or less started again. I noticed on a flight yesterday that throttle 4 is not matching the control of 1-3. Generally it would sti about 20-40% below the other three throttles. When changing the throttle value you get levels close to the other three, say moving from (say 60% to 80%) but it soon settles back down to previous setting (say 40%), regardless of the throttle position. I investigated further and found that throttle 4 has a 0 input (or output, can't remember which) when the others have -16,XXX or along that lines. When moving the position it gives full range but then settles back to 0, which is halfway along the axis and explains the odd throttle value in comparison to the other three. I didn't notice it before as I have been using 2 engine jets to set-up, but all the commands (including axis) are mapped either via the module or directly via the .ini file (I find this easier as I use multiple 'modes' and save this on a keymap to then enter directly to the file). Also another unusual finding this time around is that FSUIPC did not recognise any controller inputs at all! The only way I can workaround this is to open the controller profile via windows devices and then it works. I have no idea where to even start on this one! But will start a new separate topic for it. My set-up is a Saitek Yoke with an extra throttle quadrant. Axis are Spoilers, Throttle 1, Throttle 2 on the yoke throttle and then throttle 3, throttle 4 and flaps on the extra quad. Also an X-55 Rhino for quick play and fast jets. I did not notice any issue on recognising controller inputs before adding the X-55 to FSUIPC. Controllers are disabled in FSX. I'm at work just now so apologies for vagueness, can come back with better detail next time I'm on the sim. Hopefully over the weekend if need be.