Fred,

 

when did you contact MBA ? I hope he'll come up with something better than "something is wrong with your system".

"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."

 

SteveW: I can assure everyone that my dotnet/MSV c++ library is up-to-date. I frequent the AVSIM CTD forum and anyone who has a crash, I make sure they have these libraries up-to-date and everything is installed. I'm wondering if the developers used dotnet framework for development of their program as one of its functions is to manage memory for their program. It is possible the Moving Map feature caused the crash but as I stated above, I destroyed the ProATC log.txt surrounding the crash. It had to be solely ProATC related as the error message above indicated ProATC had to close and I proved I could continue with the flight when ProATC was closed. I have FSX installed in the default location but installed ProATC in a folder on another drive. I doubt it's a 64 bit issue.

 

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 ?

 

No. Mainly because, as I stated, I accidently destroyed the ProATC log related to the crash. I plan on trying to duplicate this event as Google states kernel32.dll errors can be just a fluke and all that may be needed is to reinstall the program. If I get the error again I'll save the log and send it to ProATC developers. Just want to emphasize I had no crash, just an error in ProATC that required the program to be closed.

 

atc tried to contact me but i was too far and i couldn't answer , atc pro crash in the same time.

 

Fred, Did you get the same error message as I had above. I would be interested to know what your Event Viewer said that caused the problem. The kernel32.dll like I displayed above? Glad you reported the problem. We now have at least 3 people with a similar ProATC issue. Not sure about Al's crash(es). It's easy to blame an issue on someones system as they are prone to problems all the time. But with several people having the same problem, it has to be something other than our computer systems.

 

Al, I hope you don't mind us hijacking your OP to try to resolve these issues with ProATC!!!

 

Best regards,

Jim

 

 

 

 

• 
   
  

I was able to duplicate the crash of ProATC that I had last night. Same place on my flight plan from Lisbon to Brussels. This time I was able to save the ProATC log and I will forward it to them. It appears the co-pilot could not respond because Frequency 132.97 (Madrid) is not in range (see below). I tried several times to have ATC repeat the transmission but each time it sounded like static in the sound but clear in the ProATC line that shows what was stated. This flightplan was not edited in any way. I just selected the departure and arrival airports and then clicked on Save.

 

2012.07.08/09:22:21 - NEXT WPT: LUSEM

2012.07.08/09:22:21 - CTRL SENDMSG: rdrclrint=rbrdrclrint; rdrcontinueawy=rbrdrcontinueawy; hdgaltmtn=rbhdgaltmtn;

2012.07.08/09:22:30 - CTRL[11] FRQ=13297 IS NOT IN RANGE!

2012.07.08/09:22:30 - CTRL: WAIT FOR CONFIRMATION

2012.07.08/09:22:45 - CTRL[11] FRQ=13297 IS NOT IN RANGE!

2012.07.08/09:22:45 - CTRL[MADRID] not in range!

2012.07.08/09:22:45 - CTRL SENDMSG: affirm=-;

2012.07.08/09:22:45 - ComStatus not ok or radio in transaction: %s

 

The Event Viewer revealed exactly the same error information as I had last night - faulting module kernel32.dll. Don't think it's related to memory now but an issue solely with ProATC.

 

Best regards,

Jim

This time I was able to save the ProATC log and I will forward it to them

 

Thanks and good job Jim. Let us know how the whole thing develops.

Al, I hope you don't mind us hijacking your OP to try to resolve these issues with ProATC!!!

Jim

 

Nope, not at all, this problem is one affecting everyone on this thread, and it always has affected me, every time I have tried to use Pro ATC, it has either stopped giving me ATC diections, or failed to give me a descent, more often than not also crashing. But it has never taken FSX down with it and I've always been able to continue the flight, however, as you can imagine, I've invariably chosen to quit FSX as losing the ATC has kind of spoiled the enjoyment.

 

Given that everyone on this thread has experienced that issue on what appears to be more than one occasion, the developer's claims that my problem is 'rare' is not something I would agree with at all.

 

Unfortunately, on the contrary, the problem seems all too common, and if the developer has not seen this thread, then he ought to do so before claiming that such a problem is unusual and trying to fob people off with claims that their system is to blame, because sixteen pages of a thread, which is principally concerning the failure of the program to work adequately on many people's computers would tend to suggest otherwise.

 

If the developer is so certain that it is people's systems that are to blame, then he ought to be able to tell us exactly what it is about our systems that is to blame should he not? Particularly when pretty much everyone here has a forum avatar section where it lists their specs.

 

Al

Al, your problem is very similar to mine. It would be interesting to see if your Event Viewer had kernel32.dll as the faulting module too. I just sent Pro-ATC an e-mail describing my problems where I had to close ProATC. I would venture to state your log.txt also indicates a frequency was not in range. But, you'll never know as the log.txt file in the ProATC folder is overwritten everytime you activate a new flight. I am now saving my logs to log1.txt, log2.txt, etc.

 

I hope too that the developer and programmers are looking at this thread periodically. I hope they find a solution.

 

Best regards,

Jim

Yup, it did indeed say that Madrid was not in range, and if Pro ATC includes radio range as a feature, then great, but should that crash the program? Nope, I should be able to establish contact with another frequency or sqawk 7600 or something, and in any case, I doubt an airliner at 36,000 feet would be out of range of the controller which I had been handed off to when on an IFR flight, it would be a very inept controller who would do something like that.

 

I posted a link to this thread on the Pro ATC forum incidentally, so if the developer doesn't know about this thread, then he will do soon.

 

Al

I posted a link to this thread on the Pro ATC forum incidentally, so if the developer doesn't know about this thread, then he will do soon.

Al

 

Great idea even if they are visiting here occasionally.

 

Best regards,

Jim

Great idea even if they are visiting here occasionally.

 

and bringing an overnight bag!

Got a quick response to my e-mail from Mourad Boutabba and he's going to try to reproduce the flight. He has responded quickly to any request I have sent him and I'm impressed with his support. We'll see what he finds.

 

Best regards,

Jim

I was able to duplicate the crash of ProATC that I had last night. Same place on my flight plan from Lisbon to Brussels. This time I was able to save the ProATC log and I will forward it to them. It appears the co-pilot could not respond because Frequency 132.97 (Madrid) is not in range (see below). I tried several times to have ATC repeat the transmission but each time it sounded like static in the sound but clear in the ProATC line that shows what was stated. This flightplan was not edited in any way. I just selected the departure and arrival airports and then clicked on Save.

 

2012.07.08/09:22:21 - NEXT WPT: LUSEM

2012.07.08/09:22:21 - CTRL SENDMSG: rdrclrint=rbrdrclrint; rdrcontinueawy=rbrdrcontinueawy; hdgaltmtn=rbhdgaltmtn;

2012.07.08/09:22:30 - CTRL[11] FRQ=13297 IS NOT IN RANGE!

2012.07.08/09:22:30 - CTRL: WAIT FOR CONFIRMATION

2012.07.08/09:22:45 - CTRL[11] FRQ=13297 IS NOT IN RANGE!

2012.07.08/09:22:45 - CTRL[MADRID] not in range!

2012.07.08/09:22:45 - CTRL SENDMSG: affirm=-;

2012.07.08/09:22:45 - ComStatus not ok or radio in transaction: %s

 

The Event Viewer revealed exactly the same error information as I had last night - faulting module kernel32.dll. Don't think it's related to memory now but an issue solely with ProATC.

 

Best regards,

Jim

 

 

 

Hi,

 

I've got the same log as your.

 

event viewer:

 

 

Nom du journal :Application

Source : Application Error

Date : 07/07/2012 10:05:54

ID de l’événement :1000

Catégorie de la tâche :(100)

Niveau : Erreur

Mots clés : Classique

Utilisateur : N/A

Ordinateur : fred-PC

Description :

Nom de l’application défaillante proatcx.exe, version : 1.0.2.8, horodatage : 0x4ff1d067

Nom du module défaillant : unknown, version : 0.0.0.0, horodatage : 0x00000000

Code d’exception : 0x00000000

Décalage d’erreur : 0x00000000

ID du processus défaillant : 0xe8c

Heure de début de l’application défaillante : 0x01cd5c09478af529

Chemin d’accès de l’application défaillante : D:\Program Files (x86)\PRO-ATC-X\proatcx.exe

Chemin d’accès du module défaillant: unknown

ID de rapport : 92d466cc-c80a-11e1-87e5-f46d0499faba

XML de l’événement :

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Application Error" />

<EventID Qualifiers="0">1000</EventID>

<Level>2</Level>

<Task>100</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2012-07-07T08:05:54.000000000Z" />

<EventRecordID>38132</EventRecordID>

<Channel>Application</Channel>

<Computer>fred-PC</Computer>

<Security />

</System>

<EventData>

<Data>proatcx.exe</Data>

<Data>1.0.2.8</Data>

<Data>4ff1d067</Data>

<Data>unknown</Data>

<Data>0.0.0.0</Data>

<Data>00000000</Data>

<Data>00000000</Data>

<Data>00000000</Data>

<Data>e8c</Data>

<Data>01cd5c09478af529</Data>

<Data>D:\Program Files (x86)\PRO-ATC-X\proatcx.exe</Data>

<Data>unknown</Data>

<Data>92d466cc-c80a-11e1-87e5-f46d0499faba</Data>

</EventData>

</Event>

Yes, except my faulting module was indicated as the kernel32.dll. Yours indicates unknown. I had one of those "unknown" reports too just before the kernel32.dll event. Did you ever check your ProATC log.txt to see if your flight also had an out of range of frequency error? In any case I got a response from Mourad and they will release patch 1029, probably tomorrow to fix the issue I reported (frequency not in range of Madrid). He says during the flight I passed a few radar sectors having the same frequency. In this case latitudes and longitudes were not updated, which may have cause the out of range error. Like I said earlier, they are very responsive when an bug such as this one is reported.

 

Best regards,

Jim

and I'm impressed with his support.

 

Yes in the beginning he's really quick.When he decides that your system is to blame/runs out of excuses he does not bother anymore.

Just a theory! The developer seems to be blaming peoples systems, which seems to indicate he's not seeing the problems himself. Developers tend to work from their own native builds, which may be ok, but the release installer itself may have a problem, which is why everyone else hasn't gotten it to work (at least I haven't heard one report of it working as advertised consistently - I think there was 1 report of a successful flight in this thread). Like I said just a theory!

Yes in the beginning he's really quick.When he decides that your system is to blame/runs out of excuses he does not bother anymore.

 

I think it's all how a problem is reported. With your help I was able to fly a couple of your routes where your FSX was freezing up. I was able to fly a similar flightplan and find the issue, check the Event Viewer and verify it was a ProATC problem and submit a report to the developer. He immediately replied that he would fly the route and try to duplicate and reported back that it was a bug that would be fixed. I never got FSX to freeze up like you did but did receive the error message that ProATC had a problem and had to close. Once closed, I was able to continue the flight without having to close FSX. So your issue is a bit different and possibly an indication that you do have a computer system problem that is enhanced when you fly with ProATC. I have proven I can fly the route and not get my system to freeze up like yours did. I can continue with my flights. I think a real possibility is your configuration of UT Europe which takes up a lot of resources if not configured properly so it may not be your computer but another piece of software or hardware driver. I don't know what a developer can do more as ProATC is working for some but not on your system. Let's wait and see what the next patch does. Perhaps it will fix your issue and all of this is moot. I think we all need to be a little more patient.

 

but the release installer itself may have a problem

 

Hi Tom,

The release installer is having the proper MS Visual C++ installed which helps a developer install their software properly. I have had several successful flights now with ProATC and so have others; however, you occasionally run into a bug like I did above which affects certain locations. So far I have had successful flights from KLAX to KSFO and KORD to KSTL with the latest patch (1028). I think if everyone who owns this software flies those routes they will have a successful flight too. It's just in some regions of the world, there are issues which still need to be ironed out by the developer. Basically the software is working, maybe not to the satisfaction level of some, but it's working and I think it will get better in the future.

 

Best regards,

Jim