Frafty

Fixed it, albeit it via a complete reinstall of p3d4. Bitter sweet. lol

So I dug into the log. If I'm reading it correctly, it's not recognizing the input. I uninstalled every aircraft (except for the Qw787 to test the panel), disabled everything add-on available in the P3D4 Add-On menu, yet nothing. This log clip is from testing the auxilary doors via the QW787 panel (like the video I included above) which I can only deduce is "panel 2", since I have to hit SHIFT+2 for that panel to open up in P3D4. I'm also assuming the "key not programmed, passing to FS" section of the log is referring to something not recognizing the actual button-to-door programming that's supposed to take place, so just defaults it to triggering the only door it recognizes? I can't figure out why though, as the keys are found when FSUIPC isn't there...

RE: the Feelthere 175/195, Shift+E+2 are the only doors I've ever attempted to open with FSUIPC installed. In terms of other addons, I can say it's plausible, but hard to know for sure, particularly because once FSUIPC is removed, all runs fine. Control assignments: I've actually, once removing FSUIPC, have been able to assign all the needed axis/controls via P3D4's native controls settings. There are a few VA applications (custom built ACARS) that I'm seeing run on FSUIPC as of now, so removing it renders some of those (one in particular) obsolete. Otherwise, I'd just remove FSUIPC all together if I didn't recognize any other ramifications of removing it. RE: other key combinations, yes. I'm imagining the same thing the other person in that support thread is now happening to me, for reasons I can't determine. I'm sure enabling the logging will show that P3D4 is not registering the key combinations. Ironically, despite QW787's having a panel of its own to operate all of its exterior doors, the unknown ghost error of FSUIPC (allegedly) seems to be affecting the way that individual panel operates, also. Once the module is removed, the QW787 door panel operates all doors without a problem, unlike the video I showed with FSUIPC installed. I've already reached out to QW787's support team, and they can't replicate the issue, of course. As of now, without completely uninstalling P3D4 and all components, which I'd hate to do, the solution is to remove FSUIPC completely. Only problem with that is then that renders some crucial applications (really, just ACARS), unusable.

I should be clear by saying I did the .ini adjustment while P3D was shut down as that's what you recommend in the other thread. I tried changing the value from 4 to 0, relaunched the module, recognized that it didn't change, shut down P3D, went into the .ini file and changed it to 0, relaunched, and realized it didn't work. Hoping that helps?

Hey there, So, here are the things you're aching to know, I'm sure: - Latest P3D v4.4 - Latest FSUIPC 5.15, and registered Issue: Doors won't open on aircraft, aside from main door, and aside from toggling anything BUT the main door. Video: https://www.useloom.com/share/adead33ecceb4f1db9db777bf5c242ee I found a thread on this exact issue somewhere else, where you actually were supporting the person with the issue. There was mention in there on how he removed the module, and all worked, and that's the case for me as well. Once I added the module back (re-installed 5.15), the error continued. When then module's not active (not in the folder) everything works as normal. This started suddenly when no major changes or installations were made to my system. This is error occurs with the QW787 for me, as well as the Feelthere 175/195 (SHIFT+E+2). The issue the person in the other thread was having was with the latter of the aircraft. In fact, here's the other thread in question. I tried the same thing mentioned in that thread: resetting the TimetoSelect to 0 in the module (however, wouldn't save and would return to "4" when opened; then I went into the .ini file, changed it to 0, and still no joy).