Jarkko

When you start a ProAtc flight, the system will automatically tune the ATIS frequency. You won't be able to continue until you tune in the correct clearance delivery frequency. You can do it your self or have the co-pilot tune it for you (he does this after running the first check list)

Patrick, I tend to agree with Dutch1 with this. The "automatic flight plan importing" in ProATC is meant to help new users who are still learning to fly the default FSX aircraft (no FMC available). As you know how to operate the PMDG aircrafts, then I would do as Dutch1 suggested. When you program and operate the FMC manually, you will be much happier with ProATC. Cheers, Jarkko

Please fly the tutorial flights first. They can be found at the end of the manual. Also read the manual on how to set the paths under the options. Support only available on the main support forum.

The choice is easy if you are running a boat load of plugins (Latitude, AirHauler, FSFlightKeeper, FSPassenger) in tandem with you weather engine. One works without a problem, the other causes wind shifts (that destroy your aircraft). This is why ASN and FSGRW are the ones I use. I tried to debug the problem with the developer, but ... how should it put it ... I got the feeling that the developer was more interested in shouting rather than problem solving.

This wasn't true in the past versions (haven't tested the latest version). This is because once you get airborne, ASN doesn't inject correct weather into FSX until you are 100nm away from your destinations (distance is configurable). VoxATC used the "default calm weather" to determine the ARR weather before the correct weather was injected. This is also why the restart worked in past versions. So what I'm saying is that in the past, correct DEP weather didn't automatically mean correct ARR weather. Hence this thread asking about it.

I use Rex latitude in combination with AirHauler, FsPassenger and FSFlightKeeper. There is some overlap between these programs, but they all score the flights from a slightly different angle. I'm currently very happy with the results. FSPassenger focuses on how a passenger would rate your flight. FSFlightKeeper judges based on the way you operate your aircraft (for example lights and how well you taxi). Rex Latitude is more like a flight instructor. It makes sure you fly smoothly. It is particularly sensitive on how you you do your landing. I have found Rex Latitude to be the hardest to keep happy. Other programs might give me a perfect score, but only get 68% score from Rex Latitude, because I floated the landing or had excessive g-forces during takeoff or landing.

Thank you for the update. The install instructions I sent you specifically mentioned not to install ProATC under C:\Program Files (x86)\ The problem was that inside ProATC (under Options -> Paths to folders), you probably had incorrect path configured for FSX/P3D. If you have FSX installed under C:\Program Files (x86)\Microsoft Games\FSX, then you have to tell ProATC this path (under Options -> Paths to folders). I have now requested three times: Can we please continue the troubleshooting in the product's official support forum? ( BTW it is not advisable to install FSX or ProATC under C:\Program Files (x86) )

Dear Patrick, Just to repeat: No support for ProATC will be provided on Avsim forums. The developer and helpful users and moderators are at your service at the main forum, which can be found here: http://www.pointsoftware.de/forum/viewforum.php?f=2 As for the manual, please go to your ProATC's root folder. There you will find a holder called help. Inside that folder, gb.pdf and that is the manual in PDF format. As your install has been corrupted in a way never seen before, so you might have to contact the developer. I will PM you the email address to the developer. Thanks, Jarkko

Can we please continue on the main support site? You should be able to include your Word file there. Thanks!

Please report any problems on the product's main forum as this sound like like either a corrupted download or possibly you have only installed the update and not the main software. (ProATC shouldn't as you to insert a disk as it is only available as a download install)

Just that you know, the PMDG MD11 doesn't fly like the big boys simulator, that I got to fly (the full motion kind). PMDG has done an exceptional job system wise, but the flight model isn't true to life (and how could it be considering the price). Also the real MD11 pilots said that the real aircraft is a bit more forgiving on landings than the sim they were using for training. With the PMDG MD11 I had gotten into a habit of pushing a bit forward right after the wheels left the ground. When I did it in the sim that the real pilots use, I dropped straight back to the ground. (and got yelled at by the MD11 pilot) Same thing for landing. With the PMDG variant, I flared late and sharp and have gotten good landings. Tried that in the "real sim" and I floated all my landings. --- Now back to the topic, but from a sim view. I fly cargo with AirHauler and in this game, only things that matter are: the purchase price, fuel burn and the amount of cargo you can carry. In this scenario, MD11 and A340 are the work horses, where B747 and B777 are too expensive to purchase or too fuel hungry. So I agree, that on paper, the MD11 (and even the A340) should have been the winner (at least in cargo operations), but as mentioned, in the RW things didn't work out that way.

That is because I do not know I have never had to reject a takeoff on any of my flights (not even with Radar Contact), so I haven't checked if it's supported.

Yes, ProATC supports declaring an emergency. The last time I had to use this function was during one of my AirHauler flight. ProATC had me fly a holding pattern near LSZH, when AirHauler decided to fail my altimeter (in total IMC). I was able to declare an emergency and landed somewhat safely (I'm glad I already had the ILS tuned so I could use it for judge my altitude). You can declare an emergency anytime during flight. Based on where you are, you are either sent to the takeoff alternate, or the closest suitable airport (if your destination/alternate airports are too far away).

I will send an PM today with more info. This happens, when the auto update has failed. The fix that has solved most of the problems is by downloading the 1.4.0.0 fix file from here: http://www.pointsoftware.de/proatcx_e/download.html (proatcx-update-1400_rx.zip) If you could try to download it just once more, then take everything inside the zip file and copy them over the old files in the ProATC root directory. --- Now if this doesn't cure the problem, make you are on the clearance frequency when requesting clearance. When you select "Fly Now", ProATC will automatically tune the ATIS as the active frequency and the clearance as standby frequency. If this doesn't, can you please run the first checklist? After running the first checklist, the co-pilot will attempt to switch to the clearance frequency. --- If still no luck, then let's try to debug this remotely. As mentioned, I will send you a PM later today.

PM me your Skype info and I let's see what we can do. Sounds OK?

I just checked the forum's admin log and no posts have been deleted in the last 8 days (and even the last one was deleted because of double post). Also no posts could be found in the acceptance queue. What makes you think that the post was deleted?

The "pilot's voice" saying Speedbird is the ProATC's Alpha117 voice set.

Some of the voice sets are already corrected as can be heard on this ProATC user's video: Just to add my 2 cents. There are at least 5 ATC programs that I could imagine users quoting as "the best". The reason is that, that there isn't a complete ATC program yet. If someone were to combine all the 5 major ATC programs into one program, then I would be very happy Until that happens, the "best" ATC program is highly dependent on what features are a must for you and what features you are willing to live without.

Yesterday I requested a nick Dougal to send an email to the developer so he could get the full install file for the new version. The reason why Dougal might not have gotten an instant reply is that the team is currently working on releasing a hotfix for the 1.4 version (hopefully resolving the auto update issue for good). In case you happen to be the same Dougal, I hope you will try out the 1.4 version from the full installer and post a log on the main forum if problems occur. Thanks!

Would you happen to be using A2A AccuFeel by any change? Anytime I disable AccuFeel, the stutter goes away. Now, I'm not sure what cures it. The AccuFeel disabling or the Aircraft resets it self just by accessing a menu item.

Here are my 2 cents: I have about a 1000 hours of sim time gathered during the last 5 years. During this time I have also flown an ultralight and a LevelD MD11 simulator. How did I do? With the ultralight, I was able taxi, takeoff, traffic pattern and approach until flare without having to give up controls to the instructor on my right side. Totally different experience to anything I have experienced in the sim. No camera shake can recreate the up und down motion you got on a hot sunny day. On my LevelD MD11 ride, I was able to land OK (floated like mad on all attempts) in the slightest turbulence and 5kts cross wind. Takeoff and taxi, no problems. The one that surprised me was the control forces. Once in trim, you could control the aircraft with you finger tips. Get her out of trim and it was a very good upper body workout. So would I be able to fly a passenger jet? Absolutely not! Sensory overload was the only way to describe both the real world flying and the full motion sim experience. I was able to execute simple commands and fly the aircraft, but that was about it. There was no way I could have done anything, that would have needed any sort of decision making when hand flying. So that was my experience. I hope I caused at least a few facepalms

As I personally use only the camera features from OpusFSI, I agree that it has the potential to "fly off the shelf" if it were a separate product.

I think you might have to contact the aircraft developer (PMDG) with this request

I have the same problem at ESSA and LEPA. Taxi lights disappearing and then coming back again. I have yet to look more into the problem. Just wanted to mention, that you are not the only one. I'm not sure if the "ballast light" has anything to do with this?

On the subject of "not just what you want": Who, when and where said this? All I have said on the subject is, that this wasn't major enough problem to hold back and already delayed release. As far as I know, the fix for this is at the top of the fix list (right after not getting a landing clearance, which in turn is a major bug). I just went thought the official forum and saw nothing like this mentioned. Might have missed it though. I personally import my routes either from PFPX, FlightAware or eurofpl.eu and haven't had more that one or two routes rejected by ProATC. Just make sure to include the origin and destination airport codes to the route you are importing from PFPX and you should be good to go. If not, please report on the official forum.