If you think you have found something that's not working.........

[tigran9]

My FO just extended the slats on me at FL340 and Mach .78... immediate overspeed warning... I came to the cockpit coughing...

shouldn't this be prohibited?

[FS++]

4 hours ago, tigran9 said:

My FO just extended the slats on me at FL340 and Mach .78... immediate overspeed warning... I came to the cockpit coughing...

shouldn't this be prohibited?

It IS prohibited.

The vast majority of critical actions are safeguarded against accidental trigger. Command "extend slats" should be dealt with similar to first flaps detent extension, with a "speed check" first and only proceed with the command if speed is below damagiung speed which he gets from a reference file.

This isn't VoiceAttack.

Which MCE specific product are you on? Which simulator, and which plane did it happen with?

 

[tigran9]

On 4/26/2023 at 8:51 PM, FS++ said:

It IS prohibited.

The vast majority of critical actions are safeguarded against accidental trigger. Command "extend slats" should be dealt with similar to first flaps detent extension, with a "speed check" first and only proceed with the command if speed is below damagiung speed which he gets from a reference file.

This isn't VoiceAttack.

Which MCE specific product are you on? Which simulator, and which plane did it happen with?

 

I'm on MCE X-Plane 12 1.6.60 and flying the Toliss A321.

I also noticed that even with the patch you provided no callouts on reverse green and spoilers are made after landing.

Furthermore - even though "verbose" is switched off, I constantly hear the "stobe lights on, landing lights on" call during the flows.

[FS++]

12 hours ago, tigran9 said:

Furthermore - even though "verbose" is switched off, I constantly hear the "stobe lights on, landing lights on" call during the flows.

The verbose option applies individually to each flow. You need to enable/disable it per flow. 

The only time where it won't work as expected is when somehow the "whatever_flow_Name.vscr" file attribute is somehow in "Read Only", in which case Windows will deny MCE setting "verbose=1" or "verbose=0" from the UI.

[Fabio Lessa]

Hello everyone,

I have been using MCE for a few months and I think I have accumulated the minimum necessary experience to point out some aspects that I believe are not working as programmed.

I took a superficial look at the pages of this post and I'm not sure if this has already been discussed... there are over 50 pages here, so something may have gone unnoticed. I apologize if I am being repetitive.

I will be posting little by little here to not pollute the content too much, and I emphasize that my only intention is to make the tool's behavior available so that it becomes even better.

For now, I am basing myself on the following configuration. I always keep both X-Plane and any addon updated to their latest version.

X-Plane 12.07r1
ToLiss A320 v1.0.2
MCE 1.6.70
For this A320, during takeoff, I have noticed that the callouts have been those of landing; as if it were inverted. This occurs regardless of takeoff power or airport. The only callout I deactivate is V2 and, during landing, I keep the 70 kt callout.

In a nutshell, in the ToLiss A320, the MCE takeoff callouts have been: minimums, 500 ft, one thousand feet above the ground, radio altimeter ready, ..., instead of 100 kt, V1, rotate, positive climb, etc.

What might be happening?

[FS++]

20 hours ago, Fabio Lessa said:

Hello everyone,

I have been using MCE for a few months and I think I have accumulated the minimum necessary experience to point out some aspects that I believe are not working as programmed.

I took a superficial look at the pages of this post and I'm not sure if this has already been discussed... there are over 50 pages here, so something may have gone unnoticed. I apologize if I am being repetitive.

I will be posting little by little here to not pollute the content too much, and I emphasize that my only intention is to make the tool's behavior available so that it becomes even better.

For now, I am basing myself on the following configuration. I always keep both X-Plane and any addon updated to their latest version.

X-Plane 12.07r1
ToLiss A320 v1.0.2
MCE 1.6.70
For this A320, during takeoff, I have noticed that the callouts have been those of landing; as if it were inverted. This occurs regardless of takeoff power or airport. The only callout I deactivate is V2 and, during landing, I keep the 70 kt callout.

In a nutshell, in the ToLiss A320, the MCE takeoff callouts have been: minimums, 500 ft, one thousand feet above the ground, radio altimeter ready, ..., instead of 100 kt, V1, rotate, positive climb, etc.

What might be happening?

Co-pilot works out flight phase automatically by looking at several parameters, among them throttle levers positions.

In TakeOff phase for instance, they need to be seen beyond CLB detent.

If you are using hardware throttles, try calibrating again.

Will have to check with latest version ofToliss plane, as you never know when say a dataref changes and suddenly can't see item.

If you can't get the first "one hundred knots" call-out, push the throttle all the way forward and see if you can get the remaining ones.

If you do, then reading is OK and perhaps just a matter of adjusting the refrence throttle value that indicates it's above CLB.

[OCDD9]

I purchase MCE FlyByWire A320 only. Features almost meet my expectation. I only use A320 FlyByWire in MSFS.

For ATC Communication (Native ATC), almost command was executed well. However, I have meet some Ground services command that is not executed, I don't know whether I am using wrong command or not. (I don't active required exact call-sign options in ATC Menu of MCE)

My command is as following: (I push PTT button, then say)

Pushback: Ground, American twenty three one one, request pushback/ Ground, American twenty three one one, request pushback and start.

Fuel supply: Ground, American twenty three one one, could you send a fuel truck.

Fuel supply: Ground, American twenty three one one, could you send a power unit.

I can see MCE display red text "Ground, American 2 3 1 1, request pushback and start" after my command. But there's no pushback feedback from Native ATC and no pushback select action in ATC Menu.

Then I temporarily use MCE Voice control (not PTT ATC command), "ATC one" to select Pushback, "ATC two" to select Fuel truck, ... but it's not real feeling because just Voice control help select ATC command in ATC list of MSFS and I must maintain ATC Window open to know what I am going to select by voice control.

[Fabio Lessa]

On 10/13/2023 at 7:04 AM, FS++ said:

Co-pilot works out flight phase automatically by looking at several parameters, among them throttle levers positions.

In TakeOff phase for instance, they need to be seen beyond CLB detent.

If you are using hardware throttles, try calibrating again.

Will have to check with latest version ofToliss plane, as you never know when say a dataref changes and suddenly can't see item.

If you can't get the first "one hundred knots" call-out, push the throttle all the way forward and see if you can get the remaining ones.

If you do, then reading is OK and perhaps just a matter of adjusting the refrence throttle value that indicates it's above CLB.

Hello Gerald,

Thank you for your usual quick response. Indeed, that might be the case. I do use hardware throttles that are not the Thrustmaster Airbus edition, so in the ToLiss aircraft, I push the levers until I hear the 2 clicks, indicating that I've reached the FLX/MCT.

I'm not sure if, even though I'm in the expected FLEX setting as read on the FMA, the MCE could be reading something below a CLB setting because I imagine the difference in the dataref is significant, or not?

In any case, I did two more flights with the A320neo after my initial post, and both of them had the expected callouts during takeoff. If this happens again, is there any file I can then share with you for you to evaluate the condition?

Additionally, the spoiler and reverse callouts during landing have not been working. Everything goes well down to the "minimums" callout (which, for some reason that might be my misconfiguration, is made at the wrong time several times), but the subsequent ones are not made.

[FS++]

12 hours ago, OCDD9 said:

I purchase MCE FlyByWire A320 only. Features almost meet my expectation. I only use A320 FlyByWire in MSFS.

For ATC Communication (Native ATC), almost command was executed well. However, I have meet some Ground services command that is not executed, I don't know whether I am using wrong command or not. (I don't active required exact call-sign options in ATC Menu of MCE)

My command is as following: (I push PTT button, then say)

Pushback: Ground, American twenty three one one, request pushback/ Ground, American twenty three one one, request pushback and start.

Fuel supply: Ground, American twenty three one one, could you send a fuel truck.

Fuel supply: Ground, American twenty three one one, could you send a power unit.

I can see MCE display red text "Ground, American 2 3 1 1, request pushback and start" after my command. But there's no pushback feedback from Native ATC and no pushback select action in ATC Menu.

Then I temporarily use MCE Voice control (not PTT ATC command), "ATC one" to select Pushback, "ATC two" to select Fuel truck, ... but it's not real feeling because just Voice control help select ATC command in ATC list of MSFS and I must maintain ATC Window open to know what I am going to select by voice control.

In general items in ATC menu between brackets aren't considered ATC transmissible messages. I mean things like [ 1 - Tune whatever on XXX.XXX ], [ 4 - Ground services]]

DO not hold the PTT key for these. Rather make a verbal request to the relevant person in charge.

For ground services, see document Windows Start->Multi Crew FlyBywire A320->GSX&AES pdf document.
Once the ramp agen pops-in (he only does once the battery is on, aircraft on ground no engines running), you can ask him to coordinate for fuel, catering.

Examples: Assuming "Simon" is the ramp agent

Simon we need refueling

Simon we need some fuel

Simon we are requesting catering

Simon requesting catering

The pushback items are handled when you interact with ground mechanic

ground are you ready for push

ground begin pushback

ground pushback left

ground pushback right

can also use "mechanic", "ground mechanic", "ground engineer" (and a few other variations) instead of starting speech with "ground".

Although the speech grammars are built to catch as many speech variations as possible,If you happen to intuitively say something else completely unexpected and getting no reaction after trying a couple of times, please use this technique to teach your crew to understand whatever speech you may come up with. It's a matter of tying a custom command to a built-in one and the crew will interpret your speech as if you said the built-in sentence it was tied to

The custom speech can even be in non-English language. Many people don't know this

 

[FS++]

5 hours ago, Fabio Lessa said:

Hello Gerald,

Thank you for your usual quick response. Indeed, that might be the case. I do use hardware throttles that are not the Thrustmaster Airbus edition, so in the ToLiss aircraft, I push the levers until I hear the 2 clicks, indicating that I've reached the FLX/MCT.

I'm not sure if, even though I'm in the expected FLEX setting as read on the FMA, the MCE could be reading something below a CLB setting because I imagine the difference in the dataref is significant, or not?

In any case, I did two more flights with the A320neo after my initial post, and both of them had the expected callouts during takeoff. If this happens again, is there any file I can then share with you for you to evaluate the condition?

Additionally, the spoiler and reverse callouts during landing have not been working. Everything goes well down to the "minimums" callout (which, for some reason that might be my misconfiguration, is made at the wrong time several times), but the subsequent ones are not made.

Thanks for feedback.

Please download this file

Go to \X-Plane\MCE dlls\64 Bit\ folder.

Save previous "xmcTolA3X.dll" found there somewhere else, then replace it with new one.

Report back. Thanks

 

 

[Fabio Lessa]

On 10/18/2023 at 1:33 PM, FS++ said:

Thanks for feedback.

Please download this file

Go to \X-Plane\MCE dlls\64 Bit\ folder.

Save previous "xmcTolA3X.dll" found there somewhere else, then replace it with new one.

Report back. Thanks

 

 

I downloaded the file and saved it as requested. Coincidentally or not, my recent flights with the ToLiss A320neo no longer had the approach callout behavior during takeoff.

However, yesterday I flew the ToLiss A340 and it happened... callouts of 500 ft, 1000 ft above the ground, etc. I was recording the flight, and you can clearly hear the two clicks for the FLEX/MCT position.

I'm avoiding using X-Plane in case you need any log files, if there are any that could help. Nevertheless, I have the takeoff recording on YouTube in a private link if you wish.

[FS++]

On 10/27/2023 at 7:06 PM, Fabio Lessa said:

I downloaded the file and saved it as requested. Coincidentally or not, my recent flights with the ToLiss A320neo no longer had the approach callout behavior during takeoff.

However, yesterday I flew the ToLiss A340 and it happened... callouts of 500 ft, 1000 ft above the ground, etc. I was recording the flight, and you can clearly hear the two clicks for the FLEX/MCT position.

I'm avoiding using X-Plane in case you need any log files, if there are any that could help. Nevertheless, I have the takeoff recording on YouTube in a private link if you wish.

Thanks for feedback.

The dll handles Toliss A319 to A321 as well as A340.

Probably need to do the same for the A340 aircraft. Checking that FO can see thrust levers beyond CLP detent.

Only tested with A319.

[Fabio Lessa]

18 hours ago, FS++ said:

Thanks for feedback.

The dll handles Toliss A319 to A321 as well as A340.

Probably need to do the same for the A340 aircraft. Checking that FO can see thrust levers beyond CLP detent.

Only tested with A319.

How can I check if the FO managed to see that the thrust levers are beyond CLB detent? Because visually, the thrust levers were in FLEX/MCT, just like the indications on the PFD.

If I observe it through the dataref, which parameter should I look at, and from what value is the MCE FO programmed to understand that the takeoff thrust has been set?

[FS++]

On 10/30/2023 at 6:22 PM, Fabio Lessa said:

How can I check if the FO managed to see that the thrust levers are beyond CLB detent? Because visually, the thrust levers were in FLEX/MCT, just like the indications on the PFD.

If I observe it through the dataref, which parameter should I look at, and from what value is the MCE FO programmed to understand that the takeoff thrust has been set?

Before the change it was monitoring dataref array "sim/flightmodel/engine/ENGN_thro".

Turned out in most recent Toliss was reporting 0.0 all the time. Now switched to "sim/flightmodel/engine/ENGN_thro_use" in most recent dll. The threshold being 0.7 for CLB detent

It could be that the A340 is still using the other dataref (it would be the case if you never had any issue with that specific plane before replacing dll).

In any case, will be sorted once testing is done on most recent A340 aircraft implementation.

[Deni]

Does this program work adequately on ATR-42/72 for anyone?