AdequatelySuitable

Thank you for the patch, I very much appreciate all the work. The altitude reporting selector works as intended and makes it possible to have the MCE FO accurately set the transponder controls for several phases of flight. If I have all three controllers (joystick, throttle quadrant, and rudder pedals) connected at startup, I am still receiving the 'joystick not found' error message. However, if I have only the joystick connected at startup, it works flawlessly. I can then plug the other two controllers in after MCE is running and no error message or other issues occur. Somehow the presence of any other controller at startup interferes with MCE's ability to recognize the VKB joystick.

I performed the tests as described and the other controllers (throttle quadrant and rudder pedals) work without issue when the ATC and mute buttons are assigned to them and everything is still plugged in. No error messages after restarting MCE. It would appear that the VKB joystick is the issue, as the error messages only appear when the ATC and mute functions are assigned to it while the other two controllers are connected. I will note that the VKB joystick works without issue (no error messages) when it is the only controller connected. Thank you again.

Is it possible to allow individual, separate voice control of the three boxed selectors? This would be the best way to customize transponder settings to individual preference. Just as the "TCAS alt range"/"TCAS altitude range" selector (THRT-ALL-ABV-BLW) is separately controllable via voice command, ideally the three boxed selectors would also be able to be set via voice independent of the other selectors. If individual control isn't feasible, then the particular transponder panel used in the Fenix A320 series is normally only set one of four ways in most airlines' operations. The AUTO position of the ATC STBY-AUTO-ON selector is rarely used. 1. Command "transponder off" or "transponder standby" should result in the boxed selectors moving to these positions: 2. Command "transponder on" should result in the boxed selectors moving to these positions: 3. Command "TCAS TA" should result in the boxed selectors moving to these positions: 4. Command "TCAS TA RA" should result in the boxed selectors moving to these positions:

None of my peripherals (joystick, throttles, or rudder) are wireless. They are all connected via USB. After further experimentation, it appears that the only time MCE starts without the previously mentioned error messages is when only the VKB joystick is connected (the rudder pedals and throttle quadrant are unplugged). If I have any combination of the rudder pedals and/or throttle connected at the same time as the joystick (rudder + joystick, throttle + joystick, or rudder + throttle + joystick), then I get the "joystick disconnected" error messages. I did discover that if I start MCE with only the joystick connected, then plug in the rudder pedals and throttle quadrant after MCE is open, I do not have any problems. After performing these steps, I find that if I attempt to modify the ATC joystick button via the UI (see screenshot below), MCE doesn't even recognize buttons I press on the throttle quadrant. It will only recognize different buttons that I press on the VKB joystick. For example, I can change to any other button on the joystick via the UI, but the button assignment window below doesn't recognize any inputs from the throttles. It seems to me as if MCE is "prioritizing" one peripheral over the others by MCE. Whenever two or all three peripherals are connected before starting MCE, the joystick seems to take a lower priority and is not recognized by MCE, resulting in the "joystick disconnected" errors. However, if I have only the joystick plugged in before starting MCE, then connect the other two peripherals after MCE is open, the joystick inputs are recognized and there are no error messages. As a side note, all three peripherals (joystick, rudder pedals, and throttle quadrant) all work together at the same time without issue in MSFS.

I confirmed that the joystick is connected prior to starting MCE, but I still get the error messages. On further investigation, I do not get the error messages when I unplug the other two peripherals (T-Pendular-Rudder and TCA Q-Eng 1&2). When only the VKB joystick is plugged in, there is no error and the assigned buttons work as they should. However, if I plug in either or both of the other two peripherals (T-Pendular-Rudder and/or TCA Q-Eng 1&2) while keeping the joystick plugged in, I do get the error messages. Up until a week ago or so, I had a different joystick (Thrustmaster) with buttons programmed for ATC and speech mute. The T-Pendular-Rudder and TCA Q-Eng 1&2 were plugged in at the same time as the old Thrustmaster joystick. I changed the button assignments for ATC and speech mute (and confirmed them in the config file) after plugging in the new VKB joystick. The only thing that has changed in my setup recently is the VKB joystick, so MCE must have an issue with having two of the "old" peripherals in use in combination with the new VKB joystick.

Thank you! I appreciate your efforts and I don't mean to be particular. I've found a discrepancy in "transponder off"/"transponder on" commands as follows: "Transponder off" / "Transponder standby" commands: As of latest patch: After commanding "transponder off" or "transponder standby," the ATC (transponder) STBY-AUTO-ON selector is set to AUTO. In reality, the ATC selector should be in STBY as shown below. Desired: "Transponder on" command: As of latest patch: Same as above as of latest patch image. There appears to be no difference in result when asking for "transponder standby" (or "transponder off") and "transponder on." Desired: The ATC/transponder selector should be ON, the ALT RPTG selector should be ON, and the TCAS selector should be STBY. This turns the transponder on, but leaves TCAS (TA or TA/RA) off so that the aircraft can broadcast transponder information to airport surface surveillance systems and ADS-B out without receiving traffic advisories or resolution advisories. This is the equivalent of XPNDR mode on transponder control panels with that option. "TCAS TA" / "TCAS TA RA" commands: As of latest patch / desired: This is correct as is. The screenshot is of a "TCAS TA RA" command, but commanding "TCAS TA" or similar also works as intended, with the TCAS selector moving to TA. One solution is allowing individual control of the five selectors on the TCAS panel. If the current method remains in place, there are four states the transponder panel is normally set up for: Transponder standby/off ATC/transponder selector STBY | ALT RPTG selector OFF | TCAS selector STBY Transponder on (equivalent to XPNDR mode) ATC/transponder selector ON | ALT RPTG selector ON | TCAS selector STBY TCAS TA only ATC/transponder selector ON | ALT RPTG selector ON | TCAS selector TA TCAS TA/RA ATC/transponder selector ON | ALT RPTG selector ON | TCAS selector TA/RA Ideally, there would be a distinction between "TCAS" and "transponder" in the available commands. "TCAS" only refers to the STBY-TA-TA/RA selector in the bottom right corner. "Transponder" refers to the STBY-AUTO-ON selector in the top left corner and the ALT RPTG selector in the bottom left corner.

I recently began using a VKB Gladiator NXT EVO joystick. Drivers and firmware are confirmed up-to-date, it is calibrated, and it works without issue in MSFS. MCE recognizes the controller and the button via the MCE UI when I set buttons for ATC ([GAMEPAD] in mce.ini) and speech mute ([HARD_MUTE_JOY] in mce.ini). The following are present in mce.ini: [GAMEPAD] JoyManID= VKBsim Gladiator EVO L JoyProdID= VKBsim Gladiator EVO L JoyButton=22 UseWithVoxATC=1 [HARD_MUTE_JOY] JoyManID=VKBsim Gladiator EVO L JoyProdID=VKBsim Gladiator EVO L JoyButton=4 However, I get the follow error messages when opening MCE and when attempting to modify the joystick button assignments via the UI: I have confirmed that the joystick is connected to the computer and is working. Button inputs are recognized in the joystick's configurator software and in the Control Panel USB game controller menu. I have also done a series of restarts and even uninstalled/reinstalled MCE (via Add/Remove Programs). I have other controllers connected (throttle and rudder pedals), but none of them have buttons assigned to MCE and they aren't present in mce.ini. Here is the Game Controllers menu from Control Panel:

MSFS edition

Thank you!

Thank you, I appreciate the response! I checked the entire list in "Edit Script Commands" and I don't believe an action exists to control just the STBY-TA-TA/RA selector. Any variation of "transponder on", "TCAS on", etc. sets both the transponder (STBY-AUTO-ON) to ON and the TCAS mode (STBY-TA-TA/RA) to TA/RA. The PMDG 737 has one combined transponder/TCAS selector that has an XPNDR position and an associated MCE action. That activates the transponder for taxiing, but keeps TCAS (TA or TA/RA) in standby so that traffic alerts aren't received on the ground. Since the Fenix A320 has separate transponder and TCAS selectors, there is no singular setting that MCE can command that matches the above. Instead, it is necessary to select the transponder to ON and the TCAS to STBY for taxi. Is it possible for MCE to allow independent control of the TCAS STBY-TA-TA/RA selector?

The A320 (I'm using Fenix) doesn't appear to have any available commands to control just the TCAS STBY-TA-TA/RA selector. The existing commands, such as "set transponder on" and "turn on TCAS" move several switches at once, including ATC to ON, ALT RPTG to ON, and TCAS to TA/RA. While taxiing, standard procedure is to turn the transponder and altitude reporting ON while leaving TCAS (TA or TA/RA) off/in standby. TA/RA is only turned on while lining up on the runway. The currently available commands are "all or nothing" in that the transponder and TCAS are either turned on in TA or TA/RA mode, or turned off in standby mode. Is it possible to separately control the transponder (STBY-AUTO-ON), ALT RPTG (OFF-ON), and TCAS (STBY-TA-TA/RA) switches on the Fenix transponder panel?