Glad to see this released! Fortunately, I exclusively fly the FSLA320 with the corresponding FS2crew, so 98% of the triggers I know...or so I thought. Anyway, here's some feedback assuming it's valuable. I'll preface this by saying this is after one flight.

• I DEEPLY miss the "mute key" functionality. Am I right in that it doesn't exist in this version? I know there's a push to talk button assignment, but that would just make focusing and communicating to ATC online a nightmare. If it doesn't exist, what's the feasibility of it coming back? Even if I'm eating while its running in the background it just "check"'s incessantly. 
• I had to manually start the PNF flow in a few areas:
  • After start flow (even when the ENG selector was turned back to normal)
  • Flight control check (I did my flow, but it didn't look like the speech system was recognizing it despite it being recognized in the FSL version
• Somehow the "take off" flow is triggering mid air (setting the spoilers to arm, triggering the seatbelt sign, and the landing lights), despite the fact that I'm not saying anything (really, just eating Goldfish...). Maybe disabling certain words from particular phases of flight?
• What's the rationale for not having an Approach Checklist?
• Passing 10K, the LS system wasn't activated (button not pushed). Am I to specify the type of approach somewhere so it triggers?

I'll do another flight at some point to see if some of the issues are recurring. 

 

 

Hi Antonio:

Mute:  In all our testing, PTT really is better than having an open mic.

If using on-line ATC, just use a different button.  One for talking to ATC, and one for talking to your FO.

If you like though we could probably bring back the Hard Mute button.


After Start Flow: Make sure you speak "Starting Engine 1" / "Starting Engine 2" as shown in VOICE COMMAND ASSIST.  Those are necessary conditions for the After Start flow to trigger when you return the Ignition to Normal.  So ensure they are detected.


Flight Control check:  Not sure what you're missing but keep the ASSIST panel open.  It will tell you what to do and say while you're learning the software.


"Takeoff":  In V1.1 we'll add a condition so it can only work on the ground should it be ever detected.  But again, use the PTT key over the open mic.  It just works.

Approach Checklist:   There is an approach checklist 🙂   Look at the Voice Commands list in the Info Center.  It's definitely there.

LS at 10K:  FO will turn on his side only, but make sure you have the option checked for it on the Config Panel.  It has it's own config option.

Cheers,
 

9 hours ago, byork said:

Hi Antonio:

Mute:  In all our testing, PTT really is better than having an open mic.

If using on-line ATC, just use a different button.  One for talking to ATC, and one for talking to your FO.

If you like though we could probably bring back the Hard Mute button.

Yeah, I mean candidly, I don't find the PTT to be realistic at all (for obvious reasons) so don't plan on using it. Plus, I fly exclusively on VATSIM (have since the beginning!), so trying to essentially manage two sets of comms with two different buttons doesn't make much sense when the product is deigned to lighten the workload. I'd love to have the hard mute back. 

After Start Flow: Make sure you speak "Starting Engine 1" / "Starting Engine 2" as shown in VOICE COMMAND ASSIST.  Those are necessary conditions for the After Start flow to trigger when you return the Ignition to Normal.  So ensure they are detected.

Yup, did that. I'll do another flight here soon where I'll see if this is a repeat offender for some reason.

Flight Control check:  Not sure what you're missing but keep the ASSIST panel open.  It will tell you what to do and say while you're learning the software.

Yup, did that. In fact, I had the voice command assist window up each time. In fact, there's a discrepancy between what the voice assist is telling you to say vs what's actually said (when forcing the PNF workflow). I made the assumption that it should be the same voice phrases as the FSL version, "Full up, Full down, Neutral" etc, but the voice assist tells you to say "Elevator - Full Up ---> Down", and "Ailerons - Full Left ---> Right". So after not getting anything going through the full left, full right neutral, I tried reading off "elevator-full up, etc" and neither triggered. Forcing the PNF's workflow, he read off, "Full Up, Full Down, Netural" which is A) The workflow I assumed we were supposed to read based off of previous products that ultimately didn't trigger anything, and B) is different than what the VOICE COMMAND ASSIST has listed.

"Takeoff":  In V1.1 we'll add a condition so it can only work on the ground should it be ever detected.  But again, use the PTT key over the open mic.  It just works.

Noted on the V1.1 addition. Though I adamantly avoid the PTT key vs Open Mic for reasons listed above. 

Approach Checklist:   There is an approach checklist 🙂   Look at the Voice Commands list in the Info Center.  It's definitely there.

Hmm, I didn't see where the approach check list was. I guess I'm used to passing the TA and going "Approach Checklist". Did that sequence but noting happened. I'll take a look again.

LS at 10K:  FO will turn on his side only, but make sure you have the option checked for it on the Config Panel.  It has it's own config option.

Ah! Not sure why I was looking for them to turn on my side also. Thanks!

Cheers,

 

Edited August 16, 20214 yr by AntonioK

So here's feedback after a 2nd flight:

• Same problem with the after start. After I announced "starting engine one" (and I have the sequence in config set to 1 then 2), the assist looked like the image below. Announcing "starting engine 2", there's nothing in the command assist. So as I expected based on that, same thing as yesterday, when I toggled the IGN back to "normal', nothing triggered, causing me to have to manually trigger the FO flow again.
• If the wrong checklist is said, then you can't cancel that checklist and call the one you mean to (example, saying "before take off" when you mean "before start"). You have to quit the system all together and relaunch it to be able to trigger the right check list. +
• For the second time, the system is not recognizing "elevator full up" or "full up, full down, neutral". I doubt it's me because this works with other products of yours, so I can't pin point the solution.

Hi Antonio,

1.Was "Starting Engine 1", "Starting Engine 2" detected?  You can see it in the display if it was detected.

If they're not detected, the FO's after flow will not get triggered when you return ignition to Normal.

2. You can say "Cancel the Checklist".  That will kill the checklist.  You don't need to restart the whole program.  Available voice commands are in the Info Center.

3. "Elevator full up /down", etc., are not voice commands.  That's a note in the Flows Assist panel telling you how you need to position the controls during the flight controls check.

The FO is the one who will say "full up", "full down" when you move move the elevator/aileron.

I think I gotta make a training video.


 

18 minutes ago, byork said:

Hi Antonio,

1.Was "Starting Engine 1", "Starting Engine 2" detected?  You can see it in the display if it was detected.

• Yes, it was detected - both of them. After I'd say one, then it would disappear from the things to say list in the assist panel.

If they're not detected, the FO's after flow will not get triggered when you return ignition to Normal.

2. You can say "Cancel the Checklist".  That will kill the checklist.  You don't need to restart the whole program.  Available voice commands are in the Info Center.

• That's what I thought, too. However, after calling "cancel checklist", and calling for the one intended, nothing would happen. The voice command would be recognized in green, but nothing would happen.

3. "Elevator full up /down", etc., are not voice commands.  That's a note in the Flows Assist panel telling you how you need to position the controls during the flight controls check.

The FO is the one who will say "full up", "full down" when you move move the elevator/aileron.

• I thought this as well. After I call "flight control check",  I'm moving the elevator, rudder, but the FO is not saying anything. 

I think I gotta make a training video.


 

 

Hi Bryan,

    I think training video is necessary especially for the fresh people like me.

56 minutes ago, SophisDriver said:

Hi Bryan,

    I think training video is necessary especially for the fresh people like me.

We'll try to get something.  I'm horrible at video producing though.

If you're new to FS2Crew, start with "Button Control".  Button Control is pretty easy since you're basically just following a linear path.

Then once you see how the system works, then advance to Voice Control.

11 minutes ago, byork said:

We'll try to get something.  I'm horrible at video producing though.

If you're new to FS2Crew, start with "Button Control".  Button Control is pretty easy since you're basically just following a linear path.

Then once you see how the system works, then advance to Voice Control.

Will definitly try the button control. Thank you SIr.

Edited August 17, 20214 yr by SophisDriver

2 hours ago, AntonioK said:

 

Okay, I just look at the code to refresh my memory.

The trigger for the After Start flow is:

1. Previous action "Starting Engine 1".
2. Ignition back to normal.

That's your problem there.  You're starting 2 last, so 1 is not the previous action, so the condition was not met.

Normally engines are started 2 then 1, but I know some places do 1 do then 2.

We'll deal with your start sequence scenario for V1.1.  That's a legit bug.

3. "Cancel checklist" I'm not sure about that... That one I can't reproduce.


For your flight controls check issue:  Try using the keyboard as a test. If you're using hardware, due to a calibration issue with your joystick axis, you may not be hitting the full stop limits, and thus triggering the FO's audio call trigger points (Full Left, Right, etc.)

Edited August 17, 20214 yr by byork

2 minutes ago, SophisDriver said:

 

 

Edited August 17, 20214 yr by SophisDriver

Byork,

I do not own any FS2Crew Products but I have to say that I am constantly amazed and impressed with your customer service attitude, your response times and the help (over and above) that you consistently display in this forum.

Well Done Sir.

Regards

Tony

3 hours ago, byork said:

Okay, I just look at the code to refresh my memory.

The trigger for the After Start flow is:

1. Previous action "Starting Engine 1".
2. Ignition back to normal.

That's your problem there.  You're starting 2 last, so 1 is not the previous action, so the condition was not met.

Normally engines are started 2 then 1, but I know some places do 1 do then 2.

We'll deal with your start sequence scenario for V1.1.  That's a legit bug.

3. "Cancel checklist" I'm not sure about that... That one I can't reproduce.


For your flight controls check issue:  Try using the keyboard as a test. If you're using hardware, due to a calibration issue with your joystick axis, you may not be hitting the full stop limits, and thus triggering the FO's audio call trigger points (Full Left, Right, etc.)

Ahh. Okay, so one was a bug. I didn't get a chance to test the axis challenge since I removed all the number pad keys that were bound to an aileron or elevator, so I'll have to specifically try to set some of those up again to test that. As a result, that was the only one I had to force through. Is a solution to have a verbal trigger for that conclusion similar to "set and checked"? Maybe "Flight control check complete" (similar to the way you have it built in the PMDG FS2crew where that verbal cue is the trigger).

So far I haven't announced the wrong check list, so I'll have to keep you up to date on that one if I come across it again. 

On one note, the approach checklist: I fortunately know when to call for it given how often I use your FSL product, but there's nothing within the program to tell you that's a pending checklist especially because there's no PNF flow for that.

24 minutes ago, AntonioK said:

Ahh. Okay, so one was a bug. I didn't get a chance to test the axis challenge since I removed all the number pad keys that were bound to an aileron or elevator, so I'll have to specifically try to set some of those up again to test that. As a result, that was the only one I had to force through. Is a solution to have a verbal trigger for that conclusion similar to "set and checked"? Maybe "Flight control check complete" (similar to the way you have it built in the PMDG FS2crew where that verbal cue is the trigger).

So far I haven't announced the wrong check list, so I'll have to keep you up to date on that one if I come across it again. 

On one note, the approach checklist: I fortunately know when to call for it given how often I use your FSL product, but there's nothing within the program to tell you that's a pending checklist especially because there's no PNF flow for that.

We could add a "flight control check complete" command in case user get stuck for whatever... but it's definitely a joystick calibration issue.

The thing with the Approach Checklist is there's no real hard and fast rule on when you'd call it.

People can see it in the list... so you can call it whenever you want.

Many would do it when passing Transition Level...  some might do it later... some earlier... it can depend on the situation.

Yeah that makes sense. I'll try on the next flight I do to re-set those key bindings to see if those trigger it. 

On another not, do you know if there's anything in the code to turn on the brake fans during final? I noticed it for the second time after calling "gear down" then "flaps three", then I hear a "click" and the brake fans have been turned on.

Edited August 17, 20214 yr by AntonioK