FSX-MS PROATC-X v1.7 Released

[Jarkko 59]

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.

 

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:

Edited October 13, 2015 by Jarkko

[Ray Proudfoot 8,960]

Actually Jarkko it would be 7 requests as Concorde was cleared up to its ceiling of FL600.

 

In comparison to RC I also have to make repeated requests for higher but once cleared above 350 the next option is 570 or possible higher. Certainly fewer than 7 requests - thank goodness!

 

And as Pete noted lifting the 250kt restriction would only be requested on the departure.

[Jarkko 59]

 ... i'm really pleased with how it handles the waypoint altitudes and clearances. this alone makes pro-atc worth it to me so far, as it might be the first ATC i've used that didn't want to clear me to descend into the mountainside at KSQL ... it also perfectly handled the PIGO1J STAR at EGNX and i'm looking forward to setting it up to fly the holds there and at some of the other euro airports where holds seem to be part of the STARS very commonly. i also really liked how easy it is to customize the runways in-use, etc. ...

 

thanks for all the responses y'all

 

cheers

-andy crosby

 

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

Edited October 15, 2015 by Jarkko

[DrumsArt 270]

Hello,

 

By now I have Native Atc with Multi Crew (useful for Vfr), VoxAtc (I like it but there are some "glitches" sometimes), Pilot2Atc (I like this program but it's not possible to run Fsx in full screen mode. So....

 

Just a couple of questions :

 

1/Is it possible to run Fsx in full screen mode with ProAtc-x ?

 

2/Is ProAtc-x can to manage VFR too ?

 

Thanks,

 

Regards,

 

Richard Portier

[Pete Dowson 558]

If there's anyone here from the ProATC-X team, can they tell me why, one my very first post to the re-vamped Forum, reporting a problem, I get this response:

 

     403 FORBIDDEN!     

Either the address you are accessing this site from has been banned for previous malicious behavior or the action you attempted is considered to be hostile to the proper functioning of this system.

The detected reason(s) you were blocked are:
XSS attack (or similar Javascript exploit attempt) in file (FILE-XSS-02).

 

 

This is a very unfriendly way to greet an old user!

 

In case I remain banned from the Forum, could you pass on this, my message:

 

============================

 

Starting to look at ProATCX again, seeing that there are so many improvements in the current version. However, I reach a stumbling block straightaway.

 

I use the PLN format flight plans -- FS9's easy text format normally, but can do FSX's XML format if really necessary (though I hate XML!).

 

However, Pro-ATCX 1.7.2 won't accept either. I attach two PLN files (see below) , both the same plan, one in the easy text format of FS9 and the other saved by FSX in its own XML format. Note that FSX accepts either format readily, as do other programs like Aivlasoft's EFB.

 

Trying to import the FSX XML file gives the error displayed in German shown in attachment 'Screenhunter 01". [Omitted, can't post here!]

 

Trying to import the FS9/FSX compatible flight plan gives the error shown in attachment Screenhunter 02. [Omitted, can't post here!]

 

The log from both attempts is shown below. I've not connected to FSX yet and it doesn't show plan loading errors, so it isn't really useful.

 

I use PFPX to produce my plans and export from there to my other programs -- FSX, ASN, Prosim737, Aivlasoft EFB. I'd like to be able to include ProATC/X but it looks at present that the only way at present is cut-and-paste the text itslef. Is that so?

 

Regards

Pete Dowson

 

=================================

Plan in FS9/FSX compatible format:

 

[flightplan]
AppVersion=9.1.40901
title=EGCC to EIDW
description=EGCC, EIDW
type=IFR
routetype=3
cruising_altitude=18000
departure_id=EGCC, N53* 21.13', W002* 16.29', +000257.00
departure_position=23L
destination_id=EIDW, N53* 25.16', W006* 16.11', +000242.00
departure_name=MANCHESTER
destination_name=DUBLIN INTL
waypoint.0= , EGCC, , EGCC, A, N53* 21.13', W002* 16.29', +000257.00, 
waypoint.1= , WAL, , WAL, V, N53* 23.30', W003* 08.04', +000055.00, L10
waypoint.2= , IOM63, , IOM63, I, N53* 28.08', W003* 18.57', +000000.00, L10
waypoint.3= , IOM50, , IOM50, I, N53* 35.39', W003* 36.43', +000000.00, L10
waypoint.4= , PENIL, , PENIL, I, N53* 36.56', W003* 39.48', +000000.00, L70
waypoint.5= , BABRA, , BABRA, I, N53* 37.38', W003* 56.42', +000000.00, L70
waypoint.6= , GIGTO, , GIGTO, I, N53* 38.00', W004* 05.50', +000000.00, L70
waypoint.7= , WAL45, , WAL45, I, N53* 38.29', W004* 18.38', +000000.00, L70
waypoint.8= , SOPAX, , SOPAX, I, N53* 38.48', W004* 27.07', +000000.00, L70
waypoint.9= , RAMOX, , RAMOX, I, N53* 39.36', W004* 50.21', +000000.00, L70
waypoint.10= , IOM27, , IOM27, I, N53* 40.11', W005* 08.49', +000000.00, L70
waypoint.11= , BAGSO, , BAGSO, I, N53* 40.47', W005* 30.00', +000000.00, 
waypoint.12= , EIDW, , EIDW, A, N53* 25.16', W006* 16.11', +000242.00, 

Plan in FSX's XML format:

 

<?xml version="1.0" encoding="UTF-8"?>


<SimBase.Document Type="AceXML" version="1,0">
    <Descr>AceXML Document</Descr>
    <FlightPlan.FlightPlan>
        <Title>EGCC to EIDW</Title>
        <FPType>IFR</FPType>
        <RouteType>HighAlt</RouteType>
        <CruisingAlt>18000</CruisingAlt>
        <DepartureID>EGCC</DepartureID>
        <DepartureLLA>N53° 21' 7.80",W2° 16' 17.40",+000257.00</DepartureLLA>
        <DestinationID>EIDW</DestinationID>
        <DestinationLLA>N53° 25' 9.60",W6° 16' 6.60",+000242.00</DestinationLLA>
        <Descr>EGCC, EIDW</Descr>
        <DeparturePosition>23L</DeparturePosition>
        <DepartureName>MANCHESTER</DepartureName>
        <DestinationName>DUBLIN INTL</DestinationName>
        <AppVersion>
            <AppVersionMajor>10</AppVersionMajor>
            <AppVersionBuild>62615</AppVersionBuild>
        </AppVersion>
        <ATCWaypoint id="EGCC">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N53° 21' 7.80",W2° 16' 17.40",+000257.00</WorldPosition>
            <ICAO>
                <ICAOIdent>EGCC</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="WAL">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N53° 23' 18.00",W3° 8' 2.40",+000055.00</WorldPosition>
            <ATCAirway>L10</ATCAirway>
        </ATCWaypoint>
        <ATCWaypoint id="IOM63">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N53° 28' 4.80",W3° 18' 34.20",+000000.00</WorldPosition>
            <ATCAirway>L10</ATCAirway>
        </ATCWaypoint>
        <ATCWaypoint id="IOM50">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N53° 35' 23.40",W3° 36' 25.80",+000000.00</WorldPosition>
            <ATCAirway>L10</ATCAirway>
        </ATCWaypoint>
        <ATCWaypoint id="PENIL">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N53° 36' 33.60",W3° 39' 28.80",+000000.00</WorldPosition>
            <ATCAirway>L70</ATCAirway>
        </ATCWaypoint>
        <ATCWaypoint id="BABRA">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N53° 37' 22.80",W3° 56' 25.20",+000000.00</WorldPosition>
            <ATCAirway>L70</ATCAirway>
        </ATCWaypoint>
        <ATCWaypoint id="GIGTO">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N53° 38' 0.00",W4° 5' 30.00",+000000.00</WorldPosition>
            <ATCAirway>L70</ATCAirway>
        </ATCWaypoint>
        <ATCWaypoint id="WAL45">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N53° 38' 17.40",W4° 18' 22.80",+000000.00</WorldPosition>
            <ATCAirway>L70</ATCAirway>
        </ATCWaypoint>
        <ATCWaypoint id="SOPAX">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N53° 38' 28.80",W4° 27' 4.20",+000000.00</WorldPosition>
            <ATCAirway>L70</ATCAirway>
        </ATCWaypoint>
        <ATCWaypoint id="RAMOX">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N53° 39' 21.60",W4° 50' 12.60",+000000.00</WorldPosition>
            <ATCAirway>L70</ATCAirway>
        </ATCWaypoint>
        <ATCWaypoint id="IOM27">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N53° 40' 6.60",W5° 8' 29.40",+000000.00</WorldPosition>
            <ATCAirway>L70</ATCAirway>
        </ATCWaypoint>
        <ATCWaypoint id="BAGSO">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N53° 40' 28.20",W5° 30' 0.00",+000000.00</WorldPosition>
        </ATCWaypoint>
        <ATCWaypoint id="EIDW">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N53° 25' 9.60",W6° 16' 6.60",+000242.00</WorldPosition>
            <ICAO>
                <ICAOIdent>EIDW</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
    </FlightPlan.FlightPlan>
</SimBase.Document>

[alpha117 73]

Pete

 

Looking into this ASAP

 

Thanks

[Jarkko 59]

The detected reason(s) you were blocked are:

XSS attack (or similar Javascript exploit attempt) in file (FILE-XSS-02).

 

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.

Edited October 15, 2015 by Jarkko

[Jarkko 59]

I use PFPX to produce my plans and export from there to my other programs -- FSX, ASN, Prosim737, Aivlasoft EFB. I'd like to be able to include ProATC/X but it looks at present that the only way at present is cut-and-paste the text itslef. Is that so?

 

Regards

Pete Dowson

 

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.

Edited October 15, 2015 by Jarkko

[MadDog 353]

Pete

 

To echo Jarkko... until there's a permanent fix, the SB3 format works with PFPX.  Set the export path in PFPX to:

 

ProATC folder\import\flightplans.

 

The only issue I've noticed with using the SB3 format is that the final altitude does not appear to be transferred, so be sure to change it as necessary in ProATC.

 

MD

[Pete Dowson 558]

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.

 

Yes, thanks. That works fine.

 

 

The only issue I've noticed with using the SB3 format is that the final altitude does not appear to be transferred, so be sure to change it as necessary in ProATC.

 

Do you mean the cruise altitude? That's a bit of a bummer! I am hoping to try to get the whole process of ProATC/X starting mostly automated, one day.

 

With Radar Contact, which I've been using for years, I plan with PFPX & TOPCAT down on my office PC, then up in the cockpit I use ProsimUtils to get all the plan details on my CDU thence, via my own code in WideClient, into Radar Contact, EFB and FSX (for ASN to use). Never need to go to the Radar Contact PC (outside the cockpit).

 

Stephen sent me an FSX PLN file which loads okay. The one I tried was actually saved by FSX-SE, but the format etc looks identical, so I don't really understand why it isn't accepted. Unfortunately the error message isn't in English.

 

It'll be fixed, no doubt ...

 

Thanks,

Pete

[Jarkko 59]

Do you mean the cruise altitude? That's a bit of a bummer! ...

 

Thanks,

Pete

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.

[Pete Dowson 558]

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.

 

My "cruise altitude" is the one computed by PFPX as the most efficient for my journey taking into account the distance to travel and the winds en route. If I am heavy and can't make it initially, then I would expect to use step climbs, yes, but wouldn't I request those en route? Or perhaps that's what you meant?

 

I fly 738 in "greater" Europe only and like to keep flights to around about one hour, two at most -- the most interesting parts being departure and arrival procedures. Cruising is relatively boring (as in real life), so, for me, my cruise altitude IS my target altitude and one I'd like to climb to ASAP. With Radar Contact one might sometimes be held a bit lower for a while for traffic.

 

I'll see how ProATCX does it when I get a chance to try it properly. Next week I should think! ;-)

 

Pete

[glenm 3]

I am curious if ProAtcX runs in Fullscreen as well.

 

Thanks

[KingOfLeinster 5]

Going to give this a go tonight

[tf51d 284]

I am curious if ProAtcX runs in Fullscreen as well.

 

Thanks

Yes absolutely works very well in full screen mode.