FSUIPC 4.955 + Aerosoft Airbus doors problem identified

[Domobaby]

Hi Pete,

I have 4.955c installed. 

I had a problem with the Aerosoft Airbus cargo doors. When I hit the LSK on the MCDU to open a cargo door, all it ever does is toggle the main exit door. 

When I deleted FSUIPC4.DLL this problem disappeared. Unfortunately my P3DV3 cannot function very well without FSUIPC so I am in desperate need of it working.

Does this make any sense to you?

[spokes2112]

Pete is on vacation for a while, hopefully this will help. Why it works without FSUIPC is confusing, normally "flooding" of panel describes what's happening & Pete provided a fix starting from v4.93. Maybe that fix is keeping the AB doors from working correctly. Look for "TimeForSelect=" in your fsuipc.ini file (defaults to 2) also refer to this setting on pg.8 "FSUIPC 4 for Advanced Users".  Maybe  try a setting of zero to disable the function. 

[Domobaby]

Thanks for the reply Spokes. 

Thanks for giving me things to try. That's what I need. 

Someone has also mentioned for me to check I don't have two FSUIPC entries in the dll.xml....in the appdata and programdata locations.

Edited July 6, 2016 by Domobaby

[Domobaby]

No joy on this. 

It had defaulted to 4. I set to 0 with no change :(

When I click to open a cargo door the Front left door still opens

[Domobaby]

Also a point to note. All the MCDU door functions work grand with the PMDG. This is just a problem with the Aerosoft Airbus.

I had a look at the logging when I was pressing the cargo doors.

 

 163302 *** EVENT: Cntrl= 66389 (0x00010355), Param= 0 (0x00000000) TOGGLE_AIRCRAFT_EXIT

There are no 1,2,3,4 being controlled. Does this mean it is not distinguishing?

Edited July 6, 2016 by Domobaby

[Domobaby]

Hi all from the logs again. Does this mean anything in relation to door toggle?

 

   239789 Exception 3 "UNRECOGNIZED_ID", Ref 2891, Index param 3 on TransmitClientEvent, object=0, id=65540 (SELECT_3), data=0
   239789 Exception 3 "UNRECOGNIZED_ID", Ref 2891, Index param 3 on TransmitClientEvent, object=0, id=65540 (SELECT_3), data=0
   239789 Exception 3 "UNRECOGNIZED_ID", Ref 2891, Index param 3 on TransmitClientEvent, object=0, id=65540 (SELECT_3), data=0
   239820 Exception 3 "UNRECOGNIZED_ID", Ref 2891, Index param 3 on TransmitClientEvent, object=0, id=65540 (SELECT_3), data=0

[Pete Dowson]

15 hours ago, Domobaby said:

Also a point to note. All the MCDU door functions work grand with the PMDG. This is just a problem with the Aerosoft Airbus.

I had a look at the logging when I was pressing the cargo doors.

 

 163302 *** EVENT: Cntrl= 66389 (0x00010355), Param= 0 (0x00000000) TOGGLE_AIRCRAFT_EXIT

There are no 1,2,3,4 being controlled. Does this mean it is not distinguishing?

Toggle Aircraft Exit with no parameters, and no immediately following "SELECT" control, opens passenger doors only, exit 1 -- same as pressing Shift+E 1.  The SELECT controls, 1, 2, 3, 4 are by default assigned to the 1, 2, 3, 4 main keyboard keys.

You don't say how you are operating the doors, but if you are using keypresses Shift+E and 1, 2, 3 or 4, then FSUIPC will need the "time to select" parameter left default in order to ensure they are properly associated.  And you'll need to check that you don't have the 1, 2, 3, 4 keys assigned to other things.

Best to assign directly to Toggle Aircraft Exit with a parameter, 1, 2, 3, or 4, to control specific doors.

15 hours ago, Domobaby said:

Hi all from the logs again. Does this mean anything in relation to door toggle?

 

   239789 Exception 3 "UNRECOGNIZED_ID", Ref 2891, Index param 3 on TransmitClientEvent, object=0, id=65540 (SELECT_3), data=0
   239789 Exception 3 "UNRECOGNIZED_ID", Ref 2891, Index param 3 on TransmitClientEvent, object=0, id=65540 (SELECT_3), data=0
   239789 Exception 3 "UNRECOGNIZED_ID", Ref 2891, Index param 3 on TransmitClientEvent, object=0, id=65540 (SELECT_3), data=0
   239820 Exception 3 "UNRECOGNIZED_ID", Ref 2891, Index param 3 on TransmitClientEvent, object=0, id=65540 (SELECT_3), data=0

Aha! Yes!  The SELECT_1 to SELECT_4 controls are used to select the correct door(s). I've no idea how it becomes "UNRECOGNIZED" as it's a standard part of FS. See if  you can assign to  it in FS's assignments and whether it works that way. Or try pressing "3" in the keyboard whilst you have Event logging enabled.

Pete

 

[Domobaby]

Thanks for the reply Pete even though you are on leave.

It has been driving me crazy. These logs above have been generated from me pressing keys on the MCDU for the cargo doors on the Aerosoft Airbus. I do not encounter this problem with the PMDG MCDU door functions.

I have looked in the Aerosoft Airbus.cfg and there are indeed 4 parameters for aircraft exits. SELECT_3 as above controls the cargo doors I believe. Which makes sense because that is the button I was pressing on the MCDU whilst I was logging. 

I looked in the "P3D Controls" assignments and all I have is "SHIFT+E" to open close exits.

Perhaps the command to open the cargo door from the MCDU is not registering that this equates to SHIFT + E + 3 or something? Because I do not have it in the FSUIPC control assignments?

[Pete Dowson]

23 minutes ago, Domobaby said:

I looked in the "P3D Controls" assignments and all I have is "SHIFT+E" to open close exits.

Perhaps the command to open the cargo door from the MCDU is not registering that this equates to SHIFT + E + 3 or something? Because I do not have it in the FSUIPC control assignments?

The Event logging should show the events occurring no matter where they come from.

Which version of P3D are you using? Early version 3's had a problem with SELECT controls, I seem to remember. I can't check at present, away from my main system, but what happens when you use the keyboard Shift+E then 3? With and without FSUIPC? And with Event logging when with FSUIPC?

Pete

 

[Domobaby]

I had the problem with V3.2 then I updated the client to V3.3 still with the same problem. 

I also am at work so will have to run more tests this evening. Please note I have not changed any settings in FSUIPC ever. I have not configured any key presses, it is merely installed and registered.

1. When I performed SHIFT+E then 3 with FSUIPC and the Aerosoft Airbus // only the main exit opens (I have not tried this without FSUIPC)

2. I have tried to open the Cargo door through the MCDU without FSUIPC and I can confirm that the door works correctly. 

As mentioned above;

 239789 Exception 3 "UNRECOGNIZED_ID", Ref 2891, Index param 3 on TransmitClientEvent, object=0, id=65540 (SELECT_3), data=0
 

^This is what is logged when I try and open the cargo door on the MCDU. As you say something seems to be UNRECOGNIZED?

Really appreciate the support Pete. Such a small niggly problem but I know the solution is probably simple as well.

 

Regards,

Dom

 

 

[Domobaby]

UPDATE---

FSUIPC OFF

SHIFT+E then any key 1-4 only triggers main exit

Using MCDU to open cargo doors works

FSUIPC ON 

None of the above work

 

So the keys do not work regardless of FSUIPC on/off. But turning FSUIPC on some how defaults my input in the MCDU to only effect the front exit. 

[Domobaby]

Please see attached log from me trying to open cargo doors via the MCDU

FSUIPC4.log

[Pete Dowson]

You appear to have no Event logging enabled for the Logging, so it really isn't useful.

Also, please do not start  a new log --- by doing that you fail to provide essential start up information, like version numbers and log setting.

Pete