Yup, that too. I was informed on the support forum that my issue was 'rare', but I would beg to differ given the evidence of this thread. I too have been dilligent in always flying the same route in order to consistently track problems, when what I should really have been doing, was enjoying a product which I paid forty quid for. :lol:

 

Al

Yep. Famous last words. Another crash.FSX froze and I had to kill the sim via task manager.

 

Sorry to hear you're back to looking for a fix. NEA is about the same distance as ROMPO. Your symptoms indicate to me that your system is not getting enough resources. I don't think it's ProATC (even though you stated your system would not freeze up with ProATC uninstalled; ProATCX just added a few more resources to your problem). UT is a known resource hog if not properly configured. Have you ever looked at the settings recommended by NickN in his Settup up FSX and Tuning it - http://www.simforums.com/forums/topic29041.html. It's near the bottom of his thread. I own UT Europe but have not reinstalled it on my new system. This may be the reason why I was able to fly the route you provided earlier and your system was freezing up. Just a thought.

 

Best regards,

Jim

Jim,

 

 

If my system is not getting enough resources why is it then that FSX does not freeze with radar contact,votxatc and pfe ? This is what I ask myself.Proatc is the only software that causes freezes and crashes here.yet.

 

Thanks for the link.I use Nick's guide all the time.

have you tried a default fsx.cfg?

SteveW, yes.

Proatc is the only software that causes freezes and crashes here.yet.

 

I understand your frustrations but I flew the one flight without an issue and it worked for me. There's got to be something else that's taking up your resources. Steve has a great idea. Just rename your FSX.cfg so you can return to it if it doesn't fix the problem. Your flight won't look as pretty but it will help you investigate the problem.

 

Best regards,

Jim

I understand your frustrations but I flew the one flight without an issue and it worked for me. There's got to be something else that's taking up your resources. Steve has a great idea. Just rename your FSX.cfg so you can return to it if it doesn't fix the problem. Your flight won't look as pretty but it will help you investigate the problem.

 

 

Jim,

 

the other ATC progs I own work perfectly here (radar contact,voxatc and pfe). I have the feeling the problem is not on my end.

You have to use a default FSX setup because a program like this requests a load of information from the sim. The sim queues up the data and the program reads it in when it's ready. Other addons doing the same thing can all add up to stress the setup, maybe overburden it, but perhaps not crash it, but it is possible. I've seen scenery crash FSX "when it did not before", simply because I never flew that waypoint before and the scenery needed a service pack. A simconnect program can "Hang" FSX by incorrect implementation, but it's likely to be repeatable at the developer's system. Tweaked fsx.cfg's may be great until another addon is introduced then the tweaking may need redoing - starting from the bare fsx.cfg as Jim says.

Steve,

 

 

You asked me if i tried a default fsx.cfg.I said yes. Again I tried with a "clean" fsx.cfg and no other addons running.With proatc FSX freezes.

 

FSX running with truckloads of addons active and radar contact does not freeze.FSX get along fine with pfe and voxatc as well.

Fair enough if it's got a clash on your system, it's not your responsibility to worry about it. Perhaps the problem will surface in other systems and you can give it another go later.

I have the feeling the problem is not on my end.

 

I have a feeling you are correct. I decided to try your last flight from Lisbon to Brussels. Your system froze at NEA. I had no problems there but I got the following error message around Lusem (about 70 miles later in the flight):

 

 

I had good frame rates over 40FPS. ProATC provided a new heading to heading 34 (I was on a heading of 46). The co-pilot did not respond and a few seconds later, ATC requested the last transmission to be affirmed then the message came up that there was a problem and to close the program. I did not close the program. Instead I put my cursor back on the FSX screen and unpaused the game and the flight continued for a few seconds until ProATC came back and requested the last transmission be affirmed. Then the same error message popped up again. This time I closed the ProATC program as requested. Clicking on the FSX screen, I was able to continue my flight but, without ProATC, I decided to close it too. During the flight I had awesome FPS. Wing views were over 100 FPS. VC frames were much, much lower and hovered between 30 and 50. I had real world weather enabled and I was flying the default B737. Unfortunately I wiped out the log.txt file from ProATC. Before quitting FSX, I decided to open ProATC and clicked on the flightplan and selected Fly Now and the plan activated but FSX was still flying over Lusem so I closed it and FSX.

 

A check of my Event Viewer revealed the following:

 

 

A search of the Internet regarding Kernel32.dll revealed the following:

 

 

My system did not freeze but something (kernel32.dll) caused the program to stop working properly. There are many causes for these types of crashes but it is usually caused by a program accessing memory incorrectly. Could it be ProATC or is it FSX? Earlier you had stated you flew the same route without ProATC and you had no problems. So I think it has to be how ProATC accesses system memory to function properly. You were right. My apologies for thinking it was something else.

 

Best regards,

Jim

Certainly looks that way. Some kind of situation arises in the program and it incorrectly handles memory, or a 64 bit OS issue, or a .NET/c++ library issue. Can the moving map be turned off, if it's just the map you may get some ATC going.

Jim,

 

 

I tested again.Same flight plan (lppt-ebbr ) but with radar contact at night with UTX europe night ligthing on and all bells and whistles on.We all know utx night ligthing is a frame killer btw . NO problem, FSX was nice and smooth.

 

I already told the dev about this but he insists something is wrong with my system, that only 2 persons have this problem and all the rest of that chit.

 

Did you contact him ?

Could be you just need to refresh your scenery, there's a repair function on the DVD. Let's just say it pulls data from a slightly larger radius than RC4, and there's a dodgy scenery record gets included where it does not with RC4. Doesn't sound likely but it does happen, I've had several examples supporting my product since everyone starts flying all over the place. You do need a solid approach to elimination and fault finding. If I ever get a problem the next thing I do is test it alone with FSX. FSX is chit hot coding and does not break easily.

Hi all,

 

 

I 've got the same problem last friday in the same place like you, i was flying between lemd and lfpg, atc tried to contact me but i was too far and i couldn't answer , atc pro crash in the same time.

 

When i rode the log, i confirmed the problem about the reception between atc and my plane.

 

I sent a email at MBA, he answered that he'll try to reproduce the problem.