I think I can even confirm with better accuracy that the problem is the HOTFIX and not the MVSCR errors that people are getting.

I went into My Documents/Flight Simulator X Files/AerosoftAirbusExtended and randomly opened up "NavData.ini"

In there I noticed the following script:

[NavData]

useNavDataPro=1

pathNavDataPro=NavdataPro\NavData\

pathNavigraph=Navigraph\NavData\

//Remark:

//All paths are relative from FSX main folder!

//useNavDataPro=1loads NavDataPro database

//useNavDataPro=0 loads Navigraph database

I tried changing "//useNavDataPro=1 loads NavDataPro database" to 0 and the one below it to 1 because I use Navigraph, and I was still able to recreate the Westbound runway departure CTD out of KLAX. Doesn't even matter which SID you choose.

Food for thought... plus, perhaps one of the guys from the dev team can report back if its crucial to change the 1 and 0 in the coding if you are not using Navdatapro and are using Navigraph instead?

The reason I ask this is because when I go to install the "NAVIGRAPH 1213" cycle, it installs it automatically to "FSX Main Folder/NavdataPro/NavData" and not "Navigraph/NavData" as suggested by the INI File? Is this an error made by Navigraph? Because its kind of coincidental that Navigraph is installing their cycle into what is supposed to be the NavDataPro folder... right?

Another interesting point,

when I go to FSX Main Folder/NavDataPro/NavData/PROC and open up "KLAX.txt" I get this set of codes. Can Aerosoft confirm if there's something wrong with the way this code is written?

SID,LOOP6,24L,1

VA,0,249.0,2,530,0,1,0,0,0,0

VR,0,SMO,160.0,250.0,3,3000,0,1,0,0,0,0

VM,0,0,0,250.0,0,0,0,1,0,0,0,0

DF,LAX,33.933145,-118.432006,1, ,0.0,0.0,2,10000,0,1,0,0,0,0

SID,LOOP6,24R,1

VA,0,249.0,2,530,0,1,0,0,0,0

VR,0,SMO,160.0,250.0,3,3000,0,1,0,0,0,0

VM,0,0,0,250.0,0,0,0,1,0,0,0,0

DF,LAX,33.933145,-118.432006,1, ,0.0,0.0,2,10000,0,1,0,0,0,0

SID,LOOP6,25L,1

VA,0,249.0,2,530,0,1,0,0,0,0

VR,0,SMO,160.0,250.0,3,3000,0,1,0,0,0,0

VM,0,0,0,235.0,0,0,0,1,0,0,0,0

DF,LAX,33.933145,-118.432006,1, ,0.0,0.0,2,10000,0,1,0,0,0,0

SID,LOOP6,25R,1

VA,0,249.0,2,530,0,1,0,0,0,0

VR,0,SMO,160.0,250.0,3,3000,0,1,0,0,0,0

VM,0,0,0,235.0,0,0,0,1,0,0,0,0

DF,LAX,33.933145,-118.432006,1, ,0.0,0.0,2,10000,0,1,0,0,0,0

SID,LOOP6,DAG,3

IF,LAX,33.933145,-118.432006, ,0.0,0.0,2,10000,0,1,0,0,0,0

TF,KEGGS,34.008447,-118.299592,0, ,0.0,0.0,0.0,0.0,2,13000,0,1,0,0,0,0

TF,COOPP,34.121128,-118.100533,0, ,0.0,0.0,0.0,0.0,2,15000,0,1,0,0,0,0

TF,DAG,34.962459,-116.578167,0, ,0.0,0.0,0.0,0.0,0,0,0,1,0,0,0,0

Because if NOT? It's definitely AIRBUS X that's causing the error. The above codes are from the NavDataPro path in the FSX folder. Although this might mean nothing as according to my discovery above the Navipgrah is installing their cycle into the NavDataPro folder.

Not wishing to downplay your findings Eisa but I had not installed the hotfix and yet I still had the CTD experienced by others here. I can confirm that the westbound LAX departure crashes but I also get a crash rotating off eastbound runways.

Just to confirm, I had no hotfix installed, just the version as downloaded from the server. I have not modified or updated the FMGS navdata either, just downloadd after purchase, installed and flew (or at least tried to).

Not wishing to downplay your findings Eisa but I had not installed the hotfix and yet I still had the CTD experienced by others here. I can confirm that the westbound LAX departure crashes but I also get a crash rotating off eastbound runways.

Just to confirm, I had no hotfix installed, just the version as downloaded from the server. I have not modified or updated the FMGS navdata either.

It's all good, not downplayed at all. We are all trying to find the cause of the error. Good to know its something to do with the Airbus X programming itself and not the Hotfix then. Obviously you are recreating the same errors as people with the hotfix. I have looked at the Nav Database and done a cross reference to see if anything abnormal stands out between other airports and LAX, and I can't find anything. So there must be some form of a communication error or coding error between how the information from the Database is transferred to the FMGS when we select these specific departures. I definitely have no problems departing LAX Eastbound. Perhaps you have a LAX addon scenery?

What makes me believe stronger and stronger that this is a coding error between the information available and how the information is retrived by the FMGS is that yesterday I loaded up the YWT4 arrival into CYYZ, and the FMGS did not retrieve the waypoints. When I went into the PROC/CYYZ section of NavData folder in FSX, all the waypoints, altitude restrictions, and speed restrictions were laid out verbatim. So they are there as part of the procedures section, but the FMGS won't load it up. This is what makes me believe more and more that its a coding issue in how the FMGS retrieves the information than it is any of these DLL files that Mathijs is directing us towards fixing. I do realize how ever that Mathijs has had some success with people fixing this file and their respective CTD's getting fixed. But I think this LAX departure and my new finding of the YWT4 arrival into CYYZ are new CTD's that reveal coding issues in the FMGS.

As proved by the script below from the CYYZ.txt found in the PROC section of Navdata in FSX main folder.

STAR,YWT4,23,6

IF,YWT,43.458583,-80.379383, ,0.0,0.0,0,0,0,1,0,0,0,0

TF,ROKTO,43.509750,-80.191078,0, ,0.0,0.0,0.0,0.0,4,16000,14000,1,250,0,0,0

TF,PENGO,43.600556,-79.847222,0, ,0.0,0.0,0.0,0.0,0,0,0,1,250,0,0,0

TF,ERBUS,43.749233,-79.722033,0, ,0.0,0.0,0.0,0.0,2,6000,0,1,220,0,0,0

TF,DAVIK,43.841292,-79.588100,0, ,0.0,0.0,0.0,0.0,3,5000,0,1,200,0,0,0

TF,LEVIG,43.921231,-79.471245,0, ,0.0,0.0,0.0,0.0,1,3000,0,1,200,0,0,0

FM,LEVIG,43.921231,-79.471245,0,YWT,0.0,0.0,57.0,0,0,0,1,0,0,0,0

As you can see all the waypoints, altitude, and speed restrictions are in the Nav Database. SO it's not a database issue - it looks like a coding issue in the retrieval of the info by the FMGS.

Obviously at this point its all speculation and I'm not sure if its fact. But it seems to really push the direction of coding issues.

Thanks Eisa. I actually run FSX in a moderate configuration, just REX Essential+ and GEX North America. The rest are just a handful of other aircraft add ons.

During my eastbound departure I was able to get as far as programming the FMGS and commence take off. My eastbound CTD occurred just after liftoff when there was no FMGS activity on my part. Incidentally I did not run REX during these initial flights so I presume we cold rule out any conflicts there.

I think your associated CTD is different than the one I am talking about. It's still a CTD that needs to be investigated. Can you try installing the hotfix and see if you can recreate the CTD I'm talking about and to also SEE if you can depart off the eastbound runways with the assigned hotfix?

Thanks!

Hi fernando, you have the same set of errors as I do.

I have tried reinstalling all of my C++ libraries, still get a CTD. I am going to do win 7 system start up repair and see if that will fix anything. I will report back.

Thank you Eisa. I also think the problem is related to MCDU programming but I don't think it has to do with the Hotfix Update because I'm running version 1.0 since I reinstalled Airbus X Extended and I'm still getting CTD errors. At least until now all the CTD errors I got happened while I was testing the MCDU.

Ok great! Looks like we are narrowing the problem down to the fact that its the MCDU programming. The nav data base is complete and has no problems, and the CTD is occurring regardless of hotfix. This is great piece of information I'm sure aerosoft will appreciate in helping their findings.

Summary:

- Nav data looks great

- MCDU fails with and without hotfix out of KLAX

- YWT4 arrival has proper entries in the database, yet not retrieved by the FMGS when selected.

Eisa, will try this and report back.

Adding to all of this - I am going to try "windows 7 startup repair" to evaluate if with the MSVCR80.dll fixed, the CTD's still occurs. Seems like the fix provided by Mathijs in his link (http://pcsupport.abo...ssing-error.htm) has solved some CTD issues. Perhaps it solves issues alike the ones you had departing eastbound RENESIS? I personally don't think it will solve the issues of the FMGS retrieval of SID/STAR info related CTD's cause it is scenting like its a coding issue anyway. But worth a shot anyway.

Ok. Without trying to sound naive though I notice that my CTD error report after the eastbound departure is similar if not the same as those posted by others following MCDU input. I experienced the same error when making MCDU inputs for a 24L departure from LAX.

I am going to try something from KSEA.

KSEA should work. I still think your CTD is different than the ones regarding the MCDU because you are actually taking off. Unless something is happening in the MCDU such as a waypoint cycled. If you delete the "MANUAL" out of the FPLN and get rid of FPLN Disc's and depart on a heading of 070 instead of managed mode, do you still GET the CTD? What I'm trying to see is if you depart with the Airbus Logic not depending on managed mode, if you get CTD. Cause if you DON't get CTD in selected mode (where your SPD, HDG are not dashes, but numbers), then that's even more confirmation that there's something in the CODING of the MCDU/FMGS causing these CTD's.

I left "manual" in the legs. I cleared the discontinuity.

I will try another 07L departure on a 070 selected heading. Will try now.

Just to check, this will be a departure off 07L LAX with selected speed and heading. It will be version 1.0. It will also be a fresh reinstall of abe

OK. First attempt off 07L with selected speed and heading. CTD exactly as before - just after rotation:

Problem signature:

Problem Event Name: BEX

Application Name: fsx.exe

Application Version: 10.0.61637.0

Application Timestamp: 46fadb14

Fault Module Name: MSVCR80.dll

Fault Module Version: 8.0.50727.6195

Fault Module Timestamp: 4dcddbf3

Exception Offset: 00008aa0

Exception Code: c000000d

Exception Data: 00000000

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 2057

Additional Information 1: e926

Additional Information 2: e9263950142051511ceadcb55c0aa80c

Additional Information 3: e103

Additional Information 4: e10379e45c3b67c11759709204013043

Next try will be with clearing "manual" from the legs.

Stby..........

OK. Success this time....so far.

Conditions:

07L departure KLAX

FMGS setup

Selected speed and Heading

"manual" deleted from legs.

Can confirm that leaving "manual" in the legs page seems to cause the CTD.

I'm not very Airbus orientated yet so is manual the other term for "vectors"?

There is something definitely not right with the GMN4 departure off 07L if you leave "manual" in the legs page. However, if you do the SLI departure you can leave "manual" in.

My knowledge is far inferior to many people on here so I will leave it to those who know better. I hope my findings help.

Somehow it seems to be related to some specific SID/STAR selections at the Arrival / Departures page. I repaired the FSX installation to fix eventually corrupted files but the problem still persists. I tried to select a different SID this time and the problem didn't happen but when I selected the previous SID the problem occurred. I can always reproduce the crash by doing the following:

FSX - Free Flight - Airbus Extended Aircraft - SBGL for Current Location - Fly Now

After the simulation starts

Fill in INIT page of the MCDU (SBGL/SBSP at FROM/TO field for example) - Go to Flight Plan page (F-PLN) - Select SBGL - Departures - 33 - MOTO1A - Insert

And then FSX crashes every time for me. If I choose a different SID sometimes it doesn't crash.

I written a more general text ion CTD's, perhaps it helps some people:

http://forum.aerosof...es/#entry433895

Mathijs...why are you advising people to check that the Visual C++ 2008 and 2010 redistributables are installed and not corrupt, when MSVCRT80.dll is a component of the Visual C++ 2005 environment and redistributable package?

Also, it has to be noted that a crash with MSVCRT80.DLL as the faulting module does not necessarily mean that there is a problem with the library--a bad function call from errant panel code can (and often does) cause a fault to occur within a runtime lib module's code.

Regards

Bob Scott

At first I had no CTD but after installing the hotfix every flight ended with CTD around acceleration height. The event log showed MSVCRT80.dll as the reason for the crash on all occations. Based on Kok's hint I browsed the website http://pcsupport.abo...ssing-error.htm.

I know I had all my systems updated so the only thing I could do based on these advices was to clean the registry. I uninstalled, cleaned the registry with Ccleaner, reinstalled (also the hotfix) and since then no CTD. Airbus will rule my skies this christmas.

At first I had no CTD but after installing the hotfix every flight ended with CTD around acceleration height. The event log showed MSVCRT80.dll as the reason for the crash on all occations. Based on Kok's hint I browsed the website http://pcsupport.abo...sing-error.htm.

I know I had all my systems updated so the only thing I could do based on these advices was to clean the registry. I uninstalled, cleaned the registry with Ccleaner, reinstalled (also the hotfix) and since then no CTD. Airbus will rule my skies this christmas.

Weird - I can't seem to repair my windows 7. So I guess that's out the window. I'm not going to reformat my entire drive just to find out that I was right about the MCDU coding being messed up. Considering that this is the only addon causing this issue as well.

I'll try the registry cleaner as well and see if it works. I have ccleaner too.

OK. Success this time....so far.

Conditions:

07L departure KLAX

FMGS setup

Selected speed and Heading

"manual" deleted from legs.

Can confirm that leaving "manual" in the legs page seems to cause the CTD.

I'm not very Airbus orientated yet so is manual the other term for "vectors"?

There is something definitely not right with the GMN4 departure off 07L if you leave "manual" in the legs page. However, if you do the SLI departure you can leave "manual" in.

My knowledge is far inferior to many people on here so I will leave it to those who know better. I hope my findings help.

There you go - departing with the MCDU requiring to cycle to MANUAL after you leave the runway environment seems to be what's causing the Crash. There's definitely got to be something in the coding of the MCDU/FMGS that causes these crashes. If you try 25L/R or 24L/R and with ANY SID, I promise you should be able to recreate the CTD again even with the hot fix.

Somehow it seems to be related to some specific SID/STAR selections at the Arrival / Departures page. I repaired the FSX installation to fix eventually corrupted files but the problem still persists. I tried to select a different SID this time and the problem didn't happen but when I selected the previous SID the problem occurred. I can always reproduce the crash by doing the following:

FSX - Free Flight - Airbus Extended Aircraft - SBGL for Current Location - Fly Now

After the simulation starts

Fill in INIT page of the MCDU (SBGL/SBSP at FROM/TO field for example) - Go to Flight Plan page (F-PLN) - Select SBGL - Departures - 33 - MOTO1A - Insert

And then FSX crashes every time for me. If I choose a different SID sometimes it doesn't crash.

Yea, there's the issue. In your CASE it seems to be a SID causing the CTD. In the case of the KLAX scenario it seems to be that all westbound runways aren't configuring with the SID. Seems like an MCDU issue. It might default to the MSVCR80.dll file mentioned above, but I doubt its because of a corrupted .dll file. I think its due to a coding disagreement somewhere in how the MCDU retrieves data causing the CTD. Just like how it wouldn't retrieve the data from the YWT4 STAR into CYYZ even though in the nav database the appropriate waypoints, speed, and altitude restrictions are evident.

Hope aerosoft solves this. It's actually pretty annoying lol.

OK everybody!

I've got some great updates. I reinstalled Windows 7 on my computer. Clean FSX install. Airbus with NO HOTFIX and the original Nav Data Pro that comes with it. NO KLAX CTD.

Updated the database using Nav Data Pro - NO KLAX CTD

Installed Hotfix 1, when reloaded aircraft was asked to accept FMGS.dll as trusted, so I said ok. = KLAX CTD

Hopefully this provides some excellent feedback on the CTD error's. Obviously it can't be the associated MSVCR80.dll file as I have a fresh new copy of Win 7 and FSX with no other addons installed.

Something was obviously not coded quite right in the hotfix released regarding the FMGS, and I bet you anything that's whats causing these CTD's.

It's important to note that I installed the Airbus X Extended as an administrator on both accounts (With and Without Hotfix)

All the best,

Eisa

Airbus no hotfix is supposely no CTD but overrall NICE !

How you update the database must buy?

I will even confirm further that without the hotfix I was able to retrieve the YWT4 arrival into CYYZ with all the applicable waypoints, altitude, and speed restrictions. This was impossible with the hotfix.

Guys... obviously something got messed pretty bad in your hotfix with the FMGS. Hopefully you'll fix it.

Eisa, don't forget though that I too had CTD'd with NO hotfix installed so it is important to state these are occurring WITH as well as WITHOUT the hotfix - i deliberately delayed applying the hotfix having read the posts on here. Also, if i even try to input westerly departures I get instant CTD's - all with V1.00!

Eisa, would you kindly try a departure off 07L at LAX, selecting the GMN4 departure, and leave "manual" in the flight plan page. I am curious to see if this causes a CTD and particularly just seconds after rotate as it religiously does for me. Then if you go back and do the same thing but clear "manual" does that work? Maybe the hotfix cause the "rotation" CTD to go away but causes CTD's elsewhere like at the Acceleration Height as has been mentioned?

Otherwise, I too uninstalled Airbus X Extended, cleaned registry with an up-to-date version CCleaner, rebooted and reinstalled again..............and clearly this did not fix the problem in my case. I am unable to do a windows reinstall as this would be a mammoth task and I think since my PC performs faultlessly in ALL other respects I don't see why I should.

. I am unable to do a windows reinstall as this would be a mammoth task and I think since my PC performs faultlessly in ALL other respects I don't see why I should.

You do not have to re-install anything for us.

But fact it that this product works for thousands upon thousands of systems and not on a few. Some of those few issue have been sorted and for all of those it was clear that the issue was not related to the Airbus X Extended but to windows files. So we have to conclude the problem is with your system and not the software (again, it works on over ten thousand systems and not on yours). I understand you are upset about that, and we will continue to research the issue, but as it just works for us and we do not see the error you have on your system, this is simply very hard. There are issues we can recreate and those we are fixing.

But please accept that if you do a clean install of Windows, FSX and Airbus X Extended all will work. I am not saying you should but that is the only thing we can guarantee.

sad to see this,good luck guys tmr is Xmas ><

Mb own a ssd will be good.I suggest samsung.I have 1 myself any problem just format and isntall window no lost everything in the hard drive

Since u mb reinstalling windows.Try install fsx in another place not in the C: i have mine in my hdd.So there is no conflict between the uiautomationcore.dll.

Never had crash so far with my new sdd and fsx on a hdd and no enb.its good but it also causes crash as well use this instead same as enb i assure you.(fxaa injector) previous version works with FSX but it cant found on their offcial web,i have the files so i uploaded.

http://www.mediafire...vhu29lgnbnvbq5a password iamniceify

hope you fix your crashes hapyp marry xmas