Jarkko

I also have hardware controllers, but like to fly "as real as it gets". In tube liners, I'm the one flying and my co-pilot handles radios and reads back the instructions. This is why I don't need to access the menu structure during the flight. No errant requests, no ruined flights.

This had me thinking: what things did you access from the menu during the flight? The reason why I'm asking is that, I don't open the ProATC menu (once airborne) at all during a normal flight. I only open it if I have to request a step climb.

It's all about what is important to you. What works for others, might not work for everyone. As for ProATC not providing it's own ATIS so you would have to use the sim's ATIS. The ATIS info is displayed on the ProATC's moving map (at the moment). FWIW I can say the same about RC4 No taxi instructions, no SIDs/STARs/transitions, no holdings, telling me to fly into a mountain, really? I do agree, that currently all ATC programs have features that other programs should/could have.

Have do the following steps inside ProATC: 1) Imported AIRAC data 2) Executed makerwy in the sim's root folder (can be commanded inside ProATC if ProATC and the sim are on the same machine) 3) Executed "Align scenery with AIRAC" By doing these steps, the co-pilot should set the frequency found in the scenery.

This usually happens if do not import AIRAC, rebuild scenery (execute makerwy) and align the scenery with AIRAC, after the update. Can you please post a log on the support forum and will figure out why this is happening. Thanks!

Yes and possibly no: Under ProATC options, you should be able to disable the in sim green text. Haven't tested it though, as I like the green bar, when I have ProATC running on a separate computer.

Hello Richard! 1) Like Tom/tf51d already mentioned: You can run the sim in full screen with ProATC running in the background. 2) VFR isn't supported. Only IFR and for best results, SID/STARs should be available at the airports. Than is what I meant. You have the initial altitude in your ProATC flight plan. Once you having cruising long enough to climb again, you ask for a higher altitude. On shorter flights, no need to execute step climbs. Good point! I haven't noticed this as I have generated a generic profile, that works for flying both the A320 and B737 so I only change the profile, when I fly the MD11. This might be something to fix/improve somewhere down the line. 1) ProATC assigns you the cuising altitude you have set in your flight plan. By default, ProATC's default cruise altitude in the flight plan window is quite high. The good thing is, that in the bottom left corner, you have the flight plan distance. On short flight you can set your flight level to match the flight plan distance (of course also applying the odd/even flight level rules). If the flight plan distance is (for example) 230nm, then you could set your flight level to be either FL220 or FL230 and in an aircraft like A320 and B737, you shouldn't have problems with either climb or descent. ProATC will not assign you a higher altitude than the one in your flight plan unless you ask for higher altitude during the flight. 2) Same answer as for the first question in this post: VFR isn't supported. Only IFR and bigger airports.

I'm guessing that MadDog ment that the "final step climb altitude" isn't selected by default and that is the way it is designed to work. You enter the initial altitude as your cruising altitude and then request altitude changes while in cruise. If I guessed incorrectly, MadDog let me know.

While we look at what is happening, can you please export the plan out of PFPX in SB3 format ("Squawkbox 3 or higher" option in PFPX export dialog). SB3 is the format I use when I'm in a hurry. Haven't heard problems with SB3 (so far) with ProATC. FWIW: I normally copy/paste the route string from PFPX to ProATC (I just have to remember to type the origin and destination airport into the imported string). The reason? Because I usually copy/paste a real world route into PFPX to begin with.

Thanks Pete for the report! I might have and idea what is happening. Did you by any change try to attach the xml file as an attachment to your post? XML files could be used for XSS attacks and the xml upload may have tripped a security wire. Like Clive said, this needs to be looked at.

Thank you Andy for the feedback. You have managed to listed the main reasons why ProATC gets the most use on my sim setup out off all the ATC programs I have purchased so far

Thanks Pete! You and Tom might have found my mistake. It's too late in the evening to work out any kind of math related problems So the steps (with max allow step) would/should be from FL260 to FL500: FL260 -> FL310 -> FL360 -> FL410 -> FL460 -> FL500 Is if I'm now counting correctly, that would be 5 requests instead of the 48 I said before :blush:

This would be the third or fourth time, I have requested you to post a log of your flight on the support forum.... PFPX works perfect with ProATC. I use it on all my flights. I even did a video of one of the flights that you reported as impossible to fly. Here is the result with 100% success: So once more, please post a log on the forums.

Hello Ray! I can't check all the ProATC settings at the moment so I will have answer only based on my memory. As a baseline, I would say, that ProATC will not work realistically with the Concorde. Here's the answers: 1) I would say, that at the moment, you can't exceed 250kts below FL100. I say this because a couple of flights back, ATC told me to slow down, because I (messed up my descent and) went through FL100 with speed over 250kts. I could ask if this feature could be added. It might end up in the end of the TODO list, as is the first time it has been requested. 2) Step climbs are supported and work nicely with normal flights. Having said that, it might take some patience to request a step climb from FL260 to FL500 as currently you can only request 1000-5000ft at a time (enough from normal operations). If I counted correctly, you would have to ask for a higher altitude 48 times to get from FL260 to FL500. 3) With the current version, ATC might complain if you deviate more than 1000ft from your assigned altitude. You can ask for a lower altitude, but I think that once you ask for lower, you can no longer ask for a climb again (might be wrong, but this is what I remember) 4) You can create a descent profile in ProATC but with only two values: descent rate above FL100 and descent rate above FL100. This profile is then used for the TOD calculation. It might be that this is not enough for the Concorde. If you want to descent earlier, that ATC had planned, you can manually ask for a descent. The other option that ProATC provides is that "Request descent manually". When configured this way, ATC will not ask you to start descending before you ask it yourself. --- So based on that, I would say that for using ProATC with only the Concorde, it might not be as good as you would like. Works much better with normal IFR flights.

The current ratio of successful/blocked registrations is about 80 to 1. This would indicate, that users are getting through more often than not. Please check you private messages.

Please PM me the details you enter while registering and will have a look.

It all depends. It took me about 20 seconds to register to the forums. No hoops found along the way. You enter you purchase details and that's it, you are in. Send me a PM if you still have problems.

Hello Jim, Can you please post this on the official ProATC support forum. It can be accessed from the same site you purchased ProATC from. Thanks!

Hello Allen, Bobsk8 and MadDog have good points on what is/might be happening. Can you please post the log of such crash/freeze on the ProATC support forums so we can have a look. Thanks!

Please send me a PM (private message) here on avsim with the details you tried to enter.

Please check your email. The activation message might have ended up in your email's spam folder.

A great number of users so far have done the "impossible" Please check your spam folder.

That's not the way the auto thrust works in an Airbus... The thrust levers have to be in one of the gates (TOGA, FLEX or CL) for it to maintain speed for you (you will hear a noticeable click, when the thrust levers enter or exit one of these gates). On takeoff, you push the thrust levers either into the TOGA detent/gate or the FLEX detent (also verify that the auto thrust has engaged). After thrust reduction altitude, the aircraft will ask you to place the levers in the CL detent where the levers will stay for the rest of the flight (right until the the aircraft starts to call you a retard, retard, retard). In the above picture, you can see the levers in the CL detent/gate. If the thrust levers are not in one of the detents/gates, you are basically telling the aircraft: "I will control the thrust for now, and will give the control back to automation once I place the levers in one of the gates". Notice that I didn't use the word throttles, as the thrust levers in an Airbus do not work the same way as conventional throttles. When in the correct gates, the levers do not move at all even though the aircraft is managing the speed/thrust. You are in for a world of hurt if you try to fly an Airbus in a traditional way. Please do the tutorial flight over and over again until you understand each steps and why is it needed. FWIW: I'm again re-learning to fly the NGX after flying A320 for couple f years. After flying the Airbus for so long, the NGX it's like you've been put back in time. The aircraft feels like it was designed to have a flight engineer, but at the last minute, the designers realised, that there isn't a room enough for a third pilot on the flight deck I'm willing to say, that in the NGX I have to press twice as many buttons/switches than in the Airbus in order to complete the same task. But... The reason I'm going back to NGX is that PMDG feel like they have been very well tested and made, while the Aerosoft's Airbus has multiple bugs (some even causing FSX to crash).

I usually do not use use RTFM, but in the case of Airbus, I have to. Flying an Airbus is all about entering all the required data and then monitoring as it goes through the motions of getting you from A to B (can be flown "normally", but you would miss the "Airbus experience"). The tutorial flight in the manual is a must to execute and understans (if you are planning to use the aircraft for more than two or three test flights). The reason is that an Airbus must be in a correct mode (takeoff, climb, cruise, descent, approach) in order for the autopilot to work correctly. To get the aircraft into the correct mode, you must have the correct data entered into the systems and you must press correct autopilot buttons at the right time. Having said all of that, if you want to fly it the old fashion way, then "pull" the speed, heading and altitude knobs (pulling with a right click means that you are taking over the control of speed/heading and pushing the knob with left click, means you are giving back the control to the aircraft's automation). Then you enable the auto thrust and push the throttles one notch past climb detent. Once airborne, click the autopilot 1 button.

Hello Andy, Can you please post the same info to the ProATC support forum with a log attached. The reason I'm asking you to do so, is that you should have done things correctly. What should have happened with your flight plan, is that you would have been given GPS18 with HYOJO transition (no vectors needed). Like you mentioned, no ILS approach available so something about the installation isn't right. This is why we need to have a look at the log. (sounds like AIRAC import or scenery import didn't work as expected as ProATC falls back to ILS if required data is missing IIRC) Thanks for the report!