I've already looked at the stuff online regarding that, and I'm not totally convinced it is a system-related problem, nor that I'm unique in experiencing it, although it is one thing I am going to try sorting out anyway. I wouldn't put it past Pro ATC being at fault given the difficulties most people are having with it, as evinced by a fourteen page-long thread about it, most of which concerns failures rather than trouble-free experiences.

 

Al

although it is one thing I am going to try sorting out anyway.

Al

 

Nothing a full system format and a nice cheese sandwich couldn't rectify!

Yup, like I'm gonna do that when it's the only program on my computer with problems and it is known to be glitchy :lol: Although I do like the idea of the cheese sandwich.

 

Al

I've not had a chance to try it but will soon. I'll first use a default aircraft and fly north/south between airports with east/west runways and a consistent wind direction and no Ai aircraft. That should give it a chance. Increase complications from there...

if it's too good to be true then it probably is. I had a few successful flights and now fsx freezes when I run proatc.

 

I tested on this :

 

LIRF 07 DME D023G OST RAVAL GISPA UL5 ROMPO UQ714 GINOX UM601 BCN UN975 TAGUX EXONA LPPT

 

FSX froze around the rompo area the first time. So i restarted but this time without fsrealtime ( I thought it would somehow interfere)-Took off from lirf and fsx froze again around rompo. I tried the 3rd time but without proatc and all was good. Go figure!

 

 

It would be nice if some of you could test it on the same route using the same -plane just to see if it is on my end only.

 

Thanks

It would be nice if some of you could test it on the same route using the same -plane just to see if it is on my end only

 

Is it possible to get the name of the aircraft you were flying? :lol: Also, not sure how you made up that flightplan in ProATC. I know you can add waypoints but everything else is dependent on weather (i.e., the runway, the SID, the STAR).

 

When FSX froze, an Event should have been recorded in your Event Viewer that would be helpful to the developers if they happen to come across this thread. If the faulting module was the same as what Al received earlier (kernelbase.dll), then we can start seeing some sort of a pattern.

 

Best regards,

Jim

id:

It would be nice if some of you could test it on the same route using the same -plane just to see if it is on my end only

 

 

Jim sorry for the typo.I meant to say the same flight plan. Actually "-plane" was supposed to be "f-plan"

Good idea. Things are easier to work out if the winds are consistent so things don't change too much during the flight. The east/west runways and north/south routes direction ensures the least turning around for the departure and approach. I would use a default plane, default scenery, no other addons, go from there. Iv'e not got the time right now but as soon as I do I'll get it and have a go.

No problem. Just finished making the flight plan. This is exciting stuff!

 

Will advise after ROMPO.

 

Best regards,

Jim

It would be nice if some of you could test it on the same route using the same -plane just to see if it is on my end only.

 

Mission accomplished! No freezing or crash; however, I had great FPS before ROMPO easily over 40 FPS, but upon nearing arrival to the ROMPO intersection (about 14 miles away), FPS went down to a steady 31-33 in the VC and got down near 20 FPS in spot view. Soon after passing ROMPO, FPS increased to a steady 41-45 frames in the VC and even higher in spot view. It's just mainly water to ROMPO and land afterwards so this is strange. I would say your settings are probably too high. I was really expecting a crash when the FPS in spot view went down to 15-20 FPS. Hope this helps!

 

Best regards,

Jim

Mission accomplished! No freezing or crash; however, I had great FPS before ROMPO easily over 40 FPS, but upon nearing arrival to the ROMPO intersection (about 14 miles away), FPS went down to a steady 31-33 in the VC and got down near 20 FPS in spot view. Soon after passing ROMPO, FPS increased to a steady 41-45 frames in the VC and even higher in spot view. It's just mainly water to ROMPO and land afterwards so this is strange. I would say your settings are probably too high. I was really expecting a crash when the FPS in spot view went down to 15-20 FPS. Hope this helps!

 

 

Nice. It's weird tho. I'm still wondering how come my fsx does not freeze when I fly the same route but _without_ proatc ? I think if my setting were too high then they would be too high with and without proatc.Just guessing.

 

Thanks Jim.

When FSX hangs, see if ProATC has hung too. Since it's out-of-process it should be unaffected if it''s just FSX crashing. If they are both hung - likely it is ProATC stalling the conversation.

Updating UTX europe to the latest version solved the problem ! NO more crashes (famous last words ?).-

Updating UTX europe to the latest version solved the problem ! NO more crashes (famous last words ?).-

 

...hence the need to avoid other addons when checking out new software...

How do you actually update UTX? I see an option which says 'prepare it for patching' on the menus, but then what do you do after picking that?

 

Al