Rameyuk

I think I understand the purpose of forcing the seatbelt to on. But since the signs are shown in the ECAM memo, It's actually noticeable if the signs are still off since the ECAM memo will be displayed in Blue in case people forgot about them. I myself never forgot about them since I always turn them on as part of my Captain Overhead Panel flow. Seatbelts On, No Smoking/Electronic device Auto. Even if the app manages the Seatbelt sign, I think the No Smoking/Electronic Device should be left alone, unless it can detect the current position (ie. IF No Smoking/Electronic Device = OFF, SET to AUTO. ELSE IGNORE) in case people forget about them. But I know this could be a difficult process to do given how you need to write the code to apply the command to the cockpit.

I think the response for pitch trim is "X Percent Set" as shown on the assist panel.

Thank you for the reply... that is indeed a strange bug. Because if I bind the "Toggle Taxi Lights" command from the control options to a button or a key, the runway turn off lights switches on and both sides illuminate. Same goes with Wing Light if I use the same Toggle Wing Light command and bind it to a key or button, it illuminates both sides. If the "events" that come from the control key bindings and the one used in FS2Crew are the same. Shouldn't it behave the same way as well? Unless they changed the "event" and made the original to only be the right side, while there's a different event that controls both that is now become the event used in the key binding. Would that also be a possibility, that the SDK documentation is outdated, and FS2Crew is still using the "old" event?

Hi, I tried searching for a similar topic about this, but I couldn't find anything specific. So basically, I set my FO to control lights (to simplify the process). However, there are a few behaviour that I noticed when they do. When the FO turn on the Wing Lights (I assume during their walkaround) the Wing Lights only turns on for one side. I have to switch off the wing lights first then switch it back on to have both wing lights turn on. (see video below at 18:30 mark) When I start for my taxiing, the FO also turns on the Taxi lights, but the Runway Turn Off Lights also behave the same way as the Wing Lights. It only turns on one side instead of both. Again I need to turn off the Runway Turn Off Lights first then Turn it back on to have the lights on both sides. (see video below) After landing and taxiing, asking to turn off taxi lights also turns off the Runway Turn Off lights but only for one side, I have to manually turn on the Runway Turn Off lights again and turn it off again to turn off both sides. (See video below at 1:44:20 mark) Here's a video that you can refer to what I mean. Is this a bug to be fixed in future updates, or is there a specific configuration that I need to do to get this working properly?

Excited.. I can't wait for the update.. Especially with the joystick button support.

I think it's better for me now. Probably either my computer has learned my phrases enough, or that I actually wear my headset properly this time. Previously I place my headset around my neck and pull the boom mike close to my mouth so that I can still hear the sounds coming from the speakers instead from my headset. But apparently that position isn't really good for voice recognition. After reviewing my livestream footage the sounds from the microphone doesn't sound as clear as I thought, and a lot of wind noise from my nose when I exhale. So I wear my headset properly this time and I can hear my voice a lot cleaner and no wind noise. And the voice recognition works better now. Instead of saying "Below the line" a dozen times without getting it correct. Sometimes it can detect it straightaway, or even if it fails, only take one extra try to get it right. So it's all good. Thanks.

If FS2Crew is using the Windows Speech-to-text recognition software. Perhaps it's the Windows itself that's causing the issue? I guess I could try training myself using notepad and pressing Windows Key + H to start typing with my voice, and do a multiple times saying "Below the Line" and look at the typed text and I can adjust my own speech until it types the right phrase. I wouldn't say to change the phrase if it's not technically correct. I think we need a override switch or something that allows FS2Crew to progress the checklist. Perhaps something similar to the Manual Flow dropdown list. We could have a drop down menu for any phrase that we would have said with voice control. So if we're stuck with saying the correct phrase and the app doesn't register the command, we can open the dropdown menu, go to the phrase we would have said and click it, and the app will behave as if we're saying the correct command. I mean, the info page already have all the phrases listed in there for us to refer to when we want to say the voice command. But I think by taking it a step further to make it into a drop down choice, it would also help to continue on progressing when our voice commands are not being registered.

Is anyone having issues trying to call out "Below The Line" phrase into FS2Crew? I keep saying the phrase, but it keeps on receiving my voice command as "Aligned". I'm doing a lot of livestreaming with FS2Crew, and it just feels embarrassing to keep repeating "Below the Line" as clearly as I can over a dozen times only for it to receive as "Aligned" and nothing happens every single time. Is there a quick override button that I can press when I'm stuck like this? If I press the kill switch, it would only reset the entire checklist, and when I call the same checklist again, it would stop at "down to the line", and it's waiting for me to say "below the line" and it keeps listening my phrase as "aligned" again. It makes it difficult to progress through the checklist. Anyone have any ideas?