FSLabs A320

[Cubs105]

I know there were issues in the past with the A320 in P3Dv4 where certain functions were not working? Have they been solved or a workaround been discovered? I’m looking at buying the plane and I saw that a new version of MCE was just released. Thanks for constantly updating!

[FS++]

3 hours ago, Cubs105 said:

I know there were issues in the past with the A320 in P3Dv4 where certain functions were not working? Have they been solved or a workaround been discovered? I’m looking at buying the plane and I saw that a new version of MCE was just released. Thanks for constantly updating!

Your welcome.

Check out this thread:

https://forums.flightsimlabs.com/index.php?/topic/15263-multi-crew-software/

Should be ready by the end of the coming week.

 

 

 

[Cubs105]

Can’t wait, I just bought the plane

[RALF9636]

22 hours ago, FS++ said:

Your welcome.

Check out this thread:

https://forums.flightsimlabs.com/index.php?/topic/15263-multi-crew-software/

Should be ready by the end of the coming week.

 

 

 

Would that also be possible for the Q400?

[FS++]

1 hour ago, RALF9636 said:

Would that also be possible for the Q400?

Why not. Haven't checked whether the Pilot Edition has 2D panels though. At least Pro Edition has them. 

 

[RALF9636]

2 hours ago, FS++ said:

Why not. Haven't checked whether the Pilot Edition has 2D panels though. At least Pro Edition has them. 

 

That would be very nice. I would appreciate if you keep me informed.

I just started to learn to fly the Q400 (Pro Edition) and one of my next steps would be to work on some MCE-scripts. But I'd better wait with that until the MCE-FO learns some more switches (instead of working with notify commands now and re-do all the scripts later on) if that is to be expected in a reasonable timeframe.

 

Sorry for going a little off topic here but as far as I understand the FSL Airbus and the Majestic Q400 have the identical problem regarding MCE.

 

[FS++]

12 hours ago, RALF9636 said:

Sorry for going a little off topic here but as far as I understand the FSL Airbus and the Majestic Q400 have the identical problem regarding MCE.

 

Yes, the neat technique we have implemented for FSX to get the Fo to click buttons in VC no matter what you're looking at, even in outside view, has worked very well over the years. It has stopped working after P3D V3.2.

It's not something you find in any SDK. Therefore a lot of poking around (most of it time wasted) is required

We need a breakthrough on that one.

Having said that, it's only those 2 aircraft among 41 fully supported complex aircraft that use it. We also use that technique with PMDG 777 for FO to manipulate the ECL only as even the PMDG SDK won't tell you how to do that.

Should have considered the 2D clicking option much earlier, as it's a well oiled machine.

I'm guessing could be ready for Q400 as early as the end of next week.

Ask Ibomiles for his flows. See related video in this thread (last video). You cannot get more detailed than that 

 

 

[Cubs105]

Any updates on the update that is coming out soon?

[Guest Mik75]

Is it still planned that the new items and bug fixes of the 64bit version will be rolled back to the 32bit platforms as well?

[Cargostorm]

I am on MCE v2747. As I understand, MCE uses the 2D panels to switch buttons as a work-around. If you have created flows with a lot of items by voxscript (e.g. after start items), I get all the popping-up 2D panels if the FO switches the buttons. Is this how it is supposed to be?

I also understand that we can minimise the panel windows such that the popping-up is not that annoying, but I am wondering whether we can expect a "proper" solution. I also understand that FsLabs will not make available the SDK for the developers (which is sad). So does this mean that we have to live with the interim solution for the FSL airbus?

Cheers,

Chris

[sbs9]

If you do not use 2D panels, you can set their transparency to 100% in P3D options. MCE will still open and use them correctly, but you will not see them.

[fyase]

4 hours ago, sbs9 said:

If you do not use 2D panels, you can set their transparency to 100% in P3D options. MCE will still open and use them correctly, but you will not see them.

Yes but unfortunatly on VC sometimes PFD,ND and CDU are used as 2D panel, so set transparency to 100% will affect this items too

[sbs9]

1 hour ago, fyase said:

Yes but unfortunatly on VC sometimes PFD,ND and CDU are used as 2D panel, so set transparency to 100% will affect this items too

As I said: 'If you do not use 2D panels'. I never need them.

If the transparency can be controlled by MCE, setting the panels to fully transparent before opening them and then back to the previous value would be a perfect solution :)

[FS++]

On 2/2/2018 at 11:42 PM, sbs9 said:

As I said: 'If you do not use 2D panels'. I never need them.

If the transparency can be controlled by MCE, setting the panels to fully transparent before opening them and then back to the previous value would be a perfect solution :)

It's still a very good suggestion for many users. Didn't think about it myself. Sometimes simple steps can make a difference.

Here is a slightly refined integration with FSL A320

Users on V2.7.4.7 could just apply this patch by manually replacing files.

Others on much earlier versions, download the full package here

Adjusted the tempo for switching multiple items in a row via 2D panels (was affecting switching of fuel pumps occasionally)

Search algorithm for FCU values refined a bit, as some users still report no HDG and VS control.

.

 

[ggerolamo]

Is the Q400 also working with this patch ?