Which NGX version is which?

[pete_auau 1,152]

Hmmm ok best bet is for Bryan to sort you out via team viewer

[mkear 0]

Ok so I got it to work - kind of - as far as the before taxi checklist.  Then no matter how i said it,  the bloody first officer wouldn't accept "ON" or "SET" or "CHECKED"  or even "UP YOURS" as a response to "generators" in the before taxi checklist.   (I have run the speech recognition training routine in Windows 7 twice already.   Maybe it just doesnt like Australian accents when you have it set to US English.   Maybe I have to fake a Tennessee accent.) 

 

What do you do when you can't get past a point?   Can you skip over the checklist item that you're stuck on?

 

I found that when "ON" or "SET" or "CHECKED" didnt work as responses,  that shouting "F##K YOU" seemed to work ok.   But only until the before taxi checklist.     Not sure what the neighbours must have thought.   I'm usually such a mild-mannered individual - never raise my voice.

 

Also it seems I can have FS2Crew  or liveries but not both.   Running the downloaded SP1c updater on my already up-to-date NGX breaks all the liveries.   The Operations Center says they require updating.  But letting the Operations Center update them seems to break FS2Crew. 

 

So after spending 4 hours today reinstalling all my NGX stuff again - twice - I haven't succeeded in making a flight.  

 

I had hoped to spend my evening making a flight for my Va but instead i spent it setting up, installing, configuring and re-installing stuff.    Gee .  just like a normal day.   What a great way to spend my day off.

 

Cheers

Mike Kear

Windsor, NSW, Australia.

[byork 2,258]

Hi Mike,

 

SP1C will clear remove any pre-existing liveries if memory serves correct.  

 

Again, if you require help, I'm willing to help you via a Remote Deskop session and I can walk you through everything.

 

 

You can skip any item in the checklist using the phrase "Next".

 

 

Regarding your problem with "on", check your mic setting.  We have non-native English speakers who have no problem with the speech recognition, so it should work for you.

 

You can train specific words using this method:

 

Problem: Speech recognition is having problems detecting certain words.  Can I train the speech recognition system for "specific" words?

Solution:
 

1. Yes, you can use the dictation facility in Windows.  
2. First, start 'Windows Speech Recognition' (this is not the FS2Crew Speech Recognition system, but rather the speech recognition system that comes with Windows).
3. Open a text document.
4. Next, dictate a list of words you are having trouble with. 
5. Every time the speech recognizer makes a mistake, use the "CORRECT THAT" voice command.  This effectively train the speech recognition engine to recognize how you pronounce these words.  You may need to dictate and correct the same words multiple times until the recognition rate improves. 

 

         There is another way (and better way) to train specific words as well for Vista and Win 7 users:
 

         1. Open the Microsoft Windows Speech Recognizer and RIGHT CLICK the microphone icon.  You can open the Windows Speech Recognizer by typing "Speech Recognition" in the search for programs box in the start menu.

 

          2. Click "ON: Listen to everything I say".  Next, Select "OPEN THE SPEECH DICTIONARY" and select "ADD A NEW WORD".

          3. When done, turn off Windows Speech Recognition.  It CANNOT be running while using FS2Crew.  It must be OFF!
 

[mkear 0]

Thanks Bryan for your offer to help.     The time zone thing will mean one of us will need to be up at 3 in the morning or some such, so I'll keep persevering myself for now.  I'm making progress, and learning a lot while I'm doing it,   so for now, I'll work on the issues I have and come back to you for help if i can't get past them. 

 

I was really amused that a bellowed "F##K YOU" was taken by the speech recognition as "Checked".  But i guess that was the "K" sound causing windows to see it that way.    i"ll follow the speech recognition training on the word "ON" and some of the other words and see how that changes things.

 

I did manage to get to taking off last night, but couldn't make the NGX go into LNAV so I gave up on flying the whole flight.   I think i remember reading something about that in the docs - either the troubleshooting section or the flows section somewhere so I'll look for that again.     It's not a big deal - it took me half a dozen flights before I successfully flew the NGX in a full flight in the first place.   There is a lot to learn here.  But that's ok - I knew it was going to be a lot to learn from the getgo.   I dont want anything that's not challenging anyway - that's partly why we like PMDG products anyway isnt it .   If they were a 3 minute learn, we wouldnt like them so much.

 

 

There's an issue that isnt addressed though and I need to bring to your attention.     I understand that part about how applying the SP1c updater will clear all the liveries.  But then if i reinstall all the liveries,  PMDG's Operations Center says they need updating.   If i let the OC update them,  it breaks FS2Crew.   I presume that's because the OC applies all the airline customisations and writes a new panel.cfg.   So now I have all my liveries installed again, but OC wants to update them.  I dont dare let it,  because i'll have to go back to the beginning and install everything all over again. 

 

 

This is an issue that I think only you and PMDG are going to be able to resolve, as I'm sure you've resolved plenty of issues together in the past.     You seem to have a pretty good relationship with them. 

 

 

Another problem I had was the font size in the documentation PDFs.   They look fine on the screen, but when they are printed up I found them impossible to read.   Someone with better eyesight would have no problem i guess but at my age, my eyesight is not what it was when I was 20.     So I found a way to have the flows and checklists in my iPad where I could manipulate the size and that solved a lot of problems.   I could move around easily,  tap here, tap there, flip back and forth from flows to checklists  and it was terrific.

 

Cheers

Mike Kear

Windsor, NSW, Australia

[pete_auau 1,152]

if this were the case  than everyone  who has  the ngx  and fs2 crew would be having the same issues as you are having  so it must be specific  to your set up some how

[byork 2,258]

 

 

I did manage to get to taking off last night, but couldn't make the NGX go into LNAV so I gave up on flying the whole flight.

 

Glad you're making progress.  The learning curve can be steep if you're not used to FS2Crew, but that's the consequence of us trying to do things realistically.

 

For training, be sure to watch the various FS2Crew NGX user created videos... there are large numbers of them on YouTube.

 

 

https://www.youtube.com/results?search_query=fs2crew+ngx

 

 

The autopilot/aircraft probably wasn't configured properly to accept an LNAV engagement... you weren't in the envelope for the autopilot to allow an LNAV engagement.

 

The test is to press the LNAV button manually.

 

Regarding the Operations Center and the Liveries, I haven't heard of that issue before, but I'll check it out.

 

Anyone else ever experience their NGX Panel.CFG with the FS2Crew entries on it being wiped clean after using the new Operations Center?

[mkear 0]

Well i finally made a complete flight,  from cold and dark to shut down cold and dark.    Had a smile on my face I can tell you

 

Peter you keep assuming that I'm criticising FS2Crew.  I'm not.     I think there are a few things Bryan could do to adapt to the new way PMDG are doing things   - like for example the Operations Center now makes all the liveries invalid for FS2Crew whenever you update them.    I dont know what the fix for that will be.     I think there's a few lines in the documentation that could be modified to make it clearer for people how to ensure the NGX is both up to date and compatible with FS2Crew.   That's not because of a shortcoming in the documentation, but because PMDG have changed the way they are presenting their product now.     But they are hardly earth-shattering issues, and I wouldnt think a huge job for Bryan to fix when he gets around to it.    As a software developer myself, I need feedback from users who are fresh to my projects, because often we get so close to something we can't see issues.   I assume Bryan is the same.   It would be a miracle if he was any different. 

 

But all the other issues are related to my learning speech recognition and making windows understand me even though I'm not American.     For example, try as I might, I could not convince the speech recognition that "auto" was a word and I was allowed to say it.  I must have tried about 50 times but it insisted I was saying "All Time"  or something else.  That's not the fault of FS2Crew - just part of my experience with this.  That's all.

 

As to the size of the documentation when printed out,  I already said (if you actually READ what i wrote) that my eyesight isnt what it used to be.   I'm not complaining about that either.  Just reporting what I did to get around it.   Maybe i might write an iPad app to take care of the prompts and checklists better if I get some time to do it. 

 

There's a lot to learn about FS2Crew, I knew that going in, and the videos I saw before i bought it told me that.   I'm not complaining so there's no need to be defensive. 

 

Cheers

Mike Kear

Windsor, NSW, Australia.

[byork 2,258]

Hi Mike,

 

We're checking into the Operations Center to see if it's wiping out the old panel.cfg with FS2Crew entries on it with a refreshed panel.cfg with no FS2Crew entries on it.

 

I have not had that one reported before, but we'll check.

 

The solution would be to cycle the  Enable/Disable FS2Crew button on the FS2Crew NGX Config Manager.

 

That would re-add the FS2Crew entries to the NGX's panel.cfg file should they have vanished

[mkear 0]

Regarding the Operations Center and the Liveries, I haven't heard of that issue before, but I'll check it out.

 

Anyone else ever experience their NGX Panel.CFG with the FS2Crew entries on it being wiped clean after using the new Operations Center?

Bryan,  the symptoms are as follows: 

 

[A] When you re-install the SP1c updater,  it clears all the liveries out.  That's ok I knew that. 

so if you re-install the liveries from the ptp files the Operations Center says they need updating.  (There's a red button under an installed livery in the OC instead of a green one and you get a message saying there are notifications in the Operation Center that you need to update liveries.)

[C] If you then update them by clicking on the red button in the Operations Center, it updates the liveries ok,  and the notifications go away but FS2Crew breaks.

 

I am assuming what is breaking is the panel.cfg file is being over-written by the Operations Center as it's applying all the airline customisations - panel configurations etc.

 

So the work-around is DONT let the Operation Center update the liveries.       I guess a proper solution is probably going to require you and PMDG to work together and figure out who needs to change what to make the updating leave the FS2Crew stuff intact in the panel.cfg. 

 

Over to you for that. 

 

Cheers

Mike Kear

Windsor, NSW, Australia. 

[byork 2,258]

I just had one of my beta testers try to reproduce this.

 

It worked fine for him.

 

Running the new Operations Center and updating the liveries did not remove FS2Crew from the NGX.

 

 

I'd like to see what you've done via a Remote Desktop if you don't mind.

[mkear 0]

Yes  - what time would suit?   What part of the world are you in?   I have time Wednesday and Thursday during the day (Australian Eastern Time), and Wednesday evening Australian Eastern Time. 

 

Cheers

Mike Kear

Windsor, NSW, Australia

[byork 2,258]

Mike,

 

Please email me directly at:

 

admin **** at***** fs2crew.com

 

 

Cheers,