Hi there

 

I have the relatively new Toliss A330-900 NEO.  Which has a co-pilot now.  I am not getting take-off call outs at all.

 

Thanks 

Dudley

On 11/18/2024 at 12:13 PM, dbrooke said:

Hi there

 

I have the relatively new Toliss A330-900 NEO.  Which has a co-pilot now.  I am not getting take-off call outs at all.

 

Thanks 

Dudley

There are conditions that need to be met before Vspeed callouts are made, one of them is the FO seeing that you are in takeoff phase.

To determine that, MCE looks at a number of parameters, among them power levers positions.

The A330 isn't fully supported yet (untested).

Since it uses more or less same gauges as the A340, right now FO is seeing it as A340 (with expected 4 engines), so I guess he's not seeing the other ones.

Should have been set to see it as the A320, however, the hydraulic panel is different between A320 & A330 hence the choice of A340 instead.

The xmcTolissA3X.dll in \X-Plane\MCE dlls\64 Bit\ folder will need to be updated to differentiate between A340 & A330 so it can report correct flight phase depending on which Toliss plane is loaded. Will post new dll as soon as possible.

 

On 11/19/2024 at 3:18 PM, FS++ said:

There are conditions that need to be met before Vspeed callouts are made, one of them is the FO seeing that you are in takeoff phase.

To determine that, MCE looks at a number of parameters, among them power levers positions.

The A330 isn't fully supported yet (untested).

Since it uses more or less same gauges as the A340, right now FO is seeing it as A340 (with expected 4 engines), so I guess he's not seeing the other ones.

Should have been set to see it as the A320, however, the hydraulic panel is different between A320 & A330 hence the choice of A340 instead.

The xmcTolissA3X.dll in \X-Plane\MCE dlls\64 Bit\ folder will need to be updated to differentiate between A340 & A330 so it can report correct flight phase depending on which Toliss plane is loaded. Will post new dll as soon as possible.

 

Thanks very much, watching the PFD while taking off tends to make me wobble a bit. Also co-pilot can't engage reverse thrust like the A320.

Edited December 3, 20241 yr by dbrooke

Hi there, me again.  I have just upgraded my Toliss A321 to version V1p7, This isn't recognised as a Toliss Airbus.  I suspect pretty much the same has happened as that with the A330, I hope it is an easy fix.  1.p7 has some nice upgrades.

 

Best

 

Dudley

On 12/15/2024 at 9:23 AM, dbrooke said:

Hi there, me again.  I have just upgraded my Toliss A321 to version V1p7, This isn't recognised as a Toliss Airbus.  I suspect pretty much the same has happened as that with the A330, I hope it is an easy fix.  1.p7 has some nice upgrades.

 

Best

 

Dudley

Please go to C;\Users\your_user_name\AppData\Roaming\Multi Crew X-Plane\ folder and open "xpmce.ini in Notepad.

Change "Debug=0" to "Debug=1

With the new plane loaded, restart MCE and you should get a dialog box showing some information related to detected plane.

Post a screenshot or send it to support. Thanks

Sorry for the delay, I had a hardware problem, I am back now 😉  here is a screenshot of the 321. Strange thing is all the other 32x worked out of the box.   Another problen for the A339 is the lack of callouts on take off.  I hope you are keeping well, and have a Good New Year.

 

Best

 

Dudley

I can't see how to upload a picture 😹

 

Spoiler

 

 

Edited December 31, 20241 yr by dbrooke

Another problem is the Co-Pilot can no longer set reverse thrust. He's never able to cancel it as far as I know.

 

Happy new year 

 

Dudley.

Hi there, any progress with this.?

 

Thanks

 

Dudley

2 hours ago, dbrooke said:

Hi there, any progress with this.?

 

Thanks

 

Dudley

Still  not seeing screenshot regarding aircraft that wasn't identified. Yu have to set "Debug=1" in xpmce.ini, then run MCE with the relevant plane.

Send it toi support if you don't know how to post here. Thanks

 

Hi @FS++

I am aware that the A380 was just recently added to the supported plane’s list. So I thought I will try and make my own scripts for it. Turns out, there is a lot of things I can’t script based on the available commands.dat file. I tried to follow the official A380 FCOM to get the FO to accomplish the electrical power procedure but the program is not aware of the individual batteries the 380 has.

Let me put in a list so it’s easy to see what’s missing or not working:

- battery one (it only can turn BAT 1 on if “master battery” command is used but that turns on BAT 2 too)
- essential battery (missing)
- external power one, two, three, four (missing) - “ground power on” doesn’t do anything, and the A380 has a sequence in which external power has to be turned on - so it’d be better to have command “external power one on”, “external power two on” etc.
- engine master one, two, three, four (missing)
- ecam display electrical (wrong) - it displays the hydraulics page instead.
- ecam display hydraulic (wrong) - it displays the door page instead.
- ecam display engine (wrong) - it displays the bleed page instead.
- ecam display bleed (wrong) - it displays the apu page instead.
- ecam display apu (wrong) - it displays the elec dc page instead.
- ecam display aircon (wrong) - it displays the fuel page instead.
- ecam display fuel (wrong) - it displays the press page instead.
- ecam display pressurization (wrong) - it displays the cond page instead.
- ecam display doors (wrong) - it displays the wheel page instead.
- ecam display wheels (wrong) - it displays the flight controls page instead.
- ecam display flight controls (wrong) - it displays the C/B page instead.
So to sum up: all the ECAM pages are displayed wrong.

- “nav lights on” command (wrong) - it turns on both NAV lights & Logo lights to ON.
- cockpit door open & close (missing)

I do have the latest version, full reinstall.

So far these are the items I found not to be working, or working incorrectly. I wonder if these could be fixed.

Thank you.

Edited January 21, 20251 yr by Balint Szarka

15 hours ago, Balint Szarka said:

Hi @FS++

I am aware that the A380 was just recently added to the supported plane’s list. So I thought I will try and make my own scripts for it. Turns out, there is a lot of things I can’t script based on the available commands.dat file. I tried to follow the official A380 FCOM to get the FO to accomplish the electrical power procedure but the program is not aware of the individual batteries the 380 has.

Let me put in a list so it’s easy to see what’s missing or not working:

- battery one (it only can turn BAT 1 on if “master battery” command is used but that turns on BAT 2 too).

Will be sorted.

- essential battery (missing)

Will have a separate set of speech commands for this item

- external power one, two, three, four (missing) - “ground power on” doesn’t do anything, and the A380 has a sequence in which external power has to be turned on - so it’d be better to have command “external power one on”, “external power two on” etc.

Probably because the initial implementation which was done for the stable edition responded to different events. We have since moved to supporting the evolving Developer edition . FO will be able to handle the 4 GPU switches and switch them in sequence 1, 2, 3, 4 with a delay in-between.

- engine master one, two, three, four (missing)

When a speech command isn't listed in the "Available_Commands.dat" it doesn't always mean it doesn't exist. for instance, dialing commands aren't listed because they cannot be scripted. Others missing just due to oversight.

Here are some of the built-in commands you could use. And there are many. Listing only some  for engine 1

start master engine number one open

close start master engine one

start master number one on

start master one set to off

 

Remember, you can always teach the FO to accept your personal speech by tying your custom command to a built-in one. Having said that and considering there are 4 engines requiring 8 separate custom commands, it makes more sense for us to just tweak the speech Grammars (cfg files in \CandC\ folder) to include the speech variations you listed. 

We've been doing this for more than a decade and as you can see, despite thousands of tweaks over the years, there is the occasional scenario where the user speaks a perfectly acceptable command and it's not recognized because of the grammar we submit to the speech engine, not due to accent or things like that. Tweaking speech grammars isn't just "adding sentences".

Flightsim Speech recognition sim wouldn't be fun if the user has to pause and think what the hell he needs to say to get things done. It's our job to figure it out. 

- ecam display electrical (wrong) - it displays the hydraulics page instead.
- ecam display hydraulic (wrong) - it displays the door page instead.
- ecam display engine (wrong) - it displays the bleed page instead.
- ecam display bleed (wrong) - it displays the apu page instead.
- ecam display apu (wrong) - it displays the elec dc page instead.
- ecam display aircon (wrong) - it displays the fuel page instead.
- ecam display fuel (wrong) - it displays the press page instead.
- ecam display pressurization (wrong) - it displays the cond page instead.
- ecam display doors (wrong) - it displays the wheel page instead.
- ecam display wheels (wrong) - it displays the flight controls page instead.
- ecam display flight controls (wrong) - it displays the C/B page instead.
So to sum up: all the ECAM pages are displayed wrong.

Mix-up confirmed with pages IDs. Already sorted today. Thanks for that

- “nav lights on” command (wrong) - it turns on both NAV lights & Logo lights to ON.

Good catch, indeed, the plane has separate switches for these. Already sorted here

- cockpit door open & close (missing)

Normally we don't bother with this because it has to be applied to all supported planes. We'll see if it's worth it

I do have the latest version, full reinstall.

So far these are the items I found not to be working, or working incorrectly. I wonder if these could be fixed.

Thank you.

You're welcome. Expect a patch by tomorrow evening.

 

Thanks for the report

Answers embedded above.

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?

19 hours ago, AdequatelySuitable said:

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?

Just to clarify the built-in commands. Words between parenthesis are optional

For transponder mode...

transponder (mode) (set to) standby

transponder (mode) (set to) to ta

transponder (mode) (set to) to tara

"set to" could also be "switch to" or "to"

For Tcas range...

tcas range to threat

tcas range set to all

tcas range switch to above

tcas range set to below.

Alt report switch is never handled.

The only switch that is automatically handled is  STBY-AUTO-ON isn't off when the mode is higher than standby.

If you go to the command input screen, you should see a listbox containing many of the built-in speech commands that apply to the currently loaded plane. Just a matter of picking up the suitable one. No need to look-up the documentation.

If you happen to be using personal verbiage that the crew doesn't seem to react to, see this thread on how you can educate him to understand personal speech.

Essentially, create the command you want and tie it to the one the FO is trained to react to.

 

 

 

5 hours ago, FS++ said:

Just to clarify the built-in commands. Words between parenthesis are optional

For transponder mode...

transponder (mode) (set to) standby

transponder (mode) (set to) to ta

transponder (mode) (set to) to tara

"set to" could also be "switch to" or "to"

For Tcas range...

tcas range to threat

tcas range set to all

tcas range switch to above

tcas range set to below.

Alt report switch is never handled.

The only switch that is automatically handled is  STBY-AUTO-ON isn't off when the mode is higher than standby.

If you go to the command input screen, you should see a listbox containing many of the built-in speech commands that apply to the currently loaded plane. Just a matter of picking up the suitable one. No need to look-up the documentation.

If you happen to be using personal verbiage that the crew doesn't seem to react to, see this thread on how you can educate him to understand personal speech.

Essentially, create the command you want and tie it to the one the FO is trained to react to.

 

 

 

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?

On 3/9/2025 at 2:51 AM, AdequatelySuitable said:

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?

Good point.

Will be sorted before the end of this week.