Maximum acceptable repeat rate depends on system performance/speed. Try to slow down the rate if it is possible but also check if some button is faulty (and I saw the same problem with axis programmed to generate a button press on CH device - there was a specific axis position where virtual button was pressed-released constantly with high rate).

Could this also apply to SimConnect commands issued by FSUIPC? I have two axes that control the RealAir Duke cowl flaps based on what zone they are in. Perhaps I have set that up incorrectly and am sending repeat commands.

Oski,I have exact your setup and have no problems.An Idea comes to my mind: could you mail me you standard.xml?C:UsersYourUsernameAppDataRoamingMicrosoftFSXControls

Hi Günter,the problem is that I'm not using a single standard.xml but several for each possible configuration setup such as 1 Throttle, 1 Prop, 1 Mixture, same for double throttles, then for individual settings per A/C type. But you pointed me towards a possible solution. When I look into those XML's I see much too many entires for one component - and not only for the Rudder pedals! It is my understanding that each component should be mentioned TWICE: once for normal ops and once for SLEW ops. As I see it I will have to set up these XML's from scratch. I have no clue who is responsible for those multi-entries - maybe a glitch of FSX ? anyway I will try to sort this out and report back.Oskar

Hi Oski,sent you a mail ...

Maximum acceptable repeat rate depends on system performance/speed. Try to slow down the rate if it is possible but also check if some button is faulty (and I saw the same problem with axis programmed to generate a button press on CH device - there was a specific axis position where virtual button was pressed-released constantly with high rate).

Here's what I logged up until Linda stopped responding to button inputs: FSUIPC logging bit cleared: 2Global shift set...[C] Control: 66377 - 0 TOGGLE_RECOGNITION_LIGHTS[C] Control: 66239 - 0 TOGGLE_BEACON_LIGHTSGlobal shift UNset...[C] Control: 66341 - 0 TOGGLE_ELECT_FUEL_PUMP2[C] Control: 66340 - 0 TOGGLE_ELECT_FUEL_PUMP1[C] Control: 66290 - 1 TOGGLE_ELECTRIC_VACUUM_PUMP[C] Control: 66516 - 0 FUEL_SELECTOR_2_OFF[C] Control: 66517 - 0 FUEL_SELECTOR_2_ALL[C] Control: 65955 - 0 FUEL_SELECTOR_OFF[C] Control: 65956 - 0 FUEL_SELECTOR_ALL[C] Control: 66301 - 0 TOGGLE_STARTER2[C] Control: 66301 - 0 TOGGLE_STARTER2[C] Control: 66364 - 0 TOGGLE_ALTERNATOR2[C] Control: 66300 - 0 TOGGLE_STARTER1[C] Control: 66300 - 0 TOGGLE_STARTER1[C] Control: 66363 - 0 TOGGLE_ALTERNATOR1Global shift set...[C] Control: 66379 - 0 TOGGLE_NAV_LIGHTSGlobal shift UNset...Global shift set...[C] Control: 66240 - 0 TOGGLE_TAXI_LIGHTSThen after LUA engine reload:[G] Developer mode OFF[iNIT] Loading...Aircraft: RealAir Beech Duke Turbine N710DS WAircraft module detected: RealAir B60TAivlaSoft library loaded...FSX standard library loaded...IAO library loaded...RealityXP library loaded...A2A MAP library loaded...[C] Control: 65716 - 0 VOR1_SET[C] Control: 66379 - 0 TOGGLE_NAV_LIGHTS[C] Control: 66239 - 0 TOGGLE_BEACON_LIGHTS[C] Control: 66240 - 0 TOGGLE_TAXI_LIGHTS[C] Control: 66058 - 0 PANEL_LIGHTS_SET[C] Control: 66377 - 0 TOGGLE_RECOGNITION_LIGHTS[C] Control: 66579 - 0 TOGGLE_CABIN_LIGHTSLoading a fallback joysticks config...Loading RealAir B60T joysticks config...Module: RealAir B60T Started...Ready to go, Captain!Global shift UNset...Global shift set...[C] Control: 65564 - 0 ATCGlobal shift UNset...Global shift set...[C] Control: 65564 - 0 ATC[C] Control: 65564 - 0 ATC[C] Control: 65564 - 0 ATC[C] Control: 65564 - 0 ATCGlobal shift UNset...[C] Control: 65752 - 0 PARKING_BRAKES FSUIPC logging bit set: 2WRITElua 735F, 1 bytes: 00 .WRITE0 7321, 60 bytes: 4C 47 3A 43 3A 32 00 00 00 00 00 00 00 00 00 00 LG:C:2..........00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................00 00 00 00 00 00 00 00 00 00 00 00 ............WRITE0 735F, 1 bytes: 01 .WRITElua 7321, 60 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................00 00 00 00 00 00 00 00 00 00 00 00 ............WRITElua 3400, 2 bytes: 00 04 .. FSUIPC logging bit cleared: 2 LVars watching list cleared... Offsets watching list cleared!It's interesting that I never issued these commands:[C] Control: 65716 - 0 VOR1_SET[C] Control: 66379 - 0 TOGGLE_NAV_LIGHTS[C] Control: 66239 - 0 TOGGLE_BEACON_LIGHTS[C] Control: 66240 - 0 TOGGLE_TAXI_LIGHTS[C] Control: 66058 - 0 PANEL_LIGHTS_SET[C] Control: 66377 - 0 TOGGLE_RECOGNITION_LIGHTS[C] Control: 66579 - 0 TOGGLE_CABIN_LIGHTSAnd then it did issue the commands I had requested after Linda stopped responding:Global shift UNset...Global shift set...[C] Control: 65564 - 0 ATCGlobal shift UNset...Global shift set...[C] Control: 65564 - 0 ATC[C] Control: 65564 - 0 ATC[C] Control: 65564 - 0 ATC[C] Control: 65564 - 0 ATCGlobal shift UNset...[C] Control: 65752 - 0 PARKING_BRAKESI have seen no evidence of jittering buttons or commands. It there additional logging you would suggest?Thanks,Scott

guenseli why is not possible to use "CTRL" or "SHIFT" as a keypress? When I try to record a keypress "CTRL" and "SHIFT" alone are not saved. Is a reason for this or is a bug?

CTRL and SHIFT are modifiers they cannot be used on their own in FSX or FS9, they are only allowed to be used in combination with another key.

Thanks Andy. I was asking because I've seen that with the Saitek profiler is it possible to define the "CRTL" or "SHIFT" to a button. My whish was to use the push-to-talk button in TeamSpeak and avoid to run the Saitek profiler only for this function but only Linda.

Surely Teamspeak allows you to change the key does it not?

Peter,there is a little trick to assign only CRTL and it can be done by editing FSUIPC.ini.Peter offers a list of codes in "FSUIPC4 for Advanced Users.pdf"With this codes you can program keypress.A button is programmed like thisFor keypresses: <Entry number> = <Action><Joy#>,<Btn#>,K<key>,<shifts>Here is one example (only CRTL send when pressing Button 0 with repeat on Joystick21=R2,0,K0,10K0 means the Key "Null" used for SHIFT, CRTL etc only. This value can only be used to press, but it could vot be detected, so you have to edit the ini-File.For "shifts" like Normal, SHIFT, CRTL, ALT, TAB etc. you have to add specific valuesadd1 for SHIFT2 for CRTL4 for TAB8 for Normal (Add this in anyway)16 for ALT32 for Windows Key64 Menue Keyexample Shift-Value for SHIFT CTRL ALT is 1 + 2 + 8 +16 = 27CTRL is 2 + 8 = 10BTW: This Manuals are worth to read :-)

I finally received my MCP Combo II. I am exploring now this piece of hardware. LINDA is really impressive a lot of function are there. I saw in LINDA that the USER display section looks like the MCP Combo I. In the MCP Combo II you will find the DME/CRS Knob beside the AUX (note : in the manual it is said AUX, but in test mode and in real adction this button act as Amber light). Under the DME/CRS Knob there is the Swap button. Under the Aux there is the Light button (which correspond to me for STBY in test mode or AUX contrarily to the manual). I don't see any mode button as on MCp Combo I.So ??? I do not know what to think.First - Are my Aux and Light button OK ?Second - should we expect a futur release of LINDA to take into account the modification on the user panel ?ThanksMichel

OK I think the answer is in this topic : MCPII ADFs for PMDG 737NGX. Sorry to do not saw it before.Michel

After a period of time the LINDA engine ceases to function ie buttons not working. Selecting to restart the engine from the GUI resolves the problem for a time.This appears to be a similar issue to that posted by Scott whom has never resolved the issue and returned to direct use of FSUIPC::

I've recently installed LINDA 1.1 over FSUIPC 4.749e. After running properly for a few minutes, joystick button commands will cease to have any effect in FSX. When I reload the LUA engine via the LINDA gui, all the commands that did not reach FSX take effect. So, if I was trying to zoom out, then turn on the autopilot, these actions would occur upon LUA engine reload without any additional inputs from me (like they were stored in a buffer).Setup notes:I run a VRInsight M-panel using the FSP2 (not FSUIPC)A few button commands are still controlled by FSUIPC-my CH Yoke hat switch is not fully detected, so I use FSUIPC (see my other post)The CH Yoke is not using the CH Control Manager, just the standard Win 7 x64 HID driversIt's interesting to note that my POV hat functions continue to work through FSUIPC when the LINDA commands stop working.No error messages display in the LINDA console when this occurs.Has anyone else seen this behavior or have any ideas what to try?Thanks,Scott

I noticed this on a Saitek X52 Pro, recently replaced with a Thrustmaster Warthog where the problem persists. Any pointers other than a possible 'jitter' button?

Having deleted the specific aircraft configuration and re-programmed the buttons all appears well.