V2.6.2.2

 

Transponder standby on the Majestic Q400 doesn't work. On the transponder ta/ra command the FO correctly uses the radio panel popup and performs the necessary long key press. For the standby command, he doesn't do this anymore.

 

Current workaround: Command ta/ra again.

 

Forgot to add: Plane version reads 1.011 PILOT (should be the latest)

 

If you have "mcmjq400.dll" V1.0.2.4, that's already in synch with Q400-1.011

 

FO definitely can see whether it's in standby or ON. Could be to do with simulated click not held down long enough. Normally 2 seconds or so does it.

 

For instance, when you say "transponder standby", and it happens to be already in standby, the ARCDU panel won't pop-up. You may need to repeat either command if the first click fails.

 

Let us know if it happens too often (need to repeat), and we'll do something about it.

I use MCE under P3Dv2.4. 

 

I often use the sims native ATC when I practice touch and go or VFR. I use 3 monitors.

 

Each time I press push and talk button, the ATC window shows up very shortly on one place (on a moniter) then move to and stay on the place where I placed before (on another monitor). Sometimes after I talk to ATC and I close the ATC window, the window pops up again. 

 

Is there any way to avoid this strange behavior of the ATC window when using MCE?

 

Many thanks for the great support.

 

The strange ATC window behaviour is something to do with P3D. It was much better as a transparent window.

 

We have added an option to minimize the amount of drawing that ATC window does.

 

Go to \Prepar3D V2\ installation folder and open "fsInsider.ini"

 

Look at [Prepar3D] section.

 

Change "ReduceAtcFlicker=0" to "ReduceAtcFlicker=1" and save the file.

 

There should be less flickering when the ATC window appears on the screen.

I've been using MCE very successfully with PMDG 747 and recently PMDG MD11.

 

But with both planes, FO calls out "Localiser alive, Glideslope alive" even though it's only the localiser.

 

Even worse, sometimes he keeps repeating this over and over, until Glideslope capture.

 

Any comment, please?

I've been using MCE very successfully with PMDG 747 and recently PMDG MD11.

 

But with both planes, FO calls out "Localiser alive, Glideslope alive" even though it's only the localiser.

 

Even worse, sometimes he keeps repeating this over and over, until Glideslope capture.

 

Any comment, please?

 

Those call-outs apply to all aircraft.

 

When LOC needle goes under 2 dots (read via FSX SDK), FO will typically say "localizer alive".

 

If at some point the LOC signal is lost or deflection goes above 2 dots, the call-out is reset. Which means you may hear it a second time, or even a third time.

 

This can happen on a non-stable approach.

 

Will check why "Glide slope alive" came on with LOC only.

Many thanks for your very quick response.

 

FO repeats himself many more times than two or three!

 

Next time I'll take a note of the localiser level but I believe it was stable.

Confirming, I've just "flown" into Gatwick 08R in the PMDG MD11 and, even though fully established, FO keeps repeating "Localiser alive, Glideslope alive" at least 8 times whilst on short final approach!

Confirming, I've just "flown" into Gatwick 08R in the PMDG MD11 and, even though fully established, FO keeps repeating "Localiser alive, Glideslope alive" at least 8 times whilst on short final approach!

 

OK, thanks.

 

Will do something about it in next update.

That's great. :smile:

 

Once again your customer service is second to none!

That's great. :smile:

 

Once again your customer service is second to none!

 

Thanks Tight Git

 

New package uploaded today.

 

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

Wow, that's sensational; downloading now!

Hello.

I have the version 2.6.33

The issue is for PMDG 777:

 

Flaps

only flaps up works fine.

The commands "flaps 1, flaps5, flaps15, flaps20, flaps25, flaps30 or full flaps" does not work, copi says the command but nothing happend

 

Logo lights

Logo lights ON works

Logo lights OFF does not works (copilote says logo lights swith off already)

 

Everything else is just perfect and great!!

Thanks for your reply

Pascal

This isn't the best topic to place this question, but I didn't think it was worth starting a new topic.  I was reading a post a few minutes ago that was discussing the decrease in fps that occurs in FSX when the mouse cursor is on the screen.  I've noticed that when the MCE copilot is flipping switches, the cursor will appear (or the hand in a PMDG airplane) even though I'm not moving the mouse, and there is a slight drop in fps just because of the cursor being displayed.  Is this simply unavoidable because of the way FSX is designed, or can something be done about it on the MCE side to stop that cursor from appearing? 

This isn't the best topic to place this question, but I didn't think it was worth starting a new topic.  I was reading a post a few minutes ago that was discussing the decrease in fps that occurs in FSX when the mouse cursor is on the screen.  I've noticed that when the MCE copilot is flipping switches, the cursor will appear (or the hand in a PMDG airplane) even though I'm not moving the mouse, and there is a slight drop in fps just because of the cursor being displayed.  Is this simply unavoidable because of the way FSX is designed, or can something be done about it on the MCE side to stop that cursor from appearing? 

 

No, not exactly unavoidable because of FSX design. One can at least try to minimize the impact.

 

Think of all those controls in VC as child windows. The more you have, the worse the performance impact is going to be.

 

Aircraft builders get to decide how many mouse events a particular gauge or control on a gauge will listen to, and what cursor shape the mouse pointer should take when that happens.

 

The simpler is to only listen to "left click". Many buttons (the ON/OFF type) don't need more than that. But items like FCU controls would typically also require to listen to "right-click", "mouse scroll". And the worst is probably "mouse move".

 

Now picture this....

 

If every control in a rich VC is set to listen to "mouse move", then .......lots of unnecessary "mouse move" events are being fired as the mouse moves over any of them. Every event needs to be processed, even though it would most of the time end-up being discarded when the control doesn't do anything with that event.

 

Our interfacing of the PMDG NGX and 777 is constrained by the fact we have to use their SDK (nothing wrong with that). It is essentially simulating mouse clicks on controls.

 

Nothing we can do about it.

Airbus 320 of all flavours

 

Before start checklist

Windows and Doors .... Closed

 

Does not recognize any command except reply with item.

Metroliner

 

Battery ON/OFF command just move the switch in the cockpit but the action is not executed

I means if I mouse click on the battery, the switch not only move but the electricity is on, as well. it is not the case with the MCE command

 

I did not find a command for the "nose wheel steering" ARM/OFF. Does it exist? I tried a few possibilities without sucess

 

Everything else is just perfect. Thank you very much  :smile:

Cheers

Pascal

Metroliner

 

Battery ON/OFF command just move the switch in the cockpit but the action is not executed

I means if I mouse click on the battery, the switch not only move but the electricity is on, as well. it is not the case with the MCE command

 

I did not find a command for the "nose wheel steering" ARM/OFF. Does it exist? I tried a few possibilities without sucess

 

Everything else is just perfect. Thank you very much  :smile:

Cheers

Pascal

 

You're welcome.

 

Some voice commands are only enabled for supported aircraft that have it,like PMDG 737 NGX. Probably an oversight.

 

Will also get the battery switch checked.