Airbus und Pro ATC X

[lowHitman 1]

Hi,

ich nutze neben dem Airbus A318,19,20,21 Pro ATC X um meine Flüge zu planen, etc.

Über Pro ATC X werden auch die Frequenzen im Cockpit automatisch ein- bzw. umgestellt, dies lief bis dato immer einwandfrei.

Seit dem aktuellen Update 1.30 jedoch funktioniert diese "Automatik" nicht mehr, bzw. nicht mehr vollständig. Auf dem Boden ist noch alles in Ordnung aber nach dem Start werden plötzlich keine Frequenzen mehr geändert.

Bitte um Hilfe bei der Lösung da ich sonst nur auf die "alte" Version zurückgreifen kann

[kides7 3]

Ja, das stimmt. Ich habe das gleiche Problem. Aber es ist nicht immer, 2-3 mal pro Flug und nicht immer wärend des fligen manchmall auch auf dem Boden.

PS. Benutze P3D v2.5

[airway 8]

The same here.

[FwFreak 2]

Before V1.30 everything worked fine. But now I have the same problem. Not any time, but often.

[Cheyenne Chief Pilot 829]

It works OK with RadarContact in FSX-MS. RC can tune in and change freqs in v1.30.

[darrro87 3]

have the same issue.. is there any solution ?

[Jarkko 39]

It works OK with RadarContact in FSX-MS. RC can tune in and change freqs in v1.30.

The difference might be that RC uses FSUIPC while ProATC uses SimConnect. Maybe the shared cockpit changes effect add-ons that use SimConnect?

[FwFreak 2]

I had this issue this evening on a flight from LOWI to EDDF 3 times (and on every flight since the SP3).

Today Pro-ATC/X was unable to switch to the Tower frequency before take off, a second fail while CRZ (switching to a Center) and at least on the Approach switching the Tower frequency to receive the landing clearence.

It's not possible to let the Airbus fly alone for a while on longer flights

[Jonas S. 466]

"It's not possible to let the Airbus fly alone for a while on longer flights"

What do you mean with that? You can surely let the airbus fly with the ap on.

Jonas

[Jarkko 39]

"It's not possible to let the Airbus fly alone for a while on longer flights"

What do you mean with that? You can surely let the airbus fly with the ap on.

Jonas

It means that you can't let ProACT co-pilot handle the frequencies anymore with ProATC, when using SP3. This then means, that you can't leave the computer as, you might miss a frequency change.

In the past (SP1, SP2), you could leave the aircraft to cruise and let the co-pilot "monitor" and handle radios.

[FwFreak 2]

Yes! Thats exactly what I mean.

[lennylion 0]

I have this issue ,since installing sp3 and unable to tune the tower frequency

any one put this on the pro atc forum ?

[Jarkko 39]

I have this issue ,since installing sp3 and unable to tune the tower frequency

any one put this on the pro atc forum ?

Yes. Many users have reported this on the ProATC forum. From the logs, that the users have posted, it can be seen that the Airbus SP3 version keeps setting the same active frequency over and over and over again (about 3-10 times every second).

No other aircraft has this behaviour.

[vysous 5]

I guess this has nothing to do with Pro-ATC. I use stock "autotune" feature from ATC menu - and sometimes it does not tune the frequency I click on (in ATC menu) and I have to do it manually. 1.3c HF installed.

[Charn 2]

Hello,

I like to know only 1 thing. Does the aerosoft will fix this problem?

Because the other add-on aircraft doesn't have this behavior.

[kides7 3]

A 320 CFM reagiert sehr schlecht auf umschalten die Frequenzen, manchmal muss man 4-5 mall umschalten damit die Frequenz Aktiv wird. Und es ist egal mit oder ohne ATC-PRO. Und das ist seit version 1.30. Kein einzigen Hotfix hat dieses Problem gelöst.

[Jarkko 39]

A 320 CFM reagiert sehr schlecht auf umschalten die Frequenzen, manchmal muss man 4-5 mall umschalten damit die Frequenz Aktiv wird. Und es ist egal mit oder ohne ATC-PRO. Und das ist seit version 1.30. Kein einzigen Hotfix hat dieses Problem gelöst.

You are correct, also people using the default FSX ATC users are having problems. There was also a report, that it effects flying online.

My guess is, that reason can be found from a log that a ProATC user posted. This small snippet of the log contains 68 "frequency change/update" events within 4 seconds:

2015.04.22/22:08:08 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:08 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:08 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:08 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:08 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:08 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:08 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:08 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:08 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:08 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:08 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:08 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:08 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:09 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:09 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:09 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:09 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:09 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:09 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:09 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:09 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:09 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:09 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:09 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:09 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:09 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:09 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:09 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:09 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:09 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:09 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:09 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:10 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:10 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:10 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:10 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:10 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:10 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:10 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:10 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:10 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:10 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:10 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:10 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:10 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:10 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:10 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:10 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:10 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:10 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:11 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:11 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:11 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:11 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:11 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:11 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:11 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:11 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:11 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:11 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:11 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:11 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:11 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:11 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:11 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:11 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:11 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940
2015.04.22/22:08:11 - - ComRadioUpdate: status=0; avmaster=1; activefrq=11940

Normally you only get one of these events, when you change a radio frequency.

In this case, SP3 seems to flood FSX/SimConnect with a message, that active frequency has been set to 119.4 (or what ever frequency you have tuned as active). As mentioned before, no such problem with SP1 or SP2.

[kides7 3]

So, my result is that SP3 is worst SP of all time.

[Charn 2]

Does anybody report this problem to developer? or Did they know it already?

I think this problem should be fixed.

[kides7 3]

And what are we doing here? Exactly, we report the problem.

And worst of all, the aircraft can not fly with one engine.

But anyway, I like it.

And what is very good that the team is working on the improvements.

[The Dude 6537]

Does anybody report this problem to developer? or Did they know it already?

I think this problem should be fixed.

We are aware of it by reading this thread. Thanks for reporting and it has been past on to the dev.

[bud 3]

And what are we doing here? Exactly, we report the problem.

And worst of all, the aircraft can not fly with one engine.

But anyway, I like it.

And what is very good that the team is working on the improvements.

LOL, good one.

Me too, actually I don't like it, I love it.

Since we're talking about radio stuff, I'd love it even more if Airbus radio would have VHF2 (COM2) Receive (listen) turn-knob independent, so it does not turn off VHF1 Call (Mic) off.

I know I can have VHF1 back on by turning its turn-knob to off and then back on, then VHF2 stays on the way I want it.

It never bothered me before bot now that I'm using PRO-ATC-X, after contacting tower and for remainder of the flight, it is that initial VHF1 Call (Mic) off that causes "! CTRL[#] is inactive" where PRO-ATC-X no longer interacts with user aircraft.

Configuring and leaving VHF2 (COM2) Receive (listen) on at the gate with VHF1 both on for entire flight causes other unfriendly problems.

But for now I still have 1.21(d) source files and I guess I'll remove v1.3 until initial problems is fixed.

Cheers,

Michael

[lowHitman 1]

me too , i'll uninstall 1.30 and go back to 1.20 - very bad - the Airbus is a great work but 1.30 is no step Forward (framerates are very bad, the frequenzy issue,.... it makes no sense to fly and loose 10 Frames in Cockpit View, 1.20 run faster)

[Charn 2]

I have to park these buses until the permanent solution is deployed.

[FwFreak 2]

During 2 flights this evening everything worked fine using the new Hotfix 1.30d.

Problem seems to be solved. Thanks!