The A2A Simulations Community

Tried reloading All P51 probrams, including the "core up date". Now I can't "repair" either the P40 or P51 and get the "nil" error!!!!

Try making the default plane the Microsoft Microlight.

Close FSX and reboot PC and restart FSX so now it shows the Microlight every time you start FSX.

Now do you have the problem ?

A restart is most important during this kinda of stuff as it allows the system to correctly register files. Alot of issues reported to me via email is because users are installing a bunch of stuff and not restarting the system before use. Its a bit old school, but it still applies to most modern computing.

_________________
A2A Facebook for news live to your social media newsfeed
A2A Youtube because a video can say a thousand screenshots,..
My twitter for my own twitter and random A2A insights

Not the case with the gents I fly with who have this problem!!! It is a bad BUG! Lets get it fixed!

Please read my post above and tell me if it did or did not work.

Also try removing the FSXAccusim.dat and p51log.dat files with a complete restart of your PC.

Note the Microsoft Microlight should be the default everytime - not an A2A issue an FSX issue.

If however what I wrote above does not work then it may be an A2A issue.

Currently I am guessing it isn't an A2A issue.

Hi Shousa!

My default flight is the ultralight since the beginning. I also tried deleting the p51log.dat with no success.
But I havent tried deleting the Accusim.dat. I will try that later. But until now, nothing helped.
I'll report back, when I tried the accusim dat

Cheers

wothan,

What happens if you don't load AS2012?

Scott.

_________________
A2A Simulations Inc.

I only got the error once.
I used AS2012, but had alot of flights (starting with new instances of AS2012 and FSX) without any problems after that.

For me it seemed more like some Accusim dll not being proberly loaded or crashing , since no Accusim sounds where played.
Maybe some OAT or barometric pressure reading.

Definitly not an big issue for me, since it only occured once.

May I suggest for those who have the issue very often to try a different starting location than their default one ?


FinnJ

After deleting the files above, no more error msg. ( and the "Kite" is NOT my default a/c/flight!!!

I too, had the "Attempt to call a nil value stack traceback error".
As some folks had suggested the error was due to a corrupt saved flight, I removed all recently saved flights.
Did not help.
Today, it occurred to me that I had uninstalled "Accu-Feel" a while back, using "Control Panel - Programs & Features" (I have Windows 7 64 Bit). However, Accu-Feel never did go away from the FSX toolbar under "addons".
I didn't think much of it, but I was puzzled as to why it didn't completely disappear from the toolbar.
Well today, I had that "Eureka" moment. I re-installed "Accu-Feel" (as well as the 1.091 update).
Problem solved!
No more "nil value" error.

Loren

I would like to confirm that there is absolutely NO ERROR with Accu-Feel.

First of all the FSX Menu toolbar "addons" will show the "Accu-Feel" feature as long as it is included with your "dll.xml" file where all those add-on are registered like the FSX SDK Toolbox Menu.
Then under the FSX-MAIN Folder there must be the A2A Folder that has a subfolder "feel".
If you want to test/create the error advice just delete the folder "feel" (backup before).

I'm sure the error is not caused by Accu-Sim but with a wrong or corrupted installation.

regards,
friedrich
.

Hi Everyone,

first post on this forum having just bought the B17 Accusim package - fabulous product, I very much enjoy it! However, I appear to have a similar 'nil value stack' error message when I load FSX and the Free Flight screen appears. I just click on the 'OK' button of the error message and it goes away, and I don't seem to have any subsequent problems with flying my B17, but I would prefer to see if I can get rid of it. I was also intrigued to find through this forum that the problem exists on the P51 but no one else seems to have called it up for the B17. Obviously I don't have a P51log.dat file to remove, and I have default aircraft for the start-up flight. Any thoughts anyone?

And, by the way, those of you who had this problem on the P51, what issues did it create? What problems did you encounter as a result of this error message?

Thanks to all.

_________________
Dave

On surveying my precious F4M with a tree branch down the intake: "I thought you called-in with a birdstrike, skipper?" " Yeah, she was sitting on the nest when I hit her ..."

Hello Dave,

he P-51 ans B-17 Accu-sim products are not related as the B-17 is not the current core code. However please check the B-17 forums and make sure you download and install the updates for the B-17.

thanks,
Lewis - A2A

_________________
A2A Facebook for news live to your social media newsfeed
A2A Youtube because a video can say a thousand screenshots,..
My twitter for my own twitter and random A2A insights

Thanks Lewis.

I installed the B-17 updates and the issue is still there.

I have searched all parts of the A2A Forum and the only place where this fault is discussed is in the P51 forum. It does not appear to have been an issue with the B-17 before.

_________________
Dave

On surveying my precious F4M with a tree branch down the intake: "I thought you called-in with a birdstrike, skipper?" " Yeah, she was sitting on the nest when I hit her ..."

Hello,

can I please ask you start a new thread in the B-17 forum so we can better help you.

thanks,
Lewis -A2A

_________________
A2A Facebook for news live to your social media newsfeed
A2A Youtube because a video can say a thousand screenshots,..
My twitter for my own twitter and random A2A insights