controls Buttons control doesn't work from FSUIPC5 to P3DV4.4

[cleonard]

Hello Pete,

This is the first time I can not properly operate your module in 10 years of use. I can not find the problem.

1. I recently uninstalled P3DV3 and fully installed P3DV4 on another hard drive. Everything works well. I can use widefs with planG on my remote PC for example. But when FSUIPC is present in the directory "modules", I can not open the doors of my A320 anymore (same for all planes), even with the keyboard and controls at the MCDU. Only the main door works. I also lost the operation of the auto-start engine right and left on the 2 buttons of my throttle (saitek yoke system). Same for gear toggle : Yoke button works fine only with a direct assignment into P3D.

In fact, when installed, FSUIPC perfectly recognizes the button but nothing happens, while it works on the keyboard or P3D controls assignment. And worse, about the cargo door problem, I ask myself about many controls totally locked with their offsets invisibly forced.

FSUIPC and wideFS are Registered (with an old mail adress, but it doesn't mind I hope) and installed as administrator with Windows defender disabled (not sure at each test). Joystick assignment is Inside P3D... I didn't tried with FSUIPC: Perhaps I would. Of course all the drivers are upgraded. My fps average is up than 80.

2. Here is all the files you probably need for a diagnostic. But everything seems to be correct. 

3. I've noticed for exemple (Gear) :

offset 3360 has no effect when tried with the LINDA console or FSUIPC button affected to FScontrol: 

Watching new offset: 3360:UB:DEC = 0
btn 06A30D670-1=00000000000001000010>>>00000000000001000001
rl: 06A30D670-1=00000000000001000010>>>00000000000001000001 bit 19 2
pr: 06A30D670-1=00000000000001000010>>>00000000000001000001 bit 20
[EVNT] OnPress Button detected PR:06A30D670:20 ++++++++
[hHID] Button OnPress   06A30D670_20/G: 0
[hHID] Button Repeat Cancel 06A30D670_20/nil *****
[hHID] Button Repeat Cancel 06A30D670_20/nil *****
[hHID] Button Repeat Cancel 06A30D670_20/nil *****
[hHID] Action unshifted 06A30D670/20 press call: nil
[hHID] Button Execute   06A30D670/Gears_down
btn 06A30D670-1=00000000000001000001>>>00000000000001000010
pr: 06A30D670-1=00000000000001000001>>>00000000000001000010 bit 19
rl: 06A30D670-1=00000000000001000001>>>00000000000001000010 bit 20 2
[EVNT] OnPress Button detected PR:06A30D670:19 ++++++++
[hHID] Button OnPress   06A30D670_19/G: 0
[hHID] Button Repeat Cancel 06A30D670_19/nil *****
[hHID] Button Repeat Cancel 06A30D670_19/nil *****
[hHID] Button Repeat Cancel 06A30D670_19/nil *****
[hHID] Action unshifted 06A30D670/19 press call: nil
[hHID] Button Execute   06A30D670/Gears_up
 

And Inside FSUIPC log I can read :

 1482360 Button changed: bRef=0, Joy=2, Btn=19, Pressed
  1482360 [Buttons] 1=P2,19,C65570,0
  1482360 FS Control Sent: Ctrl=65570, Param=0 GEAR_TOGGLE
  1482703 Button changed: bRef=0, Joy=2, Btn=19, Released

Best regards.

Christophe LEONARD (LFRC)

 

 

FSUIPC5.ini

FSUIPC5 Install.log

[Pete Dowson]

On 1/30/2019 at 11:14 PM, cleonard said:

But when FSUIPC is present in the directory "modules", I can not open the doors of my A320 anymore (same for all planes), even with the keyboard and controls at the MCDU. Only the main door works. I also lost the operation of the auto-start engine right and left on the 2 buttons of my throttle (saitek yoke system). Same for gear toggle : Yoke button works fine only with a direct assignment into P3D.

Before trying to answer, I will pont out that you buried you support question in a reference subforum. If you want answers to specific questions about FSUIPC on your System you do need to post here, in the Support Forum. I moved it for you.

And all these things are assigned in FSUIPC? But they work with no FSUIPC present?

In this case they are all assigned in P3d, not FSUIPC. And if nothing is assigned in FSUIPC, and there are no FSUIPC applications or plug-ins telling it to do things, then it cannot possible interfere with any P3D operation. It is only sitting there receiving data from SimConnect and storing it into the offsets incase any application or plug-in wants to read it.

On 1/30/2019 at 11:14 PM, cleonard said:

Joystick assignment is Inside P3D.

You really should have controlllers disabled in P3D if you are assigning in FSUIPC. Otherwise P3D can still automatically assign functions to buttons on controllers it recognizes.

On 1/30/2019 at 11:14 PM, cleonard said:

offset 3360 has no effect when tried with the LINDA console or FSUIPC button affected to FScontrol: 

Offset 3360 has no FS control function. It is just the last 32 bits of the 288 bit area used to signal "virtual" buttons.

And LINDA is a very complex beast and uses many methods of which I have no idea and cannot support. I suggest that either you test assignments and FSUIPC in general without LINDA, or any of its lua plug-ins, OR seek support from the LINDA folks.

On 1/30/2019 at 11:14 PM, cleonard said:

1482360 Button changed: bRef=0, Joy=2, Btn=19, Pressed
  1482360 [Buttons] 1=P2,19,C65570,0
  1482360 FS Control Sent: Ctrl=65570, Param=0 GEAR_TOGGLE
  1482703 Button changed: bRef=0, Joy=2, Btn=19, Released

Best regards.

Christophe LEONARD (LFRC)

Why are all these lines crossed out? Am I not supposed to see them? The first part I don't know in any case. It isn't anything to do with FSUIPC. Looks like LINDA maybe?

Reading under the crossing out I see there a correct button recognition and the resulting assigned FS control being sent to P3D. The rest is up t P3D. If that control isn't working (it is sent to SimConnect in the normal correct way), then either your aircraft is broken, or another application is intercepting that control in SimConnect (a programmable facility in that part of P3D).

Rather than merely show such a small part of the log please next time append the Log as you have with the INI file. There is a lot more useful information there which you haven't provided!

In your INI file you have these two lines inserted into the [General] section:

!1=[Auto]
1=lua HIDSwitch

The !1= part makes that line a comment. Did you intend for "HIDSwitch.lua" to run automatically?

To test without LINDA you will need to move "ipcReady.lua" and "inda.exe" out of the Modules folder.

I see from the INI file that the GEAR TOGGLE assignment which was shown as working in your crossed out inclusion is in fact the ONLY button assignment. So your described button problems are all down to another add-on which is only operating when FSUIPC is installed -- maybe LINDA?

Pete

 

[cleonard]

Hello Pete, Thanks a lot for your answer.

I will take time to repair P3D and deinstall every file i'll have to. 

1- About the crossed lines : I wrote my message initially into the Notepad. Sorry for the mistake : the copy-paste was not correct. You were well advised to read the text anyway.

2- About lua HIDswitch : It was a test to scan the status of the buttons on Saitek pro flight switch panel. This program provided by Linda team is intended to Watch the 3360 offset values (saitek switches panel adress, as they say) and look at "FS window" changes according to the position of the buttons. In fact, I can see0x0000 only, without any change. I gave up this point.

3- As I said into my message, i totally reinstall P3D before sending my help message to you. That is the Reason why i've got only gear button assignment. It's a test. I did a try again following your advice and I also uninstalled all modules (LINDA, ASN, GSX). The test is negative. When assigned in P3D, gear is controlled. When removed in P3D and setted in FSUIPC, nothing happens.

4- doors : just curious. No assignment first. Just "D" key is setted into P3D controls (doors - select). If I press D1, D2, D3 etc... I just open/close main door (idem with many planes even carenado window with graphic commande of copilot or Passenger door). If I remove FSUIPC. all door control returns to normal. I can't explain that.

What I just tried : GSX + SODE + ASconnect & ASN for P3DV4 removal, CCleaner for registry cleaning, Nothing happens.

I totally empty  my "modules" folder and removed FSUIPC : all doors controls are avalaible again.

I reinstalled FSUIPC (restore from  and try controls from distant PC with "FS FLIGHT CONTROL external software (instructor post using simconnect). aicraft controls are working normally (all exit doors open and gear toggle). 

5- You'd like to look at my log file. I really hope that we'll find together what happens with FSUIPC.

With thanks for reading my very academic English coming from french scool.

Best regards.

Christophe

 

 

 

 

FSUIPC5.log

[Pete Dowson]

5 hours ago, cleonard said:

This program provided by Linda team is intended to Watch the 3360 offset values (saitek switches panel adress, as they say)

Well, use of that offset is reserved for virtual buttons, so needs an external driver or Lua plug-in to drive the bits. Who provides that? I'm sute Saitek don't -- they dn't use FSUIPC at all.

5 hours ago, cleonard said:

The test is negative. When assigned in P3D, gear is controlled. When removed in P3D and setted in FSUIPC, nothing happens.

ASN and GSX have no effect. LINDA installs Lua plug-ins, and it uses ipcReady.lua to load things, so you'd need to remove those too.

If you use the FSUIPC logging to log events then you'll see that using the assignment direct in P3D and in FSUIPC both send exactly the same control. You should test that with FSUIPC still installed, but with no assignments -- just remove or rename you FSUIPC5.INI file. Then it is absolutely sure that FSUIPC itself is not responsible for sending or interfering with anything. The Logging just logs what it sees. If strange things still happen you most certainly still have an FSUIPC application program doing things, or a Lua plug-in.

5 hours ago, cleonard said:

Just "D" key is setted into P3D controls (doors - select)

You changed this? It's normally Shift+E ("Toggle aircraft exit" control, being its proper name) followed by 1, 2, 3 or 4.

6 hours ago, cleonard said:

You'd like to look at my log file.

Well, that is more interesting, as it shows that the controls being sent by FSUIPC are rejected with a SimConnect Error. e.g.

113282 Exception 1 "ERROR", Ref 2811, Index param 2 on TransmitClientEvent, object=2, id=65570 (GEAR_TOGGLE), data=0

Now that's a puzzle.  But unfortunately you again omit vital data. See this line:

[Continuation log requested by user]

That means you pressed the "New Log" button, which starts a new log after renaming the main one, with more start-up information. So that start up data is missing. Please do NOT do this! Surely you had no reason to start a new log?

Please append the complete ORIGINAL log, do not start a new one!

Pete

 

[cleonard]

Ok Pete. I will try tomorow to retrieve the first log file and compress it. When i tried to send it this afternoon it was rejected by forum (too big). It's 1.25 am at the moment. Good night and everyone sleeps in my house...

best regards

Christophe

[Pete Dowson]

About the doors.  It occurred to me that FSUIPC does intercept and resend the aircraft exit control so it can prevent other controls making the 1,2,3 or 4 selection afterwards lose association.  If the re-sending of the control is rejected in the same way as those Gear controls, then this could explain your doors problem.

You can switch that facility off by finding this line in the INI file:

TimeForSelect=4

and setting 0 instead of 4.

The big puzzle, though, is why SimConnect is rejecting the controls.

Pete

 

[cleonard]

Good mornig Pete,

Following your advice I checked that Linda was totally erased from the program. I think the config is clean now.
However the problem persists and I still do not see anything in the log that could explain it to me.

This is the last files of the new test...

I deleted many messages into log file because size limit is 10kb into forum.

Deleted hundreds of this :

52735 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW
52813 *** EVENT: Cntrl= 66837 (0x00010515), Param= 0 (0x00000000) PRESSURIZATION_PRESSURE_ALT_DEC

I do not know the origin of this pressure_alt_dec event.

This is the first part...

 

 

 

FSUIPC5.1.log

[cleonard]

This is the second part... in text...

    71250 KEYDOWN: VK=113, Waiting=0, Repeat=N, Shifts=0
    71250 .. Key not programmed -- passed on to FS
    71266 *** EVENT: Cntrl= 66851 (0x00010523), Param= 0 (0x00000000) VIEW_CAMERA_SELECT_1
    71360 KEYUP: VK=113, Waiting=0
    73594 KEYDOWN: VK=112, Waiting=0, Repeat=N, Shifts=0
    73594 .. Key not programmed -- passed on to FS
    73594 *** EVENT: Cntrl= 66860 (0x0001052c), Param= 0 (0x00000000) VIEW_CAMERA_SELECT_0
    73688 KEYUP: VK=112, Waiting=0
    74485 KEYDOWN: VK=114, Waiting=0, Repeat=N, Shifts=0
    74485 .. Key not programmed -- passed on to FS
    74485 *** EVENT: Cntrl= 66852 (0x00010524), Param= 0 (0x00000000) VIEW_CAMERA_SELECT_2
    74594 KEYUP: VK=114, Waiting=0

    78703 KEYDOWN: VK=115, Waiting=0, Repeat=N, Shifts=0
    78703 .. Key not programmed -- passed on to FS
    78703 *** EVENT: Cntrl= 66853 (0x00010525), Param= 0 (0x00000000) VIEW_CAMERA_SELECT_3
    78813 KEYUP: VK=115, Waiting=0

    84110 KEYDOWN: VK=68, Waiting=0, Repeat=N, Shifts=0
    84110 .. Key not programmed -- passed on to FS
    84110 *** EVENT: Cntrl= 66389 (0x00010355), Param= 0 (0x00000000) TOGGLE_AIRCRAFT_EXIT
    84110 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
    84110 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
    84391 KEYDOWN: VK=51, Waiting=0, Repeat=N, Shifts=0
    84391 .. Key not programmed -- passed on to FS
    84391 *** EVENT: Cntrl= 65540 (0x00010004), Param= 0 (0x00000000) SELECT_3
    84688 KEYUP: VK=51, Waiting=0
    84781 KEYUP: VK=68, Waiting=0
    85235 KEYDOWN: VK=68, Waiting=0, Repeat=N, Shifts=0
    85235 .. Key not programmed -- passed on to FS
    85235 *** EVENT: Cntrl= 66389 (0x00010355), Param= 0 (0x00000000) TOGGLE_AIRCRAFT_EXIT
    85235 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
    85235 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
    85625 KEYDOWN: VK=52, Waiting=0, Repeat=N, Shifts=0
    85625 .. Key not programmed -- passed on to FS
    85625 *** EVENT: Cntrl= 65541 (0x00010005), Param= 0 (0x00000000) SELECT_4
    85844 KEYUP: VK=52, Waiting=0
    85891 KEYUP: VK=68, Waiting=0

    94953 KEYDOWN: VK=68, Waiting=0, Repeat=N, Shifts=0
    94953 .. Key not programmed -- passed on to FS
    94953 *** EVENT: Cntrl= 66389 (0x00010355), Param= 0 (0x00000000) TOGGLE_AIRCRAFT_EXIT
    94953 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
    94953 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
    95047 KEYUP: VK=68, Waiting=0
    99500 KEYDOWN: VK=68, Waiting=0, Repeat=N, Shifts=0
    99500 .. Key not programmed -- passed on to FS
    99500 *** EVENT: Cntrl= 66389 (0x00010355), Param= 0 (0x00000000) TOGGLE_AIRCRAFT_EXIT
    99500 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
    99500 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
    99985 KEYDOWN: VK=68, Waiting=0, Repeat=Y, Shifts=0
    99985 .. Key not programmed -- passed on to FS
    99985 *** EVENT: Cntrl= 66389 (0x00010355), Param= 0 (0x00000000) TOGGLE_AIRCRAFT_EXIT
    99985 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
    99985 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
   100000 KEYDOWN: VK=50, Waiting=0, Repeat=N, Shifts=0
   100000 .. Key not programmed -- passed on to FS
   100000 *** EVENT: Cntrl= 65539 (0x00010003), Param= 0 (0x00000000) SELECT_2
   100281 KEYUP: VK=50, Waiting=0
   100297 KEYUP: VK=68, Waiting=0
   103235 KEYDOWN: VK=68, Waiting=0, Repeat=N, Shifts=0
   103235 .. Key not programmed -- passed on to FS
   103235 *** EVENT: Cntrl= 66389 (0x00010355), Param= 0 (0x00000000) TOGGLE_AIRCRAFT_EXIT
   103235 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
   103235 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
   103563 KEYDOWN: VK=51, Waiting=0, Repeat=N, Shifts=0
   103563 .. Key not programmed -- passed on to FS
   103563 *** EVENT: Cntrl= 65540 (0x00010004), Param= 0 (0x00000000) SELECT_3
   103860 KEYUP: VK=51, Waiting=0
   103860 KEYUP: VK=68, Waiting=0
   109110 Button changed: bRef=0, Joy=2, Btn=0, Pressed
   109110 [Buttons] 3=P2,0,C65570,0
   109110 FS Control Sent: Ctrl=65570, Param=0 GEAR_TOGGLE
   109422 Button changed: bRef=0, Joy=2, Btn=0, Released
   109625 Button changed: bRef=0, Joy=2, Btn=0, Pressed
   109625 [Buttons] 3=P2,0,C65570,0
   109625 FS Control Sent: Ctrl=65570, Param=0 GEAR_TOGGLE
   109766 Button changed: bRef=0, Joy=2, Btn=0, Released
   110031 Button changed: bRef=0, Joy=2, Btn=0, Pressed
   110031 [Buttons] 3=P2,0,C65570,0
   110031 FS Control Sent: Ctrl=65570, Param=0 GEAR_TOGGLE
   110188 Button changed: bRef=0, Joy=2, Btn=0, Released
   110719 KEYDOWN: VK=115, Waiting=0, Repeat=N, Shifts=0
   110719 .. Key not programmed -- passed on to FS
   110719 *** EVENT: Cntrl= 66853 (0x00010525), Param= 0 (0x00000000) VIEW_CAMERA_SELECT_3
   110766 KEYUP: VK=115, Waiting=0
   110953 KEYDOWN: VK=113, Waiting=0, Repeat=N, Shifts=0
   110953 .. Key not programmed -- passed on to FS
   110969 *** EVENT: Cntrl= 66851 (0x00010523), Param= 0 (0x00000000) VIEW_CAMERA_SELECT_1
   111063 KEYUP: VK=113, Waiting=0
   111703 Button changed: bRef=0, Joy=2, Btn=0, Pressed
   111703 [Buttons] 3=P2,0,C65570,0
   111703 FS Control Sent: Ctrl=65570, Param=0 GEAR_TOGGLE
   111922 Button changed: bRef=0, Joy=2, Btn=0, Released
   112360 Button changed: bRef=0, Joy=2, Btn=0, Pressed
   112360 [Buttons] 3=P2,0,C65570,0
   112360 FS Control Sent: Ctrl=65570, Param=0 GEAR_TOGGLE
   112516 Button changed: bRef=0, Joy=2, Btn=0, Released
   112656 Button changed: bRef=0, Joy=2, Btn=0, Pressed
   112656 [Buttons] 3=P2,0,C65570,0
   112656 FS Control Sent: Ctrl=65570, Param=0 GEAR_TOGGLE
   112781 Button changed: bRef=0, Joy=2, Btn=0, Released
   113672 Button changed: bRef=0, Joy=2, Btn=18, Pressed
   113672 [Buttons] 2=P2,18,C66079,0
   113672 FS Control Sent: Ctrl=66079, Param=0 GEAR_UP
   113969 Button changed: bRef=0, Joy=2, Btn=18, Released
   114328 Button changed: bRef=0, Joy=2, Btn=19, Pressed
   114328 [Buttons] 1=P2,19,C66080,1
   114328 FS Control Sent: Ctrl=66080, Param=1 GEAR_DOWN
   114453 Button changed: bRef=0, Joy=2, Btn=19, Released
   114516 Button changed: bRef=0, Joy=2, Btn=19, Pressed
   114516 [Buttons] 1=P2,19,C66080,1
   114516 FS Control Sent: Ctrl=66080, Param=1 GEAR_DOWN
   114594 Button changed: bRef=0, Joy=2, Btn=19, Released
   118203 *** EVENT: Cntrl= 65732 (0x000100c4), Param= 0 (0x00000000) EXIT
   118313 Sim stopped: average frame rate for last 70 secs = 70.5 fps
   118313    Max AI traffic was 0 aircraft
   119547 === Closing session: waiting for DLLStop to be called ...
   129500 === DLLStop called ...
   129500 === Closing external processes we started ...
   130500 === About to kill any Lua plug-ins still running ...
   130641 === Closing global Lua thread
   131656 === About to kill my timers ...
   131860 === Restoring window procs ...
   131860 === Unloading libraries ...
   131860 === stopping other threads ...
   131860 === ... Button scanning ...
   131953 === ... Axis scanning ...
   132063 === Releasing joystick devices ...
   132063 === Freeing macro memory
   132063 === Removing any offset overrides
   132063 === Closing all WideFS threads
   133406 === Clearing any displays left
   133406 === NOTE: not calling SimConnect_Close ...
   133406 === AI slots deleted!
   133406 === Freeing button memory ...
   133406 === Deleting wxstationlist.bin file ...
   133406 === Closing my Windows ...
   133406 === Freeing FS libraries ...
   134406 === Closing devices ...
   134406 === Closing the Log ... Bye Bye! ...
   134406 System time = 03/02/2019 11:37:21, Simulator time = 11:36:20 (10:36Z)
   134406 *** FSUIPC log file being closed
Minimum frame rate was 50.8 fps, Maximum was 91.4 fps
Average frame rate for running time of 70 secs = 70.5 fps
Maximum AI traffic for session was 0 aircraft
Memory managed: 34 Allocs, 33 Freed
********* FSUIPC Log file closed ***********

 

[cleonard]

This is FSUIPC config :

[General]
UpdatedByVersion=5150
History=8XKEO6VG332XGHR38MEZ2
InitDelayDevicesToo=No
PMDG737offsets=Auto
PMDG747offsets=Auto
PMDG777offsets=Auto
Annotate=Yes
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
RestoreSimcWindows=No
FixMachSpeedBug=No
AutoScanDevices=Yes
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=No
DelayedMouseLookZoom=No
WideLuaGlobals=Yes
AxesWrongRange=No
TCASid=Flight
TCASrange=40,3
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
ThreadAffinityMask=x0
LuaAffinityMask=x0
InitDelay=0
GetNearestAirports=Yes
LogOptionProtect=Yes
TimeForLuaClosing=2
WeatherReadFactor=2
WeatherRewriteSeconds=1
TrafficStallTime=1
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
ComReadLoopTime=20
ControlsListBuild=27077
Console=No
ConsoleWindow=100,220,869,744
DebugLua=Yes
LogWrites=Yes
LogReads=Yes
LogEvents=Yes
LogLua=Yes
LogButtonsKeys=Yes
FSVersionUsed="Lockheed Martin® Prepar3D® v4",4.4.16.27077
SimConnectUsed=4.4.0.0

[Traffic Limiter]
AirportPreference=50
PlannedAirportsPreference=50
GroundPreference=50
NearerPreference=50
TargetFrameRate=0
TrafficLimit=0

[JoyNames]
AutoAssignLetters=No
0=Mad Catz Pro Flight Rudder Pedals
0.GUID={4FF8ED00-A42F-11E5-8007-444553540000}
2=Flight Yoke System
2.GUID={50D17D40-A430-11E5-8001-444553540000}

[JoystickCalibration]
RudderBlendLowest=1
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60

[Axes]
PollInterval=10
RangeRepeatRate=10
0=2X,256,F,65763,0,0,0 -{ TO SIM: AXIS_AILERONS_SET }-
1=2Z,256,F,65765,0,0,0 -{ TO SIM: AXIS_THROTTLE_SET }-

[LuaFiles]

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=P2,19,C66080,1  -{GEAR_DOWN}-
2=P2,18,C66079,0  -{GEAR_UP}-
3=P2,0,C65570,0  -{GEAR_TOGGLE}-

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No

[GPSout]
GPSoutEnabled=No

[GPSout2]
GPSoutEnabled=No

[WideServer]
WideFSenabled=Yes
AdvertiseService=1
Port=8002
Port2=9002

[Sounds]
Path=E:\Program Files\Lockheed Martin\Prepar3D v4\Sound\
Device1=Périphérique audio principal
Device2=SAMSUNG-0 (NVIDIA High Definition Audio)
Device3=PROJECTORS-C (NVIDIA High Definition Audio)
Device4=Realtek Digital Output (Realtek High Definition Audio)
Device5=Haut-parleurs (5- Philips SHG7980)
Device6=Haut-parleurs (4- Philips SHG7980)

[Monitor]
Display=1

[ClientNames]
1=FLIGHTSIM2

[cleonard]

I just noticed a new point, when selecting FSUIPC option "extras miscellany" :

 138015 LogOptions changed, now 60000000 0000001D
   138250 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
   141453 KEYDOWN: VK=71, Waiting=0, Repeat=N, Shifts=0
   141453 .. Key not programmed -- passed on to FS
   141453 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE
   141500 KEYUP: VK=71, Waiting=0
   142984 Button changed: bRef=0, Joy=2, Btn=0, Pressed
   142984 [Buttons] 3=P2,0,C65570,0
   142984 FS Control Sent: Ctrl=65570, Param=0 GEAR_TOGGLE
   142984 Exception 1 "ERROR", Ref 2805, Index param 2 on TransmitClientEvent, object=2, id=65570 (GEAR_TOGGLE), data=0
   143140 Button changed: bRef=0, Joy=2, Btn=0, Released
   156765 Button changed: bRef=0, Joy=2, Btn=18, Pressed
   156765 [Buttons] 2=P2,18,C66079,0
   156765 FS Control Sent: Ctrl=66079, Param=0 GEAR_UP
   156765 Exception 1 "ERROR", Ref 2818, Index param 2 on TransmitClientEvent, object=2, id=66079 (GEAR_UP), data=0
   157031 Button changed: bRef=0, Joy=2, Btn=18, Released
   157500 Button changed: bRef=0, Joy=2, Btn=19, Pressed
   157500 [Buttons] 1=P2,19,C66080,1
   157500 FS Control Sent: Ctrl=66080, Param=1 GEAR_DOWN
   157500 Exception 1 "ERROR", Ref 2820, Index param 2 on TransmitClientEvent, object=2, id=66080 (GEAR_DOWN), data=1
   157578 Button changed: bRef=0, Joy=2, Btn=19, Released
   163781 *** EVENT: Cntrl= 65732 (0x000100c4), Param= 0 (0x00000000) EXIT

The problem may be visible in this "exception" message...

[Pete Dowson]

1 hour ago, cleonard said:

I deleted many messages into log file because size limit is 10kb into forum.

Why not ZIP files up like most folks? With simple text files like these they Zip up really small!

1 hour ago, cleonard said:

Deleted hundreds of this :

52735 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW
52813 *** EVENT: Cntrl= 66837 (0x00010515), Param= 0 (0x00000000) PRESSURIZATION_PRESSURE_ALT_DEC

I do not know the origin of this pressure_alt_dec even

What about the "hundreds" of PAN_VIEW controls?  I don't see many of those.

This:

    17969 \\FLIGHTSIM\Prepar3D v4\SimObjects\Airplanes\Carenado DO228_100\DO228.air
    17985 ### The user object is 'Dornier Do228-212 CyberAvia'

is an add-on aircraft. Next time please test with a default P3D4 aircraft, because many add-on aircraft do some strange things themselves, like sending lots of controls (that's the reason for the "TimeToSelect" facility normally being enabled). I wouldn't be surprised if this aircraft is sending those controls. 

In the first part of the log I see that you used Gear controls through FSUIPC and  the Gear control was definitely sent to P3D4. (Of course if you were on the ground it would have no effect anyway).

You didn't have "Extras" selected for logging this time, so no SimConnect errors were reported (but I see that you did this later). Can you leave that set and re-run in case I can see Simconnect errors when FSUIPC requests Simconnect to register its ID numbers for the controld.

This part:

  103235 *** EVENT: Cntrl= 66389 (0x00010355), Param= 0 (0x00000000) TOGGLE_AIRCRAFT_EXIT
   103235 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
   103235 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE
   103563 KEYDOWN: VK=51, Waiting=0, Repeat=N, Shifts=0
   103563 .. Key not programmed -- passed on to FS
   103563 *** EVENT: Cntrl= 65540 (0x00010004), Param= 0 (0x00000000) SELECT_3
   103860 KEYUP: VK=51, Waiting=0
   103860 KEYUP: VK=68, Waiting=0

shows why, in this case, Aircraft Exit 3 didn't operate -- there were intervening controls before the '3'.  this is what the "TimeToSelect" facility in FSUIPC is intended to prevent. There was an earlier Exit attempt, for exit 1, which should have worked (though Exit 1 is defaulted in any case):

    63844 KEYDOWN: VK=68, Waiting=0, Repeat=N, Shifts=0
    63844 .. Key not programmed -- passed on to FS
    63844 *** EVENT: Cntrl= 66389 (0x00010355), Param= 0 (0x00000000) TOGGLE_AIRCRAFT_EXIT

    64141 KEYDOWN: VK=49, Waiting=0, Repeat=N, Shifts=0
    64141 .. Key not programmed -- passed on to FS
    64141 *** EVENT: Cntrl= 65538 (0x00010002), Param= 0 (0x00000000) SELECT_1

Or in this case did you delete lines beween those? Else I don't know why there's a space line. (I wish you'd just ZIP files and leave them intact).

1 hour ago, cleonard said:

This is FSUIPC config :
...
TimeForSelect=4

Ah, you didn't try setting that to 0 as I suggested!

1 hour ago, cleonard said:

The problem may be visible in this "exception" message...

Yes, as I stated in response to your earlier log, yesterday which also had "Extras" enabled. Do you not read all my replies? Please do so now.

You missed this:

  18 hours ago, cleonard said:

You'd like to look at my log file.

Well, that is more interesting, as it shows that the controls being sent by FSUIPC are rejected with a SimConnect Error. e.g.

113282 Exception 1 "ERROR", Ref 2811, Index param 2 on TransmitClientEvent, object=2, id=65570 (GEAR_TOGGLE), data=0

Now that's a puzzle.  But unfortunately you again omit vital data. See this line:

[Continuation log requested by user]

That means you pressed the "New Log" button, which starts a new log after renaming the main one, with more start-up information. So that start up data is missing. Please do NOT do this! Surely you had no reason to start a new log?

Please append the complete ORIGINAL log, do not start a new one!

and this:

About the doors.  It occurred to me that FSUIPC does intercept and resend the aircraft exit control so it can prevent other controls making the 1,2,3 or 4 selection afterwards lose association.  If the re-sending of the control is rejected in the same way as those Gear controls, then this could explain your doors problem.

You can switch that facility off by finding this line in the INI file:

TimeForSelect=4

and setting 0 instead of 4.

The big puzzle, though, is why SimConnect is rejecting the controls.

I need more logging! Please add these lines to the [General] section of the INI file:

Debug=Please
LogExtras=x400

Then do a re-run with a default aircraft. Keep the session short as the log will get huge very quickly. Just try your GEAR controls. No need to keep retrying.

Then supply the FULL log (Zipped), and also the "controls List for P3D4 ...txt", which you'll find in the FSUIPC documents subfolder. You can ZIP that too. It is generated from information supplied by P3D4 at run time and updated automatically on every P3D4 update.

One last question, for now. Is it possible that there are other add-on DLLs installed and still running?  These can be loaded via the P3D Add-Ons.xml methods or via a file called DLL.XML, with one of these in the P3d4 Appdata folder and another in the P3D ProgramData folder. You can stop all the AddOns.xml ones loading by renaming the Documents subfolder Prepar3 v4 Add-Ons, but this will not stop the others. FSUIPC is loaded by an entry in the AppData copy of DLL.XML.

Pete

 

 

 

 

[Pete Dowson]

Please note that if you read my reply above very soon after I posted it, i have revised the last part slightly to add parameters which will give me more logging.

Pete

 

[cleonard]

My apologies for not having read your lines closely enough.

OK, let's go… Nice to feel hope !

1- I send you a copy of "dll.xml" from appdata folder and from programdata folder + "Controls List for P3D4 Build 27077.txt"

2- I rename Prepar3D v4 Add-ons. Inside I can see "addon scenery" (some VFR freeware scenery) and "Orbx ObjectFlow 2" (which allows Orbx scenery to display dynamic content).

3- I change parameters Inside FSUIPC.ini (timeforselect, debug)

4- Tried a new test and zip all files you can look at...

For information: my niche next week to put me on my simulator is just Tuesday night (business trip then a few days).

Best regards.

Christophe.

 

dll_into appdata folder.xml

dll_into programdata folder.xml

Controls List for P3D4 Build 27077.zip

FSUIPC5.zip

[cleonard]

Just to notice : I never type a command or key called "ATC menu close" and Don't know were it comes from .

Christophe

 

[Pete Dowson]

15 hours ago, cleonard said:

1- I send you a copy of "dll.xml" from appdata folder and from programdata folder + "Controls List for P3D4 Build 27077.txt"

The only add-ons which it may be worth trying to disable are RAASPRO (in the ProgramData one), and CMeteoXml, whatever that is. Note that you have CMeteoXml loading twice, which can't be good. There are entries for it in both DLL.XML files.

To disable entries without having to remove them, just change the False to True in the <Disabled> line.

But before doing that let me check to see what could be causing these errors:

    14281 Exception 7 "NAME_UNRECOGNIZED", Ref 1146, Index param 2 on MapClientEventToSimEvent for "ENGINE", id=65554 [0x10012]
    14281 Exception 3 "UNRECOGNIZED_ID", Ref 1147, Index param 2 on Group 2 AddClientEventToNotificationGroup for "ENGINE", id=65554 [0x10012]
    14281 Exception 7 "NAME_UNRECOGNIZED", Ref 1149, Index param 2 on MapClientEventToSimEvent for "XPNDR", id=65556 [0x10014]
    14281 Exception 3 "UNRECOGNIZED_ID", Ref 1150, Index param 2 on Group 2 AddClientEventToNotificationGroup for "XPNDR", id=65556 [0x10014]
    14281 Exception 7 "NAME_UNRECOGNIZED", Ref 1152, Index param 2 on MapClientEventToSimEvent for "EGT", id=65558 [0x10016]
    14281 Exception 7 "NAME_UNRECOGNIZED", Ref 1153, Index param 2 on MapClientEventToSimEvent for "SMOKE_TOGGLE", id=65559 [0x10017]
    14281 Exception 7 "NAME_UNRECOGNIZED", Ref 1154, Index param 2 on MapClientEventToSimEvent for "STROBES_TOGGLE", id=65560 [0x10018]
    14281 Exception 7 "NAME_UNRECOGNIZED", Ref 1158, Index param 2 on MapClientEventToSimEvent for "ADF", id=65566 [0x1001E]
    14281 Exception 3 "UNRECOGNIZED_ID", Ref 1159, Index param 2 on Group 2 AddClientEventToNotificationGroup for "ADF", id=65566 [0x1001E]
    14281 Exception 7 "NAME_UNRECOGNIZED", Ref 1161, Index param 2 on MapClientEventToSimEvent for "HEADING_GYRO_SET", id=65568 [0x10020]
    14281 Exception 7 "NAME_UNRECOGNIZED", Ref 1162, Index param 2 on MapClientEventToSimEvent for "DME", id=65569 [0x10021]
    14281 Exception 3 "UNRECOGNIZED_ID", Ref 1163, Index param 2 on Group 2 AddClientEventToNotificationGroup for "DME", id=65569 [0x10021]
    14281 Exception 7 "NAME_UNRECOGNIZED", Ref 1164, Index param 2 on MapClientEventToSimEvent for "GEAR_TOGGLE", id=65570 [0x10022]
 etc

It is because the names haven't registered that the assignments fail later. The odd thing is that the Controls List is generated from the numbers and names provided BY P3D when requested, and that list is perfect.

I might have to add more logging, but this is looking suspiciously like a corrupt installation of P3D. Either that, or it is being corrupted in memory after loading. Now there is one things which I know can cause such corruption, with unpredictable consequences: bad weather files. The problem is that they are binary file and a read and processed without any chgecks being provided (yes, I have repeatedly asked L-M to fix this, to no avail so far).

So, another thing to try before I have to modify FSUIPC for extra logging: delete wxstationlist.bin from the P3D4 AppData folder (don't worry, another will be made), and delete, or move out (if you want to preserve them) all the .wx type files from the P3D4 Documents folder (where the flights are stored).

Let me know if that makes any difference.

Oh, there is one more thing also: a SimConnect log, so i can see if it is actually receiving the Name Registration requests. Because strnagely, though if they fail, an error should appear in that FSUIPC log, there are no such errors, It looks just as if all of those requests succeeded.

To get a Simconnect log please put this file into the P3D4 documents folder, naming it simConnect.ini:

[SimConnect]
level=Verbose
console=No
OutputDebugString=0
file=E:\Program Files\Lockheed Martin\Prepar3D v4\Modules\simconnect%u.log
file_next_index=1
file_max_index=9

This will create files named SimConnect1.log ... (etc).. in the Modules folder, with a LOT of lines!  Try it, and ZIP up the result for attachment. Again, keep the session VERY short, because the file will get huge!

If neither of these steps help or get enough information, then it will be more complicated.

Pete

 

 

[cleonard]

10 hours ago, Pete Dowson said:

I might have to add more logging, but this is looking suspiciously like a corrupt installation of P3D. Either that, or it is being corrupted in memory after loading.

The bug began when I tried to upgrade totally from P3D V4.3 to V4.4. I first thought that the problem was a bad cohabitation between the two simulators. (two different FS + FSUIPC into different directories "programfilex86" / "programfiles" but same disk). At the end I uninstalled all and only reinstalled P3DV4 and all planes & sceneries. I did it twice before asking some help. Probably not all files have been deleted.

10 hours ago, Pete Dowson said:

delete wxstationlist.bin from the P3D4 AppData folder (don't worry, another will be made), and delete, or move out (if you want to preserve them) all the .wx type files from the P3D4 Documents folder (where the flights are stored).

inside "Appdata>roaming>LM" I find "Prepar3D v3" directory. I delete it.

inside "Prepar3D v4" directory I can't find any wx file  I just can see "logbook" with bin type. I find weather.cfg Inside programdata folder. I think it doesn't matter.

deleted all wx files Inside documents directory

10 hours ago, Pete Dowson said:

This will create files named SimConnect1.log ... (etc).. in the Modules folder, with a LOT of lines! 

I send you files

 

10 hours ago, Pete Dowson said:

The only add-ons which it may be worth trying to disable are RAASPRO (in the ProgramData one), and CMeteoXml, whatever that is. Note that you have CMeteoXml loading twice, which can't be good.

Deleted these add-ons into dll.xml

damn, in spite of that there is no change.

I'm starting to think that I have to format disk and reinstall sim rather than waste time on you… Possible next week if you agree.

Christophe.

files.zip

[Pete Dowson]

18 minutes ago, cleonard said:

inside "Appdata>roaming>LM" I find "Prepar3D v3" directory. I delete it.

That's not relevant to P3D4 in any case. It would have had no effect either way.

18 minutes ago, cleonard said:

inside "Prepar3D v4" directory I can't find any wx file  I just can see "logbook" with bin type. I find weather.cfg Inside programdata folder. I think it doesn't matter.

If there's no wxstationlist.bin file then FSUIPC5 did its job and deleted that file at the end of the last sessio. It will be created again, so I'm now wondering if the mast copy, the once it is generated from, is corrupt. in case it is, please replace the copy in your main P3D4 folder, subfolder "weather", by the one attached.

In the SimConnect log file, I still see MANY add-on DLLs being loaded and run:

0.04501 DLL Loaded:  Path=".\CMeteoXml.dll"  Version="2.0.0.1"
0.04648 DLL already loaded:  Path=".\CMeteoXml.dll"
0.04650 DLL Load Failed:  Error=-2  Path=".\CMeteoXml.dll"

Didn't you disable these entries, one in each DLL.XML?

also, one other add-on seems to have slipped though:

0.04781 DLL Loaded:  Path="Captain_Sim\bin\cs.sound.dll"  Version="<Unknown>"

My worry is with that CMeteoXML one.  Do you know where it comes from, why it is on your PC?

The Simconnect log and the new FSUYIPC log do definitely confirm to me that something is badly wrong in P3D itself. These entries in the FSUIPC log:

     4594 Exception 7 "NAME_UNRECOGNIZED", Ref 1146, Index param 2 on MapClientEventToSimEvent for "ENGINE", id=65554 [0x10012]
     4594 Exception 7 "NAME_UNRECOGNIZED", Ref 1149, Index param 2 on MapClientEventToSimEvent for "XPNDR", id=65556 [0x10014]
     4594 Exception 7 "NAME_UNRECOGNIZED", Ref 1152, Index param 2 on MapClientEventToSimEvent for "EGT", id=65558 [0x10016]
     4594 Exception 7 "NAME_UNRECOGNIZED", Ref 1153, Index param 2 on MapClientEventToSimEvent for "SMOKE_TOGGLE", id=65559 [0x10017]
     4594 Exception 7 "NAME_UNRECOGNIZED", Ref 1154, Index param 2 on MapClientEventToSimEvent for "STROBES_TOGGLE", id=65560 [0x10018]
     4594 Exception 7 "NAME_UNRECOGNIZED", Ref 1158, Index param 2 on MapClientEventToSimEvent for "ADF", id=65566 [0x1001E]
     4610 Exception 7 "NAME_UNRECOGNIZED", Ref 1161, Index param 2 on MapClientEventToSimEvent for "HEADING_GYRO_SET", id=65568 [0x10020]
     4610 Exception 7 "NAME_UNRECOGNIZED", Ref 1162, Index param 2 on MapClientEventToSimEvent for "DME", id=65569 [0x10021]
     4610 Exception 7 "NAME_UNRECOGNIZED", Ref 1164, Index param 2 on MapClientEventToSimEvent for "GEAR_TOGGLE", id=65570 [0x10022]
     4610 Exception 7 "NAME_UNRECOGNIZED", Ref 1165, Index param 2 on MapClientEventToSimEvent for "ANTI_ICE_TOGGLE", id=65571 [0x10023]
   etc (loads of Exception 7's", 

are the conotrls which become unusable -- because Simconnect doesn't recognize them! Oddly, looking at the SimConnect log equivalent to this time:

> 4.66209 [131, 1128]MapClientEventToSimEvent:EventID=65537, EventName="DEMO_STOP"
> 4.66211 [131, 1129]MapClientEventToSimEvent:EventID=65538, EventName="SELECT_1"
> 4.66211 [132, 5]AddToDataDefinition:DefineID=-86050082, DatumName="IS SLEW ACTIVE", UnitsName="Bool", DatumType=1, fEpsilon=0.000000, DatumID=2
> 4.66212 [131, 1130]AddClientEventToNotificationGroup:GroupID=3, EventID=65538, bMaskable=1
> 4.66214 [131, 1131]MapClientEventToSimEvent:EventID=65539, EventName="SELECT_2"
> 4.66214 [131, 1132]AddClientEventToNotificationGroup:GroupID=3, EventID=65539, bMaskable=1
> 4.66215 [131, 1133]MapClientEventToSimEvent:EventID=65540, EventName="SELECT_3"
> 4.66216 [131, 1134]AddClientEventToNotificationGroup:GroupID=3, EventID=65540, bMaskable=1
> 4.66217 [131, 1135]MapClientEventToSimEvent:EventID=65541, EventName="SELECT_4"
> 4.66218 [131, 1136]AddClientEventToNotificationGroup:GroupID=3, EventID=65541, bMaskable=1
> 4.66218 [132, 6]AddToDataDefinition:DefineID=-86050082, DatumName="PLANE LATITUDE", UnitsName="degrees", DatumType=3, fEpsilon=0.000000, DatumID=3
> 4.66219 [131, 1137]MapClientEventToSimEvent:EventID=65543, EventName="DEMO_RECORD_1_SEC"
> 4.66220 [131, 1138]MapClientEventToSimEvent:EventID=65544, EventName="DEMO_RECORD_5_SEC"
> 4.66221 [131, 1139]MapClientEventToSimEvent:EventID=65546, EventName="MACRO_BEGIN"
> 4.66222 [131, 1140]MapClientEventToSimEvent:EventID=65547, EventName="MACRO_END"
> 4.66223 [131, 1141]MapClientEventToSimEvent:EventID=65548, EventName="MINUS"
> 4.66224 [131, 1142]MapClientEventToSimEvent:EventID=65549, EventName="PLUS"
> 4.66224 [131, 1143]MapClientEventToSimEvent:EventID=65550, EventName="ZOOM_1X"
> 4.66225 [131, 1144]MapClientEventToSimEvent:EventID=65552, EventName="SOUND_TOGGLE"
> 4.66226 [131, 1145]MapClientEventToSimEvent:EventID=65553, EventName="FULL_WINDOW_TOGGLE"
> 4.66227 [132, 7]AddToDataDefinition:DefineID=-86050082, DatumName="PLANE LONGITUDE", UnitsName="degrees", DatumType=3, fEpsilon=0.000000, DatumID=4
> 4.66228 [131, 1146]MapClientEventToSimEvent:EventID=65554, EventName="ENGINE"
< 4.66230 [131] >>>>>  EXCEPTION=7, SendID=1146, Index=2  <<<<<
> 4.66230 [132, 8]AddToDataDefinition:DefineID=-86050082, DatumName="PLANE ALTITUDE", UnitsName="feet", DatumType=3, fEpsilon=0.000000, DatumID=5
> 4.66231 [131, 1147]AddClientEventToNotificationGroup:GroupID=3, EventID=65554, bMaskable=1
< 4.66233 [131] >>>>>  EXCEPTION=3, SendID=1147, Index=2  <<<<<

> 4.66234 [131, 1148]MapClientEventToSimEvent:EventID=65555, EventName="SIM_RATE"
> 4.66235 [131, 1149]MapClientEventToSimEvent:EventID=65556, EventName="XPNDR"
< 4.66240 [131] >>>>>  EXCEPTION=7, SendID=1149, Index=2  <<<<<
etc

there are some that it does.  In the first 20 controls request, the only two to fail were ENGINE and XPNDR (in re).

I think a portion of, probably, "CONTROLS.DLL" (a part of P3D) has becomne overwritten in memory. I think that's where the table of these names is kept.

If you cannot remove all add-ons, then I would suggest doing complete uninstall and fresh install of P3D4. Then test it with no addons, Then FSUIPC5. Then start adding things one at a time, testing each time. It's really the only sure way.

Pete

 

wxstationlist.bin

[cleonard]

Okay, Pete, 

I tried with the new elements that you had the kindness to transmit to me.

Nothing helps. Thank you very much for your help.

I will reinstall P3D the week next Monday and keep you informed, of course.

Christophe.

[cleonard]

Good evening, Pete.
Here is the conclusion of the malfunction: I totally erased all the files P3D, cleaned the disk and reinstalled P3D then FSUIPC. No more anomaly found.
This was a file corruption during a bad uninstall - reinstall operation.

Thanks again for your analysis. It brings me a lot of experience back.

Best regards.

[Pete Dowson]

15 minutes ago, cleonard said:

Here is the conclusion of the malfunction: I totally erased all the files P3D, cleaned the disk and reinstalled P3D then FSUIPC. No more anomaly found.
This was a file corruption during a bad uninstall - reinstall operation.

Nice that you solved it. Thanks for letting us know.

Pete