After an extremely laborious reinstall I get an error message {attempt to call a nil value stack trace back] just when the fsx splash screan appears. The only thing it seems to affect is the A2A maintenance hanger leaving my PA180 and C182 Skylane useless since I can't change the battery, auto start or do anything with the aircraft. All others including PMDG seem to work fine. I feel something is wrong with the FSX program {box] rather then the A2A addon. Any one with any ideas? I am running windows ten.  Thanks for any advice.  Vic

I'm a little confused when you say you get the error message just when the fsx splash screen appears.  That indicates to me your FSX is not starting up but then later you say "all others including PMDG seem to work fine" which indicates FSX might be starting up and you are having no problems with PMDG.  It seems to only affect A2A stuff.  If FSX is working with PMDG, then how can you blame the FSX program?

 

Do you have Microsoft Visual C++2005 w/SP1 installed?  Also Microsoft.net 1.1 or 2.0 needs to be installed.  Without those, your fsx splash screen does not appear.  Those programs are installed when you install FSX/Acceleration or SP2. 

 

You can also try moving your fsx.cfg to a different folder, restarting FSX and letting the config rebuild.  It could be something in the dll.xml too that is corrupted.  If you move it to another temporary folder and restart FSX and FSX starts up, then that is the culprit.  If you have any FSDT scenery, it will do this too occasionally and is fixed if you download their latest addon manager.  It's not Windows 10.

 

Whenever you reinstall FSX, you should start it up before installing Acceleration or SP2 and then for each addon installed.  You should never use an old FSX.cfg or file that came with an older installation of FSX.

 

I think your problem is the A2A addon.  Have you tried uninstalling and then running FSX to see if the error reappears?  The whole process requires some type of investigation on your part as your computer is right in front of you and not in front of me or others.  Rebuilding your FSX.cfg fixes a lot of issues as well as investigating whether your dll.xml is corrupted by moving that file to a temporary folder (it will not be rebuilt but at least you can see if it fixes your problem).  You can also just disable any entry in the dll.xml using the technique shown on page 3 of the AVSIM CTD Guide (link in my signature).

 

Best regards,

Hello,

 

From time to time I have (some others have too) the nil value message with some A2A aircrafts. Reload the plane or the saved file and your are good with the stuff.

 

Regards,

 

Richard Portier

I'm a little confused when you say you get the error message just when the fsx splash screen appears.  That indicates to me your FSX is not starting up but then later you say "all others including PMDG seem to work fine" which indicates FSX might be starting up and you are having no problems with PMDG.  It seems to only affect A2A stuff.  If FSX is working with PMDG, then how can you blame the FSX program?

 

Do you have Microsoft Visual C++2005 w/SP1 installed?  Also Microsoft.net 1.1 or 2.0 needs to be installed.  Without those, your fsx splash screen does not appear.  Those programs are installed when you install FSX/Acceleration or SP2. 

 

You can also try moving your fsx.cfg to a different folder, restarting FSX and letting the config rebuild.  It could be something in the dll.xml too that is corrupted.  If you move it to another temporary folder and restart FSX and FSX starts up, then that is the culprit.  If you have any FSDT scenery, it will do this too occasionally and is fixed if you download their latest addon manager.  It's not Windows 10.

 

Whenever you reinstall FSX, you should start it up before installing Acceleration or SP2 and then for each addon installed.  You should never use an old FSX.cfg or file that came with an older installation of FSX.

 

I think your problem is the A2A addon.  Have you tried uninstalling and then running FSX to see if the error reappears?  The whole process requires some type of investigation on your part as your computer is right in front of you and not in front of me or others.  Rebuilding your FSX.cfg fixes a lot of issues as well as investigating whether your dll.xml is corrupted by moving that file to a temporary folder (it will not be rebuilt but at least you can see if it fixes your problem).  You can also just disable any entry in the dll.xml using the technique shown on page 3 of the AVSIM CTD Guide (link in my signature).

 

Best regards,

Thank you for your help Jim. uninstalling my A2A   aircraft and deleting their folders makes the error message go away. Every thing else works fine so it seems to be an A2A bound problem which I hate that I can't use my favorate GA planes. I'll work on it some more tomorrow but thanks for your help. Regards VIC.

Hello,

 

From time to time I have (some others have too) the nil value message with some A2A aircrafts. Reload the plane or the saved file and your are good with the stuff.

 

Regards,

 

Richard Portier

Thank you Richard. I'll try that.

I'm a little confused when you say you get the error message just when the fsx splash screen appears.  That indicates to me your FSX is not starting up but then later you say "all others including PMDG seem to work fine" which indicates FSX might be starting up and you are having no problems with PMDG.  It seems to only affect A2A stuff.  If FSX is working with PMDG, then how can you blame the FSX program?

 

Do you have Microsoft Visual C++2005 w/SP1 installed?  Also Microsoft.net 1.1 or 2.0 needs to be installed.  Without those, your fsx splash screen does not appear.  Those programs are installed when you install FSX/Acceleration or SP2. 

 

You can also try moving your fsx.cfg to a different folder, restarting FSX and letting the config rebuild.  It could be something in the dll.xml too that is corrupted.  If you move it to another temporary folder and restart FSX and FSX starts up, then that is the culprit.  If you have any FSDT scenery, it will do this too occasionally and is fixed if you download their latest addon manager.  It's not Windows 10.

 

Whenever you reinstall FSX, you should start it up before installing Acceleration or SP2 and then for each addon installed.  You should never use an old FSX.cfg or file that came with an older installation of FSX.

 

I think your problem is the A2A addon.  Have you tried uninstalling and then running FSX to see if the error reappears?  The whole process requires some type of investigation on your part as your computer is right in front of you and not in front of me or others.  Rebuilding your FSX.cfg fixes a lot of issues as well as investigating whether your dll.xml is corrupted by moving that file to a temporary folder (it will not be rebuilt but at least you can see if it fixes your problem).  You can also just disable any entry in the dll.xml using the technique shown on page 3 of the AVSIM CTD Guide (link in my signature).

 

Best regards,

Hey Jim! I did the FSX.cfg rebuild and it worked it worked it worked!!! Now my Skylane is flying again! Thanks for your expertise. Best wishes, vic

Hey Jim! I did the FSX.cfg rebuild and it worked it worked it worked!!! Now my Skylane is flying again! Thanks for your expertise. Best wishes, vic

Hi Vic,

 

It's always great to hear a recommendation worked.  You must have had a tweak in there that FSX did not like.  Thanks for your kind words.

 

Best regards,