Doors open error

[diegoafov]

*** Posted in Download Links - please post support requests in the main Support Forum ***

Hello,
For a year I have been experiencing a problem related to Fsuipc when opening the doors of the plane, I know that the error is due to fsuipc because if I uninstall fsuipc, the error disappears.

The error is that despite being able to open different doors of the airplane (for example the QW 787) through the menu or the keyboard commands, only the first door opens despite having selected any other.

Hope you can help me

Diego

Edited April 24, 2020 by John Dowson
Moved to support forum

[John Dowson]

Hi Diego,

first you posted in the 'Download Links' sub-forum. Please do not post there - all new support request should be posted in the main forum (or in the .net client dll, if the request is related to this dll).

You have also not provided enough information. What sim are you using? What version of FSUIPC? Which aircraft? If you are using FSUIPC for this, what have you assigned? Please post your ini and log files.

[diegoafov]

Hi John,

So sorry for posting in the wrong place, any way to move the post?. My simulator is Prepar3D v4.5, it happens with Fsuipc 5 (all versions) and Fsuipc 6 with all the aircrafts (default and payware) actually I dont have anything assigned in Fsuipc.

There are only a few exceptions, pmdg planes and aerosoft ones, I think they use their own custom doors comands. 

FSUIPC6.ini FSUIPC6.log

Edited April 24, 2020 by diegoafov

[Pete Dowson]

6 hours ago, diegoafov said:

For a year I have been experiencing a problem related to Fsuipc when opening the doors of the plane, I know that the error is due to fsuipc because if I uninstall fsuipc, the error disappears.

Excuse me for butting in, but why wait a year before reporting what you think is an FSUIPC error, and only report it just after a new version is released?

Such problems have been raised periodically, and are usually traced to other addons.

Useful threads to review are these

https://forum.simflight.com/topic/83826-shift-e-1234-only-opens-main-doors-in-p3dv3/?tab=comments#comment-506681

Note in that one the replies there are suggestions about the "TimeForSelect" parameter in FSUIPC. If you set that to 0 then FSUIPC will not attempt to provide any assistance against interfering controls from other add-ons. This may allow things to work better on some aircraft, but worse on others.

There's also a technique whereby instead of using separate key presses you assign in FSUIPC to Toggle Aircraft Exit and provide the 1,2,3 or 4 as the parameter. Probably more reliable is to assign to Offset Byte Togglebits with offset set as x3367 and the parameter set to 1, 2, 4 or 8 (or additions for more than one door at a time).

Other useful references:

 https://forum.simflight.com/topic/80422-opening-aircraft-doors/?tab=comments#comment-485890

https://forum.simflight.com/topic/86431-cargo-door-issues/?tab=comments#comment-523946

https://forum.simflight.com/topic/80167-doors-failing-to-open/?tab=comments#comment-484347

Pete

 

 

[diegoafov]

Hi Pete,
Sorry for the late reply, but he has been very busy these past few days. In response to your first question, I did not report the error because as I am studying the ATPL I only flew small aircraft to practice procedures, which only have one door and made me unaware of the error.

I have done everything that has been indicated to me, however nothing has solved the error, although fortunately thanks to it I have been able to at least locate the error (until now I did not know why it was) and that is when I have FSUIPC activated, at the moment opening door 2 of the plane for example the following occurs:

   779750 *** EVENT: Cntrl= 66389 (0x00010355), Param= 0 (0x00000000) TOGGLE_AIRCRAFT_EXIT
   779750 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
   779750 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
   779750 *** EVENT: Cntrl= 65539 (0x00010003), Param= 0 (0x00000000) SELECT_2

also happens with any other door:

   800031 *** EVENT: Cntrl= 66389 (0x00010355), Param= 0 (0x00000000) TOGGLE_AIRCRAFT_EXIT
   800031 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
   800031 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
   800031 *** EVENT: Cntrl= 65541 (0x00010005), Param= 0 (0x00000000) SELECT_4

 

I don't understand very well about this, but I think I understand that the error is that the command ATC_MENU_CLOSE blocks the select for each command to open the door. I am attaching the log so you can see it, the command is registered in line 828. I hope you can help me solve this problem.

Diego

 

Log (was to heavy to uploaded here):https://easyupload.io/v0jgte

[Pete Dowson]

7 hours ago, diegoafov said:

I did not report the error because as I am studying the ATPL I only flew small aircraft to practice procedures, which only have one door and made me unaware of the error.

But you said

"For a year I have been experiencing a problem related to Fsuipc when opening the doors of the plane"

so, you experienced an error 'related to fSUIPC', but did not know it was an error? that doesn't make sense.

7 hours ago, diegoafov said:

779750 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
 779750 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE

That's very strange. what add-ons are you running apart from FSUIPC?

Logs are text files and ZIP up very compactly. If a ZIPped log is too large then you need to demonstrate in a shorter session. i'm not ploughing through an immense file. Sorry.

7 hours ago, diegoafov said:

I have done everything that has been indicated to me

You've tried the assignments I indicated? If they don't work I need to see (short) logs showing that please.

Also check with a default aircraft.

Pete

 

[diegoafov]

1 hour ago, Pete Dowson said:

so, you experienced an error 'related to fSUIPC', but did not know it was an error? that doesn't make sense.

Yes, I knew it was a FSUIPC error because when I started experiencing it, I formatted the computer and retested one by one the addons that I had with a default airplane, the only addon that I had the problem with was FSUIPC.

 

2 hours ago, Pete Dowson said:

That's very strange. what add-ons are you running apart from FSUIPC?

I use addons like Accu-Feel from A2A, GSX (V1 and V2), Active Sky + ASCA, envtex, ORBX and the rest are scenery and airplanes.

 

I have remembered that with the first versions of FSUIPC for P3Dv4 I had no problem since I remember using the QW 787 without problems with the doors. I understand it's a very strange error but I greatly appreciated if you could help me.

Diego

[Pete Dowson]

3 hours ago, diegoafov said:

Yes, I knew it was a FSUIPC error because when I started experiencing it, I formatted the computer and retested one by one the addons that I had with a default airplane, the only addon that I had the problem with was FSUIPC.

Ah, so, you only worked out that it was related to FSUIPC recently?  And is that why you didn't report it a year ago?

3 hours ago, diegoafov said:

I use addons like Accu-Feel from A2A, GSX (V1 and V2), Active Sky + ASCA, envtex, ORBX and the rest are scenery and airplanes.

Can you try without GSX and Accu-Feel please?

Did you yet try the two alternatives I suggested? did you try changing the TimeForSelect parameter as I also suggested. Unless you do try what i ask I really can't see any way to help you!

3 hours ago, diegoafov said:

I have remembered that with the first versions of FSUIPC for P3Dv4 I had no problem since I remember using the QW 787 without problems with the doors.

But since then you use a different add-on aircraft with Accu-Feel. sorry, but we either need to find out what is making the difference, or whether an alternative way of assigning works. You need to try one or the other or both, because this sort of thing is certainly no different now in P3Dv4 nor in P3Dv5 installs of FSUIPC. You have something else changed.

Pete

 

[diegoafov]

12 hours ago, Pete Dowson said:

Ah, so, you only worked out that it was related to FSUIPC recently?  And is that why you didn't report it a year ago?

Exactly sorry if I didn't express myself correctly from the start.

12 hours ago, Pete Dowson said:

Can you try without GSX and Accu-Feel please?

I deactivate Accu-Feel, GSX and also SODE that I forgot to mention but nothing changed, I was still experiencing the same error, this time I tried with default aircraft.

12 hours ago, Pete Dowson said:

Did you yet try the two alternatives I suggested? did you try changing the TimeForSelect parameter as I also suggested. Unless you do try what i ask I really can't see any way to help you!

As you advised me I did, but I have not obtained any results either.

Honestly this error puzzles me more and more, is it possible to make FSUIP have no command assigned? I mean I wish that all he does is read data and parameters of the simulator (which is really what interests me). I think the problem is that although there is no command assigned to close the ATC menu in the simulator, FSUIPC does have it in its registry and that is why I have this error (it is an assumption because I do not understand this).

 

Because I do not understand this error considering that in case it was due to that I deleted the assignment to close the ATC menu, which did not solve anything, I also tried to assign a very different command to the one that open the doors.

779750 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
 779750 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE

Diego

[Pete Dowson]

32 minutes ago, diegoafov said:

is it possible to make FSUIP have no command assigned?

If you have no assignments, there is no command assigned. Same with just the default INI file.

Let me try to explain something.

With TimeForSelect=0 there is no assistance in allowing the "SELECT" commands (for selecting door or engine or whatever) to be associated with the previous command needing it (like Toggle Aircraft Exit) even with intervening controls (like in your case those ATC Menu ones, coming from who knows where).

With no key assignments in FSUIPC, the keys are not interfered with at all.

With TimeForSelect=4 (say), FSUIPC remembers commands like Toggle Aircraft Exit, and holds it for up to 4 seconds to see if it is followed in that time by a SELECT command. Then it sends both on to the Sim in one request (in what is called a SimConnect macro).

This facility was specifically added in order to deal with cases where the add-on aircraft (most notably the PMDG ones) were sending so many commands internally that the SELECT commands became detached from their "owner" and therefore did not operate.

This appears to be what you are experiencing.  So maybe you do really need TimeForSelect=4 or similar, though it would be nice to find out where those ATC commands are coming from.

Note that these commands do not need assigning within FSUIPC for this facility to operate. It detects them being issued the same as it has to for the logging facilities.

Pete

 

 

[Pete Dowson]

I've just loaded P3D4.5 on my test PC (my cockpit runs a completely different door system for ProSim's 738, where all doors, even emergency doors, have door controls).

I have no add-on aircraft in this installation to test with, so I transferred the FSX B738 over to P3D.

Using the default "shift E" key press to send the Toggle Aircraft Exit control, I get the same as you -- two "ATC MENU CLOSE" controls. Very strange -- I've no idea where these come from. There's even another after the Selection:

  1284590 *** EVENT: Cntrl= 66389 (0x00010355), Param= 0 (0x00000000) TOGGLE_AIRCRAFT_EXIT
  1284590 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
  1284590 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
  1284590 *** EVENT: Cntrl= 65539 (0x00010003), Param= 0 (0x00000000) SELECT_2
  1284590 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE

With the "TimeToSelect" parameter set to 0 these intervening controls stop any subsequent '2', '3' or '4' keypress (by default Slect 2, 3 or 4) from doing anything, so only Exit 1 opens.

BUT if I set the "TimeForSelect" parameter to 4, the selections do work. So FSUIPC is doing its job.

This is why the TimeForSelect parameter is defaulted to 4.

Please note that, whilst you can change the number of seconds for TimeForSelect in the FSUIPC 'Miscellaneous' menu in FSUIPC Options, you cannot change it to 0 or from 0 to another value in the menu. You have to change it in the INI file and restart P3D. This is because the operation of the facility requires a different Simconnect initialisation sequence.

However, I think it is far easier to assign, in FSUIPC, a key press (or combination) to Toggle Aircraft Exit with a parameter selecting which one.  Here I used Ctrl+Shift+2 for exit 2. That works fine (on the FSX 738 exit 2 operates both cargo doors). The log shows:

  1615874 FS Control Sent: Ctrl=66389, Param=2 TOGGLE_AIRCRAFT_EXIT
  1615874 .. This key is programmed in FSUIPC6 'Keys' options
  1615874 *** EVENT: Cntrl= 66389 (0x00010355), Param= 2 (0x00000002) TOGGLE_AIRCRAFT_EXIT

Note the parameter 2. It is that which selects door 2. And no spuriosly generated ATC_MENU_CLOSE controls!

So, in conclusion, I think that you may have TimeForSelect=0 in your INI (though that isn't defaulted), so check that.

Also, you say you have tested the assignment using a parameter as above. I'm sure that should work, so I think you must have made a mistake somewhere. Please try again, and then show me the Log and your INI file so I can check what you've done.

Pete

 

 

 

[diegoafov]

As you recommended, I have assigned through FSUIPC a command to open each of the doors, I assigned the command Ctrl + Shift + 2 for Toggle Aircraft Exit with parameter 2.  I have done it with the parameter "TimeForSelect "configured for 4, unfortunately it has not worked. Here is the log:

Running inside Prepar3D v4 on Windows 10
Module base=7FF9D0EF0000
  1265906 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
  1265906  READ0[8000]  3304,   4 bytes: 00 00 53 51                                      ..SQ
  1265906  READ0[8000]  3308,   4 bytes: 0C 00 DE FA                                      ....
  1266000  READ0[8000]  330C,   2 bytes: 06 00                                            ..
  1266656 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1
  1266656 .. Key not programmed -- passed on to FS
  1266813 KEYDOWN: VK=69, Waiting=0, Repeat=N, Shifts=1
  1266813 .. Key not programmed -- passed on to FS
  1266813 *** EVENT: Cntrl= 66389 (0x00010355), Param= 0 (0x00000000) TOGGLE_AIRCRAFT_EXIT
  1266813 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
  1266813 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
  1266969 KEYUP: VK=69, Waiting=0
  1267000 KEYUP: VK=16, Waiting=0
  1267125 KEYDOWN: VK=50, Waiting=0, Repeat=N, Shifts=0
  1267125 .. Key not programmed -- passed on to FS
  1267125 *** EVENT: Cntrl= 65539 (0x00010003), Param= 0 (0x00000000) SELECT_2
  1267281 KEYUP: VK=50, Waiting=0
  1272828 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1
  1272828 .. Key not programmed -- passed on to FS
  1273031 KEYDOWN: VK=69, Waiting=0, Repeat=N, Shifts=1
  1273031 .. Key not programmed -- passed on to FS
  1273031 *** EVENT: Cntrl= 66389 (0x00010355), Param= 0 (0x00000000) TOGGLE_AIRCRAFT_EXIT
  1273031 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
  1273031 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
  1273188 KEYUP: VK=69, Waiting=0
  1273219 KEYUP: VK=16, Waiting=0
  1273375 KEYDOWN: VK=50, Waiting=0, Repeat=N, Shifts=0
  1273375 .. Key not programmed -- passed on to FS
  1273375 *** EVENT: Cntrl= 65539 (0x00010003), Param= 0 (0x00000000) SELECT_2
  1273485 KEYUP: VK=50, Waiting=0
  1278422 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2
  1278422 .. Key not programmed -- passed on to FS
  1278610 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=3
  1278625 .. Key not programmed -- passed on to FS
  1279047 KEYDOWN: VK=50, Waiting=0, Repeat=N, Shifts=3
  1279047 FS Control Sent: Ctrl=66389, Param=2 TOGGLE_AIRCRAFT_EXIT
  1279047 .. This key is programmed in FSUIPC5 'Keys' options
  1279047 Exception 1 "ERROR", Ref 3387, Index param 2 on TransmitClientEvent, object=1, id=66389 (TOGGLE_AIRCRAFT_EXIT), data=2
  1279266 KEYUP: VK=50, Waiting=0
  1279344 KEYUP: VK=16, Waiting=0
  1279344 KEYUP: VK=17, Waiting=0
  1281031 KEYDOWN: VK=18, Waiting=0, Repeat=N, Shifts=4
  1281031 .. Key not programmed -- passed on to FS
  1281125 Deactivated for PID=2496, "explorer.exe"
  1281141 Lost focus to PID=2496, "explorer.exe"
 

[Pete Dowson]

3 hours ago, diegoafov said:

As you recommended, I have assigned through FSUIPC a command to open each of the doors, I assigned the command Ctrl + Shift + 2 for Toggle Aircraft Exit with parameter 2.  I have done it with the parameter "TimeForSelect "configured for 4, unfortunately it has not worked. Here is the log:

 

Looking at the log

  1279047 FS Control Sent: Ctrl=66389, Param=2 TOGGLE_AIRCRAFT_EXIT
  1279047 .. This key is programmed in FSUIPC5 'Keys' options
  1279047 Exception 1 "ERROR", Ref 3387, Index param 2 on TransmitClientEvent, object=1, id=66389 (TOGGLE_AIRCRAFT_EXIT), data=2

You seem to have a different error. There's no way you should get a Simconnect error like that with the parameter 2.

I saw you were using P3D 4.5.13. I'm still on 4.5.12.

The control with a parameter of 2 most certainly always worked with all the versions of FSX and P3D i used it with. I can try to test with 4.5.13 but it may not be for a day or two.

BTW I checked back, and the FSUIPC6.INI file you uploaded earlier had no TimeForSelect=4 parameter in it at all. Do you know how that went missing?

Could you try adding it please? I goes into the [General] section.

[LATER]

I can't get 4.5.13 now. It's been superseded by 4.5.14. I'll test with that.

Pete

 

 

[Pete Dowson]

9 hours ago, Pete Dowson said:

I can't get 4.5.13 now. It's been superseded by 4.5.14. I'll test with that.

Okay. Version 4.5.14 is okay too, no problems. here I assigned Ctrl+Shit+7 to "TOGGLE AIRCRAFT EXIT" with parameter 2. Here's the whole sequence including key presses and releases:

   774545 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2
   774545 .. Key not programmed -- passed on to FS
   774748 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=3
   774748 .. Key not programmed -- passed on to FS
   775232 KEYDOWN: VK=55, Waiting=0, Repeat=N, Shifts=3
   775232 FS Control Sent: Ctrl=66389, Param=2 TOGGLE_AIRCRAFT_EXIT
   775232 .. This key is programmed in FSUIPC6 'Keys' options
   775232 *** EVENT: Cntrl= 66389 (0x00010355), Param= 2 (0x00000002) TOGGLE_AIRCRAFT_EXIT
   775310 KEYUP: VK=55, Waiting=0, Shifts=3
   775731 KEYUP: VK=16, Waiting=0, Shifts=2
   775746 KEYUP: VK=17, Waiting=0, Shifts=0

In the B738 the cargo doors open or close using this assignment, so it works as intended. As you can see, there is no Error reported as there was in your test.  Now there may possibly be a bug in P3D version 4.5.13 which isn't in 4.5.12 or 4.5.14, but that seems highly unlikely to me. Therefore I suspect you have a corrupt P3D installation. Maybe you have some weather files which are corrupt -- that can have strange and unpreductable consequences, usually a CTD but not always. Se this thred:

You could also try P3D 4.5.14 of course.

I also re-checked the other method I suggested to you (and which I assume you didn't even try), using Offset 3367. This offset operates the doors directly, using SimConnect, without using any controls or events.  I used key press Ctrl+Shift+8 for this. Here's the sequence:

   781160 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2
   781160 .. Key not programmed -- passed on to FS
   781596 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=3
   781596 .. Key not programmed -- passed on to FS
   781908 KEYDOWN: VK=56, Waiting=0, Repeat=N, Shifts=3
   781908 IPC Offsets Control: Ctrl=x0D00, Length=1, Offset=3367, Param=x2
   781940 .. This key is programmed in FSUIPC6 'Keys' options
   782018 KEYUP: VK=56, Waiting=0, Shifts=3
   783125 KEYUP: VK=16, Waiting=0, Shifts=2
   783234 KEYUP: VK=17, Waiting=0, Shifts=0

That also operated the cargo doors.

Another advantage of using this direct method is that instead of using "Offset Byte Togglebits", as here, you could use "Offset Byte Setbits" to open or "Offset Byte Clearbits" to close doors. AND you can do this with multiple doors at the same time.

With this offset method, set offset x3367, with these  parameters:

1 = door 1
2 = door 2
4 = door 3
8 = door 4

Just add them for more than one at a time.

I think that's really all I can do for you.

Pete