Sorry to hear you are still having issues Michael!

 

Thanks Jim. Actually, I tried 1.0.2.8 again with the PMDG 747 on the default EDDF-EDDH, and it all worked rather well! ATC from gate to gate, and nothing worse than the other ATC products I use. Quite a lot of fun, and it creates a remarkably good ambience for something so simple to use. It's definitely got it's priority correct by understanding that FS X is the main event, and that an add-on should not take over one's FS life!

 

The developer was very good trying to sort things out, and responded promptly to all requests. I can see this going on to be an excellent product in future, and - if it continues to work for me - I'd say it's pretty good already.

 

Michael

Thanks Jim. Actually, I tried 1.0.2.8 again with the PMDG 747

 

Hello

How does ProATC handle the differences in the PMDG's navdata ?

There's no real differences to speak of on this short flight, so not something that mattered to me.

 

I suspect that the key thing is to view the Pro ATC X routes on the default GPS (there are two routes, one each for departure and arrival), and then follow the GPS commands using heading select in places where the LNAV route will be significantly different. I will not mind doing this if it ever crops up, because the Pro ATC X simplicity and ambience will outweigh it for me.

 

Michael

Hello

So it is basically unusable with third party aircraft with updateable navdata, unless you are able to ask for a direct to waypoint.

Can ProATC handle direct to waypoint requests ? and can the copilot handle the systems in non default aircraft?

so you don't have to fly for the Luftwaff - I mean Lufthansa:

 

You're such a bleedin' Limey!

 

Jerome

<br />Can ProATC handle direct to waypoint requests ? and can the copilot handle the systems in non default aircraft? <br />

 

No. It's total vectoring from Point A to Point B. However, once you know the SID and takeoff runway and you have the basic waypoints, you can program these into the FMC of a commercial aircraft such as the PMDG 737. You have to listen carefully though and make sure you are on the same course/heading as what ATC directs. At Cruise Level, you should be okay until you begin the descent. Again, once ATC provides the STAR and Runway, you can enter that into the FMC. You'll have to handle speeds and altitude settings manually as ATC provides those during the descent or change this data in the Legs Page of the FMC. Could be quite a chore for those just learning the FMC.

 

Best regards,

Jim

<br />The developer was very good trying to sort things out, and responded promptly to all requests.<br />

 

I agree. Things are definitely getting better with 1028. I repaired my background ATC and choose US ATC I had set up for all of the United States. I flew another flight from LAX to SFO and took off from 25L. US ATC ground chatter was great as well as departure chatter. Then, I flew out over the Pacific and that's UK territory so my chatter turned from US to UK out over the water. It continued even inland but finally went back to US chatter. I have since changed the profile from country to region. That way I can cover all the way to Japan over the US to Europe. Hopefully that will work. BTW, my most recent flight from LAX to SFO was completely successful again. I think my next flight will have nasty weather. See if it can handle that!

 

Best regards,

Jim

_{Finally got around to giving it a try with the latest patch, and I thought it was working okay, it gave me the descent, and it looked like it was keeping me clear of terrain too, but at 21,000 feet the sound failed, being just static, with my co pilot failing to respond and the controller text asking me to confim descent as text on screen but with only a static sound, and a minute later I got the on screen Windows message that Pro ATC had stopped working, so, another two hours up the swanee. Windows still randomly close during the flight planning stage too. This was with the EVO 737-300, using LNAV and VNAV, with occasional manual flying or autopilot headings on the MCP.}

_{Screenie of me actually getting a descent for a change, sadly, it bombed about 2 mins after this shot:}

 

 

 

_Al

Well you guys are having more luck than I am.

 

I cannot even hit the first waypoint following the vectors I am handed out. The headings are constantly out by 24 degrees. Looking at it's moving map and another third party moving map ( Courseplanner) I can see that the headings of my plane differ between the two, with Pro-ATC consistently wrong. If I let the program control the plane it leads me out into no mans land.

 

Even the list of ai traffic of the two programs differ. Pro-ATC was consistently only showing about half of them (not using any 3rd party AI programs). Even worse was that it was showing the wrong data for them. I was waiting behind two other planes waiting for take off clearance, which I got before the other two had left. In this case Pro-ATC showed them still sitting at the various ramps. I waited then took off and flew around aimlessly chasing the vectors. Looking back at the moving map I saw that the two ai planes that had taken off were still being shown as sitting on the ramp. The other moving map program was displaying them correctly.

 

I have wasted enough time on this. I have better things to do than test software I have paid for.

 

Mark

I got the on screen Windows message that Pro ATC had stopped working, so, another two hours up the swanee. Windows still randomly close during the flight planning stage too.

 

Al, You should check the Event Viewer to see what exactly what module, if any, caused ProATC to stop. It's probably a system issue rather than FSX/ProATC. As I recall now, I had difficulties editing my flight plan too with ProATC closing unexpectantly. But this happened when ProATC was started (but not activated) and I started FSX and got to the FSX startup screen, then I went back to ProATC and tried to edit the flightplan. When I closed ProATC and restarted it, the problem went away.

 

Well you guys are having more luck than I am.

 

Mark, my success(es) have been with the default B737 only and with the co-pilot handling everything. Since the 1028 patch I have not tried a payware aircraft and tried following the vectors provided by ATC. That's not really realistic for ATC to provide total vectoring for SIDs and STARs anyway. That's definitely an issue if you suddenly allowed the co-pilot to takeover and he took you "into no mans land". In any case, just wanted to emphasize my successes were with the default and always with the co-pilot handling everything.

 

Best regards,

Jim

I cannot even hit the first waypoint following the vectors I am handed out. The headings are constantly out by 24 degrees. Looking at it's moving map and another third party moving map ( Courseplanner) I can see that the headings of my plane differ between the two, with Pro-ATC consistently wrong. If I let the program control the plane it leads me out into no mans land.

 

It works better on defined SDs. Vectors seem not to be perfected yet, with cross-winds and mag var possibly not accounted for. Again though, by keeping an eye on the GPS you can see what the program expects you to achieve, and you can then achieve it quite easily.

 

I have had no cause for complaints about the AI traffic so far. In fact, it has worked quite well, with the default ATC operating in the background to add extra ambience in relation to the AI traffic.

 

Michael

Al, You should check the Event Viewer to see what exactly what module, if any, caused ProATC to stop. It's probably a system issue rather than FSX/ProATC.

 

this is the log, dunno if this means anything to anyone:

 

Faulting application name: proatcx.exe, version: 1.0.2.8, time stamp: 0x4ff1d067

Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e211319

Exception code: 0x0eedfade

Fault offset: 0x0000b9bc

Faulting process id: 0x15f0

Faulting application start time: 0x01cd598e440f308a

Faulting application path: C:\Program Files (x86)\PRO-ATC-X\proatcx.exe

Faulting module path: C:\Windows\syswow64\KERNELBASE.dll

 

Al

I had a couple of successful flights. I had to uninstall input director and kill off sandboxie before starting pro atc cause they were interfering and fsx froze.

I had a couple of successful flights. I had to uninstall input director and kill off sandboxie before starting pro atc cause they were interfering and fsx froze.

 

I love input director. Darn.

 

Bob

this is the log, dunno if this means anything to anyone

 

Al, I did a Google search for kernelbase.dll and this issue can be caused by several system problems. A corrupted User Profile is one, a corrupted registry is another. There are several possible fixes. That's why I'm not going to post them here. You might find one that applies to your system. I doubt it is caused by ProATC as no one else has suffered this type of crash. Hope this helps!

 

Best regards,

Jim