starvip

Bryan I experienced exactly the same issue whenever I fly online the speech by picks up ATC as well as picking up its own sound... Have you ever considered reversing the mute button? So instead of having a push to soft mute having a binding to push to speak? that way when you speak in never picks up any background noise except for the time you want it to listen. Or at least having it as an option alongside how it is now... then you could reverse the hard mute to be the opposite to just listen all the time for people who don’t want to push a button. Thanks

Fantastic news! I did do the The new way to Train the Speech Recognizer for "Specific Words" like Auto fix, didnt work for me unfortunatley. Look forward to the new version.

Hi ive been using Fs2crew for many years and have had great experiences up until now. I used to fly SOP3 (with a lowcost airline in europe) on the NGX back on windows 8. Hundreds of fault free flying. However SOP3 on the NGXu is giving me one small problem. The interface just cannot recogise me saying ON its always ARM 🤣 I am a UK user and speak very clear English it just refuses to recognise me. Ive even tried saying it like an american, still nothing. Still always "ARM". On SOP3 this command is imperative and is the only allowed response for a lot of checklist items. This new found non understanding has been since US English was required to me set on my PC for FS2crew to work. Ive used the voice trainer 3 times and have also tried to set "words that sound like other words" in the voice recog options. Is there anything else I can do to get it to understand me? Thanks

Everything is fixed for me now On 1.1 regardless of the lighting config thanks for your help and hard work!

Same for SOP3 unfortunately. Ive never really used SOP2 to unsure if its the same for that too.

Will do. This was SOP1 Voice Control. No LED no pulse. Im about to do a flight with SOP3 so ill see if its any different and attach the details after.

Thanks for clarification..picture attached shows the issue...you can see the FO operated right fixed landing light vs the one I toggled on the left to get it to come on..it doesnt engage fully hangs in the middle so the light doesnt actually come on. Thought my landings at night were a bit dark! 🤣 This is with standard halogen light config no pulse with SOP1 Voice

Forgive me I have found the actual issue now which caused confusion on my end. I was used to the wings splash and it wasn’t getting it and upon further inspection it seems that the first officer when operating the landing lights (and also the logo lights) doesn’t fully press the switch resulting in it not coming on at all. Read somebody else’s comment about logos not coming on. When operating the fixed landing lights/logo lights The switch remains in an intermediate position between on and off resulting in none of the lights working. If you manually toggle the switch afterwards it operates normally in the full on or off position. (this is in voice control SOP1)

No. The runway turnoffs are in the wing root with the fixed landing lights. Fs2crew for the original NGX correctly depicted what the vast majority of carriers do...taxi + turnoffs on when taxiing....takeoff...fixed landing and runway turnoffs remain on until 10k...then back on together at 10k in the descent (the turnoffs are what incidentally illuminate the inner cowling of engines aswell, a sight we are all used to at night when its time to land at 10k) Anyway my point is it was active on the the NGX version and not this version for the NGXu for some reason, so wondered why it had changed. You coded it in all 3 SOPS on both the NGX legacy and Reboot.

I’ve noticed on the new version that the RW turn off the lights aren’t operated when descending through 10,000 and are turned off with the taxi lights after the gears retracted. Looking at other sources the turn offs remain on until 10,000 feet and all turned on with the landing lights when descending. This was modelled correctly in the original PMDG 737 simulation but seems not to do it on the new one. Any ideas?

Correction it ONLY takes the weight of the aircraft into consideration and whether or not icing is present, which is more than adequete for 9/10 flights.

No problem.. Glad I could help! When using FS2Crew heres what should work...when you have loaded up the dash, with the correct fuel and payload, first press CTRL+SHIFT+F1 which is the FSX default for fuel cut-off ... This is because if you load up a cockpit state with the engines not running for some reason FSX, P3D still thinks the engines are running... This is the problem I ran into with random after landing flow messages...vspeeds I assume picks up on the state of the aircraft... With the engines off on the ground you should get the takeoff speeds... In the air engines running landing speeds.... And on the ground with the engines running the landing flow... So you can see how it runs into issues when it thinks the engines are running within FSX even when they are not ... But yes the after landing flow is part of vspeeds, it will perform the following actions.. bus tie to TIE, raise the flaps, set the anticollision to RED, move the spoilers to TAXI, turn off all the Anti ice pitot static heaters. The author said it was designed to help people who are flying alone with the dash 8. The reason I would not try to use the landing flow is because it's already built into FS2Crew and when you call for the after landing checklist the first officer will do most of these items anyway. I call up the speeds before I open the FS2Crew panel ensuring I've done what I've said above, and call on it again just before top of descent for landing speeds and it works perfectly. And if worst comes to worst use the aurasim app which is much more realistic in terms of entry . Hope this helps! Miles

The message is from Vspeeds..Its a fanstastic little program that calculates V Speeds for takeoff and landing based on weight and icing without having to look up figures It a lua. module file that can be brought up in the sim by assigning a key in FSUIPC..you It also performs an after landing flow. For me Vspeeds and FS2Crew work fine together so long as you populate your speeds before you use FS2Crew and dont use the after landing flow.

As it stands you call "FLAPS 0, I A S TWO HUNDRED, CLIMB CHECKLIST TO THE LINE" or 160 or 240...... quite a mouthful, especially when on VATSIM and you have ATC barking at you to contact departure....Most of the carriers I see simply call flaps up and the FO does the same flow regarding props, bleeds, flaps and speed...The two most popular procedures on the Q400 as of late seem to be (Flaps up, Props 900, speed 210)...or (Flaps up Props 850, CL soft button, speed 210)... Maybe something for the future we could select which type of climb we require in the BRIEFING page. But I think at the very least simplifying the flaps up call would definatley smooth things out. Im sure lots of people have no proplem saying it with practice. But its very easy to get jumbled up saying the command if alot is going on at once no matter how many times you do it.. Just a suggestion of course love the product! Miles

Join Norwegian virtual