FSX-MS PROATC-X v1.7 Released

[tamsini 278]

I constantly keep getting the following error - no matter how many times I try:

 

Hourly registration attempts exceeded!
Please try again at a later time.

[Jarkko 59]

I constantly keep getting the following error - no matter how many times I try:

 

Hourly registration attempts exceeded!

Please try again at a later time.

 

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

[skipph 82]

I tried to register again and was corrected about password parameters after the fact which led to another banishment to the penalty box for another hour, like all I have is time to fart around for this BS. Please state all the parameters up front and stop harassing the paid customers. Skip

[Jarkko 59]

I tried to register again and was corrected about password parameters after the fact which led to another banishment to the penalty box for another hour, like all I have is time to fart around for this BS. Please state all the parameters up front and stop harassing the paid customers. Skip

 

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.

[srcooke 52]

I tried to register again and was corrected about password parameters after the fact which led to another banishment to the penalty box for another hour, like all I have is time to fart around for this BS. Please state all the parameters up front and stop harassing the paid customers. Skip

 

The requirements have been made easier despite the 200 plus successful registrations from around the globe.

[Ray Proudfoot 9,032]

Considerable progress looks to have been made with Pro ATC-X.

 

Can I ask a couple of questions specific to flying Concorde? Radar Contact 4 gets a bit tetchy when I don't climb all the way to my assigned altitude so I was wondering how Pro ATC-X copes.

 

1) Can 250kts below 10,000ft be exceeded?

 

2) Can I maintain FL260 for a variable amount of time before starting the supersonic climb to FL550-600? On some flights it may be necessary to stay subsonic at FL260 until clear of land.

 

3) Concorde was cleared to a block flight level usually FL480 - FL600. Unusual but as nothing else was up there it had the freedom to climb and descend in that block in order to maintain Mach 2. If I'm cleared to FL600 but level off when lower or even descend slightly will this cause a problem with Pro ATC-X?

 

4) Its descent profile was different to conventional aircraft with the overriding requirement to be subsonic 25nm before land. Would I have the option of starting my descent earlier or later than instructed or is it mandatory to start down only when instructed? Concorde would slow to 350kts IAS before initiating a gentle descent that became progressively steeper at Mach 1.5 and steeper still below Mach 1.

 

And thinking way ahead when you record new call signs could you also include Speedbird Concorde?

 

Thanks.

[Jarkko 59]

Can I ask a couple of questions specific to flying Concorde? ...

 

1) Can 250kts below 10,000ft be exceeded?

 

2) Can I maintain FL260 for a variable amount of time before starting the supersonic climb to FL550-600? On some flights it may be necessary to stay subsonic at FL260 until clear of land.

 

3) Concorde was cleared to a block flight level usually FL480 - FL600. Unusual but as nothing else was up there it had the freedom to climb and descend in that block in order to maintain Mach 2. If I'm cleared to FL600 but level off when lower or even descend slightly will this cause a problem with Pro ATC-X?

 

4) Its descent profile was different to conventional aircraft with the overriding requirement to be subsonic 25nm before land. Would I have the option of starting my descent earlier or later than instructed or is it mandatory to start down only when instructed? Concorde would slow to 350kts IAS before initiating a gentle descent that became progressively steeper at Mach 1.5 and steeper still below Mach 1.

 

And thinking way ahead when you record new call signs could you also include Speedbird Concorde?

 

Thanks.

 

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.

[modano 20]

i use pro flight planner to make flightplans, and load them into pro-atc

 

i had 0 succeded flights, it seems that theese to wont work very good together.

 

my plan seems right but pro-atc suddenly want me to go to another waypoint that is not in my plan, so i am about to give up pro-atc

 

today i only godt clearence to 4000 feet and then i heard nothing from atc, very stange.

 

i have installed airac, rebuild scenery and align it. i use 1,702

[tf51d 284]

 

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.

 

Actually that would only be only 7 step climbs at 5000ft for the first 4 and 4k for the last. Set initial cruise altitude to 26K, then when ready request altitude change at 5k intervals (Last one 4K).

[alpha117 73]

Modano,

 

Have you reported this in the PRoATC forum?

 

 

Please send the PFPX exported FP so we can have a look.

 

How have you setup PRoATC Options>In-flight

 

Have you sent us your log file from ProATCX

 

Are the AIRAC in PFPX and ProATC the same cycle?

 

 

Lots of questions, and I expect a very simple answer to your issue.

 

Just ask in the correct place

 

 

That's all there is to it, to be honest

[Jarkko 59]

i use pro flight planner to make flightplans, and load them into pro-atc

 

i had 0 succeded flights, it seems that theese to wont work very good together.

 

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.

Edited October 13, 2015 by Jarkko

[modano 20]

im not saying i does not work, i just wonder what happen to my flights!!!

[tf51d 284]

I think I may know the problem, if this happened on approach. I was on a flight from KATL-KSFO last night, all went well up to initial approach clearance, I was cleared by voice to ILS 28R with the MOD5 Star During that approach I was vectored to the SHAKE intersection, which is not part of the MOD5 rnwy28R approach, I followed the instruction at which time I was cleared to final to Runway 19L. Shake is is line with that runway but I was never told of the runway change until that point.

[Ray Proudfoot 9,032]

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.

Thanks for your reply Jarkko. That would be useful but not a show-stopper.

 

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.

I've seen Tom's reply saying it would only need 7 requests. A few more than RC. Normally I would request FL600 but if I didn't make it I would be shouted at like RC. No difference there although in RC I can request deviations for turbulence which switches off the monitor.

 

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)

Doesn't sound ideal for Concorde.

 

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.

But if PATCX ordered me down first sounds like I would have to comply. I do have the manual descent option in RC.

 

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.

I think you're right. A 30 day trial version would have been useful especially when it's an expensive product.

 

Concorde did have a rule set all of its own so it would be a bit much expecting PATCX to cope with every scenario. Oh well, I'll keep using RC for now.

[Pete Dowson 558]

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.

 

Sorry for butting in, but the speed restriction on DESCENT is actually very infrequently removed.  The main question I think is can it be relaxed, on request on the climb. In real life it is often ok, and for some aircraft types (Concorde included. I think) is relatively normal.

 

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.

 

Not quite! Assuming you can get 5000 increments every time, 240 / 50  would be 5 times.  Even if the 1000 restriction operated it would still be 24 times, not 48. remember one FL = 100 feet.

 

I hope to be trying the ProATC/X update soon. So busy at present with P3D version 3 headaches! ;-)

 

Pete