srcooke

Would Pro ATC-X and the NGX have some incompatibility lurking somewhere? Please help me with this.

Possibly, but neither myself or the developer can reproduce it, and I have loaded many fights via the ProATC plan.

Indeed the only time I ever encountered a PIN ERROR ProATC wasn't used at all so clearly the issue isn't solely related to ProATC.

I did submit a ticket with a ProATC flightplan attached requesting assistance in identifying any issue but it was declined as a ProATC issue.

I was playing around and somehow changes to setting, because every time i reach TOD ATC never tell me to descend. Where can i change this?

ProATC-X Support Forum

Sorry Bryan, this is an FSX install.

The sound system is the same as used in Reboot or the Airbus.

 

Confirm the INT slider in the VHF display is Green, not white when  you're twisting the SERV/INT button on the Capt's side.

Confirmed and I cannot reduce the loud volume either, v1.5 + Q400 Pro

This is no help to you but I have randomly had this error even if I'm not running proatc so it isn't necessarily caused by that program. I have to reload to get it working again.

 

Chris

Thanks Chris, it is of help in that the issue does not appear to be ProATC specific, I cannot reproduce the problem at all whilst using the ATC program generated company route.

There is however an issue that if you load the enroute winds BEFORE entering the arrival STAR & RWY the NGX FMC will lockup and an error logged. This is totally reproducible and on an open PMDG ticket.

Solution for that problem is load the departure/arrival information prior to the wind entries. Is there any relation between the problems encountered, your guess as good as mine but there were no issues reported regarding ProATC prior to SP1D and neither did the wind entries cause the FMC to fall over without an arrival set.

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.

I just installed pro.atc 1,702 and took a trip from stavanger to copenhagen

 

NO decent clearence

No landing clearence

 

i Heard nothing from Pro-atc

 

its worse than before the update. so therefore goodbye pro-atc!!!

Still haven't seen a request for help on the support forum. Not going to help you out here.

what should we write in pmdg 737 when using pro flight planner and pro-atc

 

ekbiekch.clr not working

ekbiekch-x  working

 

after takeoff climp to 4000 feet then decend to 3000 and bum crash

 

im not impressed.

If you are a legitimate product user with an issue please post on the official support forum

I'm unable to locate your observation there.

Tried three different computers, each using a different web browser. The 'verification' letters do not show, so I cannot regester.

I would suggest you try following the steps here: Captcha not Displaying

You could try opening the recording/microphone properties and de-selecting 'Allow applications to take exclusive control of this device'.

I don't have the issue as I run vPilot on a client.

Just for info the LFMQ issue previously reported should be resolved when using Navigraph data. It was a result of undefined waypoints in the procedure file.

Re the Oslo problem, the work around, should you need it, is to replace the Alpha_Flatten.bgl with Allpha_Flatten.off before you run Make Runways. Once Make Runways has completed rename Alpha_Flatten.off to Alpha_Flatten.bgl again.

Hello Mike,

The latest version contains the flatten fix previously posted on the Aerosoft forum. (1.06)

Sent you a PM Rob.

Steve,

 

As a new user, can I purchase the software? I can't find it on FSS...

 

Thanks,

 

Rob

Now sold through FastSpring

Currently the NGX and I believe the T7 also cannot handle the dual ILS fequencies. Confirmed on a PMDG ticket more than 18 months ago following a discussion on Navigraph!

Peter, re-ordering the line entries so the ILS is listed first should be a useable workaround, again posted on the Navigraph forum.

I was referring to the OP's post

select my COROUTE from a previously planned flight plan from PFPX

 

Try setting the PMDG export paths in PFPX as:

Are you commanding "FLAPS 0, I A S ONE EIGHTY FIVE, CLIMB CHECKLIST TO THE LINE". after to FO has announced "ACCELERATION"  based on the MDA bug set during the pre-flight?

I shall have to give up entering en-route winds until the issue is fixed and accept the loss of the associated predictions. On my last flight I needed to divert to my alternate due to weather and of course as soon as I changed the destination the arrival runway was deleted and the systems locked up immediately.

Just to note this issue occurs with both FSX and Prepar3D.

I no longer have the 767 installed.

I suggest you search the official forum for "FSX Radio Problem"

Certainly when running Squawkbox powering the centre hydraulic pumps prior to connecting to Vatsim got over the issue.

Try turning on the electric hydraulic pumps before connecting to the network.

Topcat could and can load the FS9 737 whereby the pax and cargo data could be transferred to the aircraft it cannot however be used to load the NGX.

The best option is to simply use the ZFW figure and enter this in the FMS whereupon weights will be distributed, don't worry about pax numbers or cargo load.

The Navigraph AIRAC 1505 indicates a runway length of 1529m, 5016ft:

GIBRALTAR               LXGB09 05016089 36.150883  -5.358103000.0000000012
GIBRALTAR               LXGB27 05016269 36.151472  -5.341170000.0000000012

which is correct from the AIP:

both runways have extensions:

the LDA remains at 5016'.

Here is the the thread which is on an open ticket with PMDG.

Thanks Michael, I have indeed checked your solution on the errant route and was successful in completing the FMC setup.

For me it linked to the IRS alignment in that I could enter all  the en-route winds prior to alignment completing, once it aligned however it all went haywire. What puzzled me for a while was that I then couldn't load a default panel state in working order, eventually I found clearing the failure timers for the specific aircraft .ini got me in a working position again.

EDIT: I mentioned your findings in the ticket