On 10/6/2022 at 7:11 PM, threegreen said:

Thanks, seems to work again. I'll report on the FCU dialing once I've flown the A320.

A new patch was uploaded. Should settle the push/pull of FCU rotaries with FENIX (Probably why dialling wasn't woking for you).

Also, restores MCE integration with PMDG through SDK for both read and set, just as it was the case in the first release of the PMDG 737.

No more need to reload the plane and FO always in synch with Vspeeds without the need to input anything anywhere other than CDU.

Only need to replace "Simco64_Ldr.exe"

 

4 hours ago, FS++ said:

A new patch was uploaded. Should settle the push/pull of FCU rotaries with FENIX (Probably why dialling wasn't woking for you).

Also, restores MCE integration with PMDG through SDK for both read and set, just as it was the case in the first release of the PMDG 737.

No more need to reload the plane and FO always in synch with Vspeeds without the need to input anything anywhere other than CDU.

Only need to replace "Simco64_Ldr.exe"

 

I was just about to ask today . Thanks! Does not needing to reload the plane also apply to the Fenix A320?

On 10/16/2022 at 8:52 PM, threegreen said:

I was just about to ask today . Thanks! Does not needing to reload the plane also apply to the Fenix A320?

It's not that MCE mandates a plane reload. Not at all

More like when it detects a specific plane variable isn't accounted for, it prompts for a reload to ensure it is.

With FENIX A320, although not all  the 2200 Lvars are accounted for on first load, all the ones MCE needs get through on initial load anyway. Therefore no need to reload this plane.

Out of the 1800 Lvars most complex planes would have, MCE only nedds about 400 to 500.

FO doesn't need to know by how mucht spoiler surface number 6 is deflecting or how much flex is on the wing.

We don't believe anyone has this level of integration with any plane, even those who say "specifically developed for airplane A".

The reason we are able to claim to support 50 planes (4 already in MSFS not counting other simple planes) in a single package is because MCE development is a 14+ years effort.

Every plane needs about 2 months (for those that have an SDK) to 4  to 6 monthsmonths (for those that don't like FENIX A320).

And we never claim a plane is fully supported until FO is able to handle MCP or FCU, not just some switches. That's where the fun of voice control comes in.

The FO making FMA announcements as they change, is the only thing we haven't had enough feedback on, therefore would appreciate if you or others report on this. Thanks

 

 

 

Edited October 18, 20223 yr by FS++
typo

23 hours ago, FS++ said:

With FENIX A320, although not all  the 2200 Lvars are accounted for on first load, all the ones MCE needs get through on initial load anyway. Therefore no need to reload this plane.

The FO making FMA announcements as they change, is the only thing we haven't had enough feedback on, therefore would appreiate if you or others report on this. Thanks

I haven't tried the newest version yet, but on the previous version I had to reload the Fenix A320 because I noticed my F/O wouldn't properly do his preflight flow. That's what I was referring to.

I have never used the FMA announcement feature as in the airline I like to fly it's the Captain who makes the callout and the F/O just cross-checks that. I'm going to enable the feature on the next flight to see how it works.

6 hours ago, threegreen said:

I haven't tried the newest version yet, but on the previous version I had to reload the Fenix A320 because I noticed my F/O wouldn't properly do his preflight flow. That's what I was referring to.

 

There is one recommendation.

Always set the preferred complex plane you intend to fly as the one MSFS loads on startup.

Do not switch from Say PMDG 737, Flybywire mod  to FENIX or vice versa. All these have huge amounts of Lvars and no plane appears to be clearing them when it gets unloaded.

It's OK to switch from any ASOBO plane to a complex supported plane though.

Can u direct me to this latest patch please, am lost in forums trying to follow all updates !,i was on ver .82 and at least the pmdg737 was working good , i uninstalled and installed ver .83 and now the 737 is all messed up

9 hours ago, ayousry said:

Can u direct me to this latest patch please, am lost in forums trying to follow all updates !,i was on ver .82 and at least the pmdg737 was working good , i uninstalled and installed ver .83 and now the 737 is all messed up

I suggest you re-install the latest available from the Downloads page

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

Even though it says V2.9.8.3 (version is linked to mce.exe version number), other files would have been updated. Especially "Simco64_Ldr.exe"

If that doesn't do it, grab the patch and just replace "Simco64_Ldr.exe" for PMDG 737 & Fenix |320 up to date support.

http://www.multicrewxp.com/Latest-Beta.zip

Always set the complex plane you intend to fly as the one MSFS loads on startup. You should never have to reload the plane.

 

Edited October 22, 20223 yr by FS++

MCE is not working after installing the newest update from Fenix v1.0.6.146. It's initializing and afterwards the well known pop up window wich requests to restart the session comes up again and again. 

3 hours ago, delfin8896 said:

MCE is not working after installing the newest update from Fenix v1.0.6.146. It's initializing and afterwards the well known pop up window wich requests to restart the session comes up again and again. 

The Ultimate edition is going to be updated this week. It's one of the reasons we have temporarily withdrawn the Demo.

Since you have displayed your full name., might be able to send you a direct link to download the patch tomorrow.

 

 

Any news on the status of the new version? Was looking to try the demo to maybe purchase later but it's been unavailable for the past week.

On 11/14/2022 at 3:46 AM, CIKSSFMO said:

Any news on the status of the new version? Was looking to try the demo to maybe purchase later but it's been unavailable for the past week.

Almost done.

Could have been out last Saturday. But then SU 11 came, which would require a few days testing to ensure nothing major is broken.

And there was this little temptation to integrate the Inibuild A310 to a small extent for now, like at least have MCE recognize the plane, assign it the same checklist as the one in EFB, show the FO how to handle gear, flaps, spoilers, external lights, FCU and radios tuning (the most used commands) to start with so he can be helpful with that plane straight away. It will take a bit longer to give him access to 90% of switches on overhead panel.

What's more, the interface to Fenix is now unlikely to require small adjustments when a new update of the plane comes out.

Should be out tomorrow evening UK time.

Edited November 15, 20223 yr by FS++
typos

On 11/14/2022 at 3:46 AM, CIKSSFMO said:

Any news on the status of the new version? Was looking to try the demo to maybe purchase later but it's been unavailable for the past week.

It's now on: http://www.multicrewxp.com/Downloads.html

Anyone going through the Demo, please understand MCE is always works in progress.

If you come across some issue, just get in touch.

There is minimal support for Inibuilds right now. It will be fully supported in future updates.

Therefore, don't see him not controlling the packs as software defect. We can definitely give him access to 90% of the switches. But then, if we did just that right now, people will wonder why the Demo isn't coming out yet.

For now, in MSFS, only PMDG 737, Fenix A320 & Flybywire mod have both Voice & Button control,

Button control will be progressively rolled out to other supported planes, including Aerosoft CRJ, Inibuilds A310 & Others.

IMPORTANT: Whichever supported plane you might be testing with, MUST be set as the plane MSFS loads on start-up, aircraft loaded, ready to fly (in ANY state), before starting MCE.

By the way, MCE FO, only First-officer on the market able to dial everything in Fenix A320. FCU SPD, HDG, ALT, VS, VHF radios, transponder, you name it. The closest you can get to "shared cockpit".

Just saying... 😝

Edited November 15, 20223 yr by FS++

@FS++ Just checked to see if FMA callouts work with the Fenix A320. They don't, I didn't hear the F/O call out any FMA changes. Also, he still sets the ND mode to something other than MAP if told to set it to MAP (not sure what he sets it to right now); this is on the F/O side.

Any plans for adjusting the Vspeed callouts on takeoff? If I go by the F/O I'm about 10 kts past the speed already by the time he calls them out.

1 hour ago, Nixoq said:

@FS++ Just checked to see if FMA callouts work with the Fenix A320. They don't, I didn't hear the F/O call out any FMA changes. Also, he still sets the ND mode to something other than MAP if told to set it to MAP (not sure what he sets it to right now); this is on the F/O side.

Any plans for adjusting the Vspeed callouts on takeoff? If I go by the F/O I'm about 10 kts past the speed already by the time he calls them out.

You probably have an older "Simco64_Ldr.exe"

Get the patch and manually replace all files.

http://www.multicrewxp.com/Latest-Beta.zip

ChangeLog

Improvement to the Inibuild A310 intgration

With Fenix A320, Simco64_Ldr.exe will only start looking for Vspeeds in CDU once at least one engine is running. May take up to 90 seconds

Call-outs should work, but only when the plane is moving. Taxi phase or higher and the feature is enabled in "Advanced options" panel. May need to restart MCE.

Fixes an issue with MSFS Multi-monitor setup.

Patch is only for Ultimate Edition users.

Those on Fenix A320 Edition, please download a more up to date package from Simmarket.

https://secure.simmarket.com/fs-limited-multi-crew-fenix-a320-msfs.phtml

 

6 minutes ago, FS++ said:

You probably have an older "Simco64_Ldr.exe"

Thanks, will try ASAP.