Cargo Door Issues

[Frafty]

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).

 

[Pete Dowson]

7 hours ago, Frafty said:

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.

This could be significant:

7 hours ago, Frafty said:

I went into the .ini file, changed it to 0, and still no joy

You need to edit the INI file before starting P3D, because when you close P3D it will update the file.

Editing the value in the Miscellaneous tab should prevent setting 0, or changing it from 0 if set that way, because switching the option off or on has to be done during initialisation. I'll see what I can do about that. I may just remove the option from the Tab altogether. When added it wasn't envisaged that there'd ever be a need to turn it off (and there shouldn't be really).

Pete

 

[Frafty]

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?

[Pete Dowson]

18 minutes ago, Frafty said:

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.

Well, with that set off, FSUIPC really doesn't interfere with any of the controls needing a numeric value. Are you only getting the hift E results, nothing from 2, 3 or 4? Do you have other addons which may be sending lots of controls automatically (use FSUIPC Event logging (not axis) to check. That plug key logging should show what is happening with your key presses.

With control assignments instead I think you can give the numeric value as a parameter. you could try that?

Do you also get the problem with other keys taking a 1, 2, 3 or 4 selection, like Engine selection (just E then the numeric), and pushback (Shift P followed by 1 or 2 for direction). Because all these work fine for me, on two separate systems.

Pete

 

 

[Frafty]

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. 

[Pete Dowson]

19 hours ago, Frafty said:

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. 

Since it really isn't an issue for most folks' systems I think it is some interaction with something else you have also installed. The way i'd try to disabling all othe add-ons, checking FSUIPC, then adding them back one at a time, checking the Shift+E+2 actions every time.

THEN it would be worth doing the logging and enabling also the SimConnect logging, because whatever interaction is going on, it will be in there.

Pete

 

[Frafty]

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...

 

Quote

660484 *** EVENT: Cntrl= 66050 (0x00010202), Param= 1 (0x00000001) SMOKE_OFF
   660484 *** EVENT: Cntrl= 66050 (0x00010202), Param= 2 (0x00000002) SMOKE_OFF
   660484 *** EVENT: Cntrl= 66050 (0x00010202), Param= 3 (0x00000003) SMOKE_OFF
   660484 *** EVENT: Cntrl= 66050 (0x00010202), Param= 4 (0x00000004) SMOKE_OFF
   660593 *** EVENT: Cntrl= 65847 (0x00010137), Param= 0 (0x00000000) RADIO_VOR1_IDENT_SET
   660593 *** EVENT: Cntrl= 65848 (0x00010138), Param= 0 (0x00000000) RADIO_VOR2_IDENT_SET
   660593 *** EVENT: Cntrl= 65851 (0x0001013b), Param= 0 (0x00000000) RADIO_ADF_IDENT_SET
   660593 *** EVENT: Cntrl= 66560 (0x00010400), Param= 0 (0x00000000) RADIO_ADF2_IDENT_SET
   660593 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1
   660593 .. Key not programmed -- passed on to FS
   660703 *** EVENT: Cntrl= 66050 (0x00010202), Param= 1 (0x00000001) SMOKE_OFF
   660703 *** EVENT: Cntrl= 66050 (0x00010202), Param= 2 (0x00000002) SMOKE_OFF
   660718 *** EVENT: Cntrl= 66050 (0x00010202), Param= 3 (0x00000003) SMOKE_OFF
   660718 *** EVENT: Cntrl= 66050 (0x00010202), Param= 4 (0x00000004) SMOKE_OFF
   660796 KEYDOWN: VK=50, Waiting=0, Repeat=N, Shifts=1
   660796 .. Key not programmed -- passed on to FS
   660812 *** EVENT: Cntrl= 65907 (0x00010173), Param= 0 (0x00000000) PANEL_2
   660875 *** EVENT: Cntrl= 66478 (0x000103ae), Param= 0 (0x00000000) marker sound set
   660937 *** EVENT: Cntrl= 66050 (0x00010202), Param= 1 (0x00000001) SMOKE_OFF
   660937 *** EVENT: Cntrl= 66050 (0x00010202), Param= 2 (0x00000002) SMOKE_OFF
   660937 *** EVENT: Cntrl= 66050 (0x00010202), Param= 3 (0x00000003) SMOKE_OFF
   660937 *** EVENT: Cntrl= 66050 (0x00010202), Param= 4 (0x00000004) SMOKE_OFF
   660937 KEYUP: VK=50, Waiting=0
   660937 KEYUP: VK=16, Waiting=0

 

[Pete Dowson]

6 hours ago, Frafty said:

So I dug into the log. If I'm reading it correctly, it's not recognizing the input. I

If you mean Shift + E + 2, you pressed Shift + 2, no P..  Shift + 2 invokes PANEL_2

660593 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1
660593 .. Key not programmed -- passed on to FS
660796 KEYDOWN: VK=50, Waiting=0, Repeat=N, Shifts=1
660796 .. Key not programmed -- passed on to FS
660812 *** EVENT: Cntrl= 65907 (0x00010173), Param= 0 (0x00000000) PANEL_2
660937 KEYUP: VK=50, Waiting=0
660937 KEYUP: VK=16, Waiting=0

BTW, what is sending all those "SMOKE_OFF" controls? Whatever it is might be the cause of your problems.

I've been re-checking exactly what happens with Shift+E followed by a select 1-4, and if there are intervening controls, like all those SMOKE OFF ones, you probably do need TimeToSelect=4 left alone. That works fine here, on two separate systems, and with my Prosim 738 (version 1 with the older door system) I can most definitely and consistently choose which doors open -- SELECT 1 works both passenger doors, SELECT 2 works both service doors, SELECT 3 the aft cargo door, and SELECT 4 the forward one.

(The latest Prosim 738 has separate controls for each AND the emergency overwing 'doors', but that does it by using L:Vars instead, so needs a Lua plugin or L:Var macros. The plug-in is better as you can then also adjust the rate of opening/closing).

Pete

 

 

[Frafty]

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

[Pete Dowson]

17 hours ago, Frafty said:

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

Must have been some sort of corruption somewhere in the previous install. Glad you got it fixed.

Pete