scottike

They were from the same folder but I have FSUIPC on a laptop and a desktop. I was developing the control layout on the laptop and then transferred to the desktop (which was still on 7.1.0). I've updated it and the problem remains. Here are new logs after the update. FSUIPC7.logFSUIPC7.JoyScan.csvFSUIPC7.ini

I guess a reboot wasn't the cure. Using the PoV as buttons only works intermittently. The device I'm using is a Teensy 3.6 running teensyduino code. It shows up as a Serial/Keyboard/Joystick/Mouse in the Windows HID list. When using the Windows usb game controller panel the POV directions show up reliably. Moving to FSUIPC the axis changes also show up reliably with each POV change. They do not trigger reliably as buttons. In MSFS the bound events will trigger occasionally if I hold the POV down but it's random and unreliable. I had wanted to shift the function of each POV position with a compound command using a "shift" button on my yoke (K,0). I've also tested without using the compound command and it's still unreliable. I'd switch to using defined axis zones to trigger commands but I think I lose the ability to shift the function of the POV with a compound command. If there's a straightforward was to do that with lua I'm happy to try it. I've attached the log files requested. The controls are still a work in progress so the FSUIPC7.ini file is a bit messy. Thanks again for the help! FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC7.log

Well, a computer reboot solved the problem. Should have tried that first. Thanks for responding so quickly!

I'm in the process of mapping a new controller in FSUIPC7 and initially the POV hat switch directions were registering as buttons 32-39. Now they no longer register as buttons but show up as an axis. Is there a way to select which to use? Thanks, Scott

As to what caused the failure in the first place, I think my son may have plugged in an Xbox360 controller and I launched FSX without removing it. I'm unclear why that would cause this cascade of failures, but it's the only thing I can think of. Scott

You asked the perfect question about FSX-SE seeing the controllers. Apparently it wasn't. I was dumbfounded by seeing a Windows Game Controller window (opened from Win10 settings) showing all my controllers. Next to it was a duplicate window opened through FSX-SE settings showing no controllers. Apparently this is an issue with some controller settings in the Steam client software. I followed the instructions in the thread linked below and the controllers are now detected in FSX-SE again and also FSUIPC. https://steamcommunity.com/app/314160/discussions/0/1742228532895992362/ Thanks for the help! Scott

Here it is... FSUIPC4.JoyScan.csv

It also didn't show any detected devices. It'll attach a copy when I get home tonight. Thanks, Scott

I had been successfully running FSX-SE and FSUIPC but then my controls stopped working. My yoke, trim wheel, throttles, and rudder all show up in the Windows game controller menu and function properly. However, FSUIPC doesn't detect them. Any ideas? FSUIPC4.log

Hi Pete, I'm using conditional buttons in my setup, and define an "unshifted" command (11=CP(-B,0)B,34,K123,8) in the [buttons] section. When I define a "shifted command" (15=CP(+B,0)B,34,C66301,0) in a profile, it overrides my unshifted command. If I redefine (11=CP(-B,0)B,34,K123,8) in the profile, both work properly. I just wanted to check that this is working as intended. I expect it is... Thanks, Scott

Thanks Pete, As a follow up question, are the button assignments under the [buttons] header applied to all aircraft, regardless of profile? This by itself would reduce the listings considerably. That's an interesting idea about the redundant assignments, I'll have to give that some consideration. Thanks again, Scott

Hi Pete, I'm working on cleaning up my button assignments in FSUIPC.ini. There are some button assignments common to all my aircraft. Then there are many buttons common to a class of aircraft (all props, for instance). Finally, there are a few buttons for a specific aircraft (such as a Grumman Goose or the Pitts). What I wonder is if I can assign the common buttons under the [buttons] section, then others under a [buttons.props] profile, using the names of all relevant aircraft, then a [buttons.goose] profile with only the Grumman Goose listed. Can an aircraft name, such as the goose, appear in two profiles? Thanks, Scott