hello

1-if i set flaps 2 for takeoff and then order flaps one during acceleration after takeoff ,fo does nothing.

2-if i set a packs off takeoff, after takeoff ordering packs 2 on ,fo does nothing too, although it works for pack one.

3-if i order FO to start APU ,he replies 'apu already running' although its off.

4-hdg and altitude orders are very random sometimes it works an sometimes he sets a wrong value specially if i give the order during a turn.

thanks

 

1 hour ago, ayousry said:

hello

1-if i set flaps 2 for takeoff and then order flaps one during acceleration after takeoff ,fo does nothing.

This is by design. During the takeoff process FO will refrain from handling stuff that could disrupt takeoff, or deemed not critical. Ask "brake fan off" while taking off and he should say something like "we're supposed to focus on takeoff". Only a few commands should be accepted, like "max power" and a few others. Not sure if flaps are among them. Will have to check

2-if i set a packs off takeoff, after takeoff ordering packs 2 on ,fo does nothing too, although it works for pack one.

Will be checked

3-if i order FO to start APU ,he replies 'apu already running' although its off.

4-hdg and altitude orders are very random sometimes it works an sometimes he sets a wrong value specially if i give the order during a turn.

For items 3 & 4, I suggest you update to the very latest version and we'll take it from there.

http://www.multicrewxp.com/Downloads.html

The actual version is V3.0.3.2

thanks

 

Answers embedded.

Thanks

for first issue, i do request flaps one after to and during acceleration(i mean acceleration at acc alt when airborne @ approx 2000-3000ft) which is a normal procedure in real life if u selected flaps 2 for to, its different than what u smartly implemented of rejecting non logic requests during to run

For 3 and 4, I have latest version

 

Edited April 9, 20233 yr by ayousry

3 hours ago, ayousry said:

Thanks

for first issue, i do request flaps one after to and during acceleration(i mean acceleration at acc alt when airborne @ approx 2000-3000ft) which is a normal procedure in real life if u selected flaps 2 for to, its different than what u smartly implemented of rejecting non logic requests during to run

For 3 and 4, I have latest version

 

I was referring to the takeoff run on ground where some command inhibition applies.

Once airborne, you could command any flaps detent. You could even turn downwind and command flaps 3 for circuit training if you wish and witout telling the Fo beforehand.

So, maybe your command didn't get through. I guess you couldn't tell as the "show commands in FS" doesn't wok in VR.

 

yes maybr i wasnt clear, i mean after airborne, the fo replies flaps one but never set it , soething is not right if u command flaps one when flaps two is set

9 hours ago, ayousry said:

yes maybr i wasnt clear, i mean after airborne, the fo replies flaps one but never set it , soething is not right if u command flaps one when flaps two is set

Not sure I have the latest version of the plane as you never know when some changes cause the interface to break.

Once the engines are running on ground, I suggest you command various flaps positions, 1,2,3,4 and check that each time FO knows exactly where the handle was.

I mean if flaps are at 2  command "set flaps 2" should yield no action". If he's moving it, it's an indication he's not reading the current lever position.

Eventually, check with Fenix default livery, as you really never know with those freely available liveries.

I assume you don't have a hardware simpit with a flap lever.

 

no i dont have a simpit flap lever

i will test further and report back , but whatb about the APU issue? also when asking for the bird the fo replies but does nothing

not sure how can i help , let me know if i can send log files or anything

23 hours ago, ayousry said:

no i dont have a simpit flap lever

i will test further and report back , but whatb about the APU issue? also when asking for the bird the fo replies but does nothing

not sure how can i help , let me know if i can send log files or anything

"birdie on/birdie off" bug confirmed. Will be fixed in revised "Simco64_Ldr.exe". Thanks for reporting this.

Haven't found anything unusual with APU. Fo can track it accurately, with multiple start/shutdown commands.

Just a reminder, for smooth operation we do recommend you set the complex plane as the one MSFS loads on startup, even though starting from V3.0.3.2 it's not absolutely necessary.

Once MCE is up and running, wait for about 45 seconds until you see the FO's left armrest salute which indicates he has gathered all the custom variables he needs to interact with. So maybe you asked for APU start before that happened.

Plane version used is 1.0.6.146 (I assume there is no other Beta out there you may be using)

 

On 4/12/2023 at 4:16 PM, ayousry said:

no i dont have a simpit flap lever

i will test further and report back , but whatb about the APU issue? also when asking for the bird the fo replies but does nothing

not sure how can i help , let me know if i can send log files or anything

Get this patch and manually replace 3 files in MCE installation folder. "show the bird/hide the bird" should work with Fenix now.

It's possible to select which exact call-outs you need with a new [CALLOUTS] section in mce.ini

New users will get it on first installation. In your case, you need to add the section manually unless you restore MCE to factory settings. See the other thread

 

amazing quick support as usual, i will try it and report back

 

thanks