Can anyone explain what MCE is failing on here? I get this dialog with at least half of the aircraft I try to fly, and then MCE shuts down. The dialog tells me to send my aircraft.cfg to MCE support, but so far today that would be eight CFG files to email (listed below). My usual go-to aicraft is the Realair Scout, and just to compound things, I have had the MCE demo and the paid-for version working with the Scout so I am sceptical that the aircraft.cfg is solely to blame. I have attached the scout's aircraft.cfg to this message anyway.

 

Does anyone else have this problem? I have found the following a/c won't work (won't work at all - i.e. I'm not concerned about the odd switch or function that doesn't work, I'm only using this for ATC at the moment):

 

Realair Scout

Flight Replicas Super Cub Ultra

Flight 1 BN-2 Islander

Uiver Team X DC-2

Lionheart Pasped Skylark

A2A J3 Cub

Gold Age Simulations Ryan PT-22

Virtavia Rutan Long-EZ

 

Thanks.

 

MarkH

So the Scout works ok but the rest don't? That is really strange...I was going to suggest re-checking the usual..."dialog mode" and also that the MCE.dll folders are in place?

 

One of the guys in the FS++ team will hopefully help you out soon.

_Hi,

 

_{Sorry to hear you haven’t been able to use MCE with the above aircraft.}

_{We don’t like messing with the original aircraft.cfg and Panel.cfg files.}

_{There are occasions where one of these doesn’t present the data in the format MCE expects it.}

_{Example, working out the various flaps detents can be tricky sometimes.}

_{Instead of modifying the original file (with potential unwanted consequences to the aircraft), we ask the user to send the file. We then create a shadow copy (a reference file that sits inside \MCE\Reference\ folder), which is modified to suit the MCE format.}

_{MCE will then be able to load. Of course it doesn’t mean the aircraft is fully supported. But the ATC feature will work with any aircraft in the Ultimate Edition.}

_{May I suggest you send “aircraft.cfg” (for every aircraft that comes up with the message) via e-mail, so we can make a reference file for it?}

 

_Thanks

_{May I suggest you send “aircraft.cfg” (for every aircraft that comes up with the message) via e-mail, so we can make a reference file for it?}

 

I will do as you ask, although I'm still confused about why the Scout will sometimes work and sometimes not. Would it not be possible to publish the aircraft.cfg format MCE is expecting so we can also do this independently?

 

Please could you (or someone) tell me which email address is appropriate, as I only have the 'register@...' one.

 

ta.

 

So the Scout works ok but the rest don't? That is really strange...

 

Sorry, that was unclear. The Scout currently doesn't work but has worked in the past. It worked with the demo (sometimes) and yesterday it worked with the paid-for (Ultimate) version for a while. Then it stopped working and today it doesn't work at all :(

Please could you (or someone) tell me which email address is appropriate, as I only have the 'register@...' one.

 

support(at)multicrewxp.com

 

although I'm still confused about why the Scout will sometimes work and sometimes not

 

Sometimes within the same "aircraft.cfg" file, you'll find different variations of the aircraft, using different "sim=whatever_sim" under [Fltsim.X] sections.

 

The workaround file would be typically called "whatever_sim_ref.txt".

support(at)multicrewxp.com

Sometimes within the same "aircraft.cfg" file, you'll find different variations of the aircraft, using different "sim=whatever_sim" under [Fltsim.X] sections.

 

Okay, thanks. I will send the Scout and a couple of others as an experiment.

Mark, I am having the exact same issue. So far we have got nowhere with it. It fails with every add-on a/c except the PMDG. Real Air, Carenado, Digital Aviation, all no good. Failing somewhere with the aircraft recognition.

 

When it works, as with the default Cessna, everything works perfectly.

 

Still Stumped

 

Dave

Still Stumped

 

Hi Dave, after much work with tech support last week I think we have established that the specific reported issue ('failed to retrieve current aircraft information') is a red herring. It looks like there may be an elusive bug, possibly involving multi-threading, that shows up on my system. Possibly on yours too. I would encourage you to email tech support - if they have two test systems it may be easier for them to track it down!

I have been back and forth with MCE support for a week or so. It's very funny that it ONLY fails with add-on aircraft, and works perfectly fine with everything else though, don't you think? You can see my pc and sim specs in my profile, I was wondering if there was something we had in common.

 

Since I NEVER fly the default a/c I'm in a bit of a pickle, though it works as advertised in the PMDG.

 

Dave

Mark, any news on this problem? I'm still stuck with some a/c working, most not?

Mark, any news on this problem? I'm still stuck with some a/c working, most not?

 

Hello Dave, no change here. I went through several more iterations of test versions but nothing changed except the precise details of how the failure showed itself. I also tried running without any of my addons but no difference. It's a bit disappointing, although I'm only really interested in experimenting with ATC. I couldn't see any great similarities between your setup and mine, by the way.

Still trying to identify a common factor for the failures. I guess if I didn't have so many add-on aircraft it might not be so bad.

 

Dave

I too have been having the same problem. MCE works with all default aircraft, but refuses to work with addon except a select few. I also occassionally get an error that MCE is unable to find FSInsider.dll which when I checked is present. Also noticed my VOX ATC now takes an long time to initinalize Don't know if the two problems are related This all started with version 2.5. Tech support has been stellar in trying to assist with this problem, but just have not been able to resolve the issue.

Sorry guys.

 

This has been a tough one to nail down.

 

What we know so far…

 

All 3 users affected have FSX installed to a “F:” drive.

 

We know one of them has a Sandy bridge set-up.

 

There’s an element of randomness in it.

 

While Dave has it working with the NGX and DC-9 and failing on some Carenado aircraft, James can’t get it to run with the NGX.

 

And to make matters worse, none of the users is in a position to re-install FSX to another drive due to the sheer number of add-ons involved.

 

One should never discard the possibility of a random IO failure.

 

A while ago, there was some issue with a particular SATA port on the Sandy bridge platform. Not saying it is the issue, but one worth keeping in mind.

 

Would appreciate if the 3 users affected could list the chipset they are using as well as the hard drive make and model.

 

To James…

 

Do you have an older (prior to 2.5) version that loads with any aircraft? In which case we can use it as a reference.

 

Thanks.

My chipset is Intel Core i7 x990 @3.47GHz Hard drive Seagate ST 310005 24AS SCSI. Unfortunatley do not have version prior to 2.5 When I downloaded 2.5 I replaced the previous version. It did work prior to 2.5, but I 've added more add-ons since the last time I ran before 2.5. I've tried to figure out if any new add-ons has made a significant change to FSX. I find it's weird that none of the default aircraft are affected and a select few of my add-ons work ok. Racking my brain trying to figure out what's differnet between the add-ons that do work and the ones that don't