Hello!

I am on the actual version of the Bus v2.0.2.415. FS2Crew version is v1.1. I use Voice recognition on WIN10 with P3Dv4 v4.5.12.30293.

First I noticed that the FO turned the taxi light on during the before start procedure. After the pushback and start of the engines he performed his taxi flow (set to activate automaticly) but he forgot to arm the speedbrakes and didnt set the flaps for takeoff.

I restartet the flight after this to perform it without Fs2Crew. Now I am reporting to see if this was just a hickup or if others also experiencing this.

Thank you.

 

I paste here what I found inside the Fs2Crew manager in terms of log:

Current Task: Creating the Critical Section Object... SUCCEEDED!
[Unknown Operating System]
[Unknown Flight Simulator]
Current Task: Creating the ISpRecognizer object... SUCCEEDED!
Microsoft Speech Recognizer 8.0 for Windows (English - US)
Current Task: Creating the ISpRecoContext object... SUCCEEDED!
Current Task: Setting the CallBack Function... SUCCEEDED!
Current Task: Setting the Notifications Interest... SUCCEEDED!
Current Task: Creating the ISpAudio object... SUCCEEDED!
Current Task: Setting the Audio Input... SUCCEEDED!
Current Task: Setting the Recognizer State... SUCCEEDED!
Current Task: Creating the ISpRecoGrammar object... SUCCEEDED!
Current Task: Loading the Command and Control grammar from the FS2Crew Grammar resource file... SUCCEEDED!
Current Task: Setting the rule with id 1 to ACTIVE... SUCCEEDED!
 

Are you using the very latest version of the FS Labs?

Please check your mouse Macro assignments in the FS2Crew menu.

The values will have likely changed.

You may need to re-assign them.

 

 

48 minutes ago, byork said:

Are you using the very latest version of the FS Labs?

Please check your mouse Macro assignments in the FS2Crew menu.

The values will have likely changed.

You may need to re-assign them.

 

 

The version I mentioned is the latest FsLabs version. I never used any mouse Macros... but I will check if there is something that shouldnt be there.

They probably will have changed with the new version of P3D.

Go to the Mouse Macro setup page on the FS2Crew Config Panel, and check the assignments.

I'm 99.9 percent sure the ID's will have have changed.

You can easily re-assign them.. only takes about 3 minutes.

 

50 minutes ago, byork said:

They probably will have changed with the new version of P3D.

Go to the Mouse Macro setup page on the FS2Crew Config Panel, and check the assignments.

I'm 99.9 percent sure the ID's will have have changed.

You can easily re-assign them.. only takes about 3 minutes.

 

I will check asap...

But I never touched anything in regards to mousemacros. I just installed fs2crew and made my settings im the cfg menu. I have to say I dont know what they are there for 😛

Are we supposed to do anything with the macros after installing? Just curious. 

Edited October 18, 20196 yr by Rhinozherous

Mouse mouse macros will be out of date since the P3D version changed.

Everyone's mouse macros IDs will be out of date (unless they stick with the old version of P3D).

Could you update FS2Crew to work with 4.5HF2 and FSL .415? 
I also never assigned anything in mouse macros or changed anything beside whats written in the quick start documentation, just installed it and it worked. I dont even know what mouse macros means. Everything is standard installation, why do we have to do this now? And how? 

Edited October 18, 20196 yr by disco79stu

I'm planning to do that when I a free moment.

But you can update it immediately on your end.

Just go to the Mouse Macro setup page on the FS2Crew Config Panel.

The instructions are right on the screen.  It's very simple. 

 

3 hours ago, byork said:

They probably will have changed with the new version of P3D.

Go to the Mouse Macro setup page on the FS2Crew Config Panel, and check the assignments.

I'm 99.9 percent sure the ID's will have have changed.

You can easily re-assign them.. only takes about 3 minutes.

 

But I dont have the newest version of P3D... I just updated the FsLabs Bus to the latest. See my P3D version in the first post.

Okay, if he didn't set the speed brakes or flaps for TO, it mean you didn't hit the trigger for him to perform his After Start flow.

Please check the manual.

You need to start the engines as per the manual in order to hit the trigger.

 

28 minutes ago, byork said:

Okay, if he didn't set the speed brakes or flaps for TO, it mean you didn't hit the trigger for him to perform his After Start flow.

Please check the manual.

You need to start the engines as per the manual in order to hit the trigger.

Yes, I was saying "Starting engine 1" and "Starting engine 2". After push and start I switched the engine master to Norm. 

This is my standard procedure as I made me a Checklist for the fs2crew procedures. It always worked...

But I will double check and report on a new flight, had no time so far unfortunately. 

Thank you! 

 

1 hour ago, Rhinozherous said:

Yes, I was saying "Starting engine 1" and "Starting engine 2". After push and start I switched the engine master to Norm. 

This is my standard procedure as I made me a Checklist for the fs2crew procedures. It always worked...

But I will double check and report on a new flight, had no time so far unfortunately. 

Thank you! 

 

are you starting  eng  2  first  than  1

12 hours ago, pete_auau said:

are you starting  eng  2  first  than  1

Yes, I just wrote it in the wrong order here in the post... As I said, it always worked this way (eng2 then eng1) 

Well, try it again, using the FS2Crew manual, not your own private checklist.

Follow the FS2Crew manual to the letter.  

Cheers,