Classic British Flight Sim

Has anyone had FS9 shut down after declaring this error?

I've had it a few times recently when in the vicinity of London...At the moment I'm enroute from Mylor to Berlin and I had the error twice while passing London and got past in the end by pulling the Traffic slider back to Zero. I'm beginning to think it is a rogue Traffic aircraft and in view of my recent Traffic installations it would have to be in a WOA package. The other possibility is that the error is associated with Aerosoft's Heathrow. It would help to know if anyone else here has had the error...The Sim stops with a small window saying about the error and then when you click OK the Dr Watson window comes up and FS9 restarts with a message sent to MS.

Not had anything like that Peter. The only traffic I am running at the moment is Tantris and some of my own making.

Graham

umm it's as you say either a bad traffic file or as I had, a bad AFCAD and some wayward landclass files

hope this helps

ttfn

Pete

Good to see its not just me Peter. I've had this a few times lately, especially coming out of East Mids. Never quite pinned it down though. As the chaps say, a rogue AFCAD or something is probably the culprit.

I haven't seen it, but I also use "another" sim

But as it is Pure Virtual, I think you should be happy that it's not a "Real Call Error" ....

Error messages....:roll:

-

Thanks for the pointers chaps...I don't have that Traffic-GA.bgl so it can't be that...I did find a reference to Unticking "Use Smooth Scrolling" in the Internet Explorer 7 Tools > Advanced, so I've done that and I'll see what happens :think:

Hi Peter

Me, Tony & DanKH had this discussion recently on the HJG forums as it was happening to me.





It boiled down to an installation of Flight Deck 5, which was promptly removed.

Rgrds

Boeing

Thanks Boeing...That is the exact error but as far as I know, I do not have Flightdeck 5...What is Flightdeck 5?

It did seem to appear after my installation of Aerosoft's Heathrow so I had better go over there and see if there is a user forum :think:

Peter,

The exact error means that the dll file has made a call to another program incorrectly. An example might be where a developer coded a module in (for arguments sake) Visual C++ version 4 and that call is no longer supported in the Visual C++ version 5. Its a bit of a bugger to try and identify, but could be caused by anything (dll / exe etc) which has been either coded incorrectly, or uses old calls. 9 times out of 10 its lazy programing on the part of the developer.