1

Topic: ver 2.6 beta 2 WIN/MAC 64 bit

First beta, please use it if you really want take part in beta-tests

v.2.6 MCDU internal structure and internal data transfer code have huge difference compare with 2.5 and become like a330 now. For this reason a number of issue may happen for this beta stage.

beta 2 Change list (from beta1 stage)
+ADIRS alignment fixed
+color of CSTR at FPLN page change to magenta
+airport,vor,etc ND drawing fixed
+reading light fixed
+navData folder changed to ../X-PLANE 10/Custom Data/GNS430/navdata/ (not overwrite by installer)
+transponder automode changed to intruders show only
+FA voice selector deleted
+"CR/VR" legs drawing fixed for SID/STAR
+"VD" legs drawing fixed for SID/STAR
+some minor text displacements for MCDU

ver 2.6 beta 2 WIN/MAC 64 bit
So, this is the next 320 MCDU/ND improvements - reworked flightplan path (add TMPY FPLN, GA FPLN, ND), new SASL v2.4 implemented (should fix CTD when exit X-Plane), add Saitek Throttle Quadrant support (for LG, Flaps, GSpoilers control)

———————————————————————————————————————
——————————HOW TO INSTALL:——————————————
———————————————————————————————————————

Download link http://jardesign.org/a320/download/inst … V2.6b2.zip

HOW TO INSTALL:
  - be sure, that you use X-Plane 10.41 (64 bit only)
  - copy unziped "320neo_JARDesign" folder to ..\X-Plane 10\Aircraft\ folder
    (be sure, what you are not use nonEnglish symbols in aircraft installation path)
  - start X-Plane 64 bit and open a320, activation window is going to show up
  - enter your serial key (Regcode), click NEXT and after a successful activation reopen aircraft via X-Plane menu
  - activation works well with both MAC/WIN 64 bit

If your activations are over (activation error) - use contact official support http://www.jardesign.org/ticket/kb/faq.php?cid=1

———————————————————————————————————————
——————————IMPORTANT NAVDATA NOTES:————————————
———————————————————————————————————————

FMS NAVDATA Update:
v.2.6b2 use NavData from
../X-PLANE 10/Custom Data/GNS430/navdata/ folder
if not find there - will try to read it from
..X:/X-PLANE 10/Resources/GNS430/navdata/

If you need update your cycle, please use Aerosoft/Navigraph
- “a320/330 Native format” or (the same in fact)
- “XPLANE_GNS430_777WORLDLINER_FF757PROF_NATIVE”
and put new cycle to ..X-PLANE 10/Custom Data/GNS430/navdata/ folder


———————————————————————————————————————
——————       "BETA" is version for Beta-testers!!!    ———————————
———————————————————————————————————————

This is beta version for X-Plane 10 64 bit. "Beta" mean what some may work wrong. Please report about wrong thing, but only thing what changed in this beta - Flightplan part, MCDU work, ND work

Please not discuss things what are not in "whats new" list. Please post your opinion direct here. When you post some, please follow some rules like this http://jardesign.org/forum/viewtopic.php?id=861

Of particular importance will be issues:
- Drawing (wrong, sure) SID/STARS on the Nav display (please attach a screenshot of true drawing from documents and wrong drawing from your ND, specify the SID/STAR, approach, runway, name of the airport, AIRAC cycle and provider)
- Displacement of characters on the MCDU screen (attach screenshots please)

Please read a FAQ before you post a bug http://support.jardesign.org

2 (edited by AUA1377 2015-11-29 10:00:53)

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Good morning!

I just did another test flight, to be precise I just programmed the departure route for a flight LOWG-LOWI. About an hour ago I tested this with beta 1, now I checked if the same issues exist in beta 2 (they do) and created new screenshots.

Departure runway at LOWG was 17C, SID was MILGO5G
NavData: current (XPlane_GNS430_777Worldliner_FF757Prof_NATIVE_1512)
Windows 8.1 64bit / XP 10.42

Things I noticed:

  • EDIT: just forgot that issue - in LOWG, there are three runways (17L, 17C and 17R), but 17L and R are grass runways, so the FMC should not display them when selecting departure runways and routes:
    http://jardesign.org/forum/img/m/1278/t/p1a59ag8q75d8o4879ic7ndo13.jpg

  • See pictures 1-3 (FMC) -> When just selecting the departure route (for example when doing a short flight and not knowing how ATC will continue after the waypoint the SID leads to), altitude calculation fails. If there is a FPLN discontinuity, the JAR320 FMC sets the altitude of the destination airport (LOWI, 1907ft) for the last waypoint before the discontinuity. That's wrong, because it should calculate the altitude as there would be a direct instead of the discontinuity. So the altitude for MILGO should be approximately FL160 as the T/C (FL200) is located after MILGO.

    http://jardesign.org/forum/img/m/1278/t/p1a598j8mrrhl1v0t1mg8gu3127r3.jpg

    http://jardesign.org/forum/img/m/1278/t/p1a598j8ms1pt41cgtm1a4kqvgj4.jpg

    http://jardesign.org/forum/img/m/1278/t/p1a598j8ms19d62481k7u10ah12iv5.jpg

  • See picture 4 -> CA3500 is drawed shortly after the runway, and there is no realistic path curve, just a new line to MILGO.

    http://jardesign.org/forum/img/m/1278/t/p1a598j8ms3f81kdq1oof1tqbduj6.jpg

  • See picture 5 -> After departure I activated the AP to see if it is able to follow the path. The result was a little bit strange. It started turning right BEFORE reaching the altitude constraint of 3500ft. It just started the turn at 2250ft (as readable in the screenshot) and I got a terrain warning.

    http://jardesign.org/forum/img/m/1278/t/p1a598j8ms17h3e712mo1rh7icb7.jpg

  • See further pictures -> It did the full turn to come back to the direct line from CA3500 to MILGO. So the aircraft did a right turn first, heading right of MILGO and then a left turn to intercept the planned direct line to MILGO - instead of just heading direct to MILGO.

    http://jardesign.org/forum/img/m/1278/t/p1a598j8ms1preij21b1p1v0s1n458.jpg

    http://jardesign.org/forum/img/m/1278/t/p1a598j8ms1btk1iurcfp1d2hl8g9.jpg

    http://jardesign.org/forum/img/m/1278/t/p1a598j8msjbm1aijqbg1l64a2qa.jpg

    http://jardesign.org/forum/img/m/1278/t/p1a598j8ms9rs1h1enc656kkk7b.jpg

    http://jardesign.org/forum/img/m/1278/t/p1a598j8ms1vhb1c7b1bu610vkia7c.jpg

Chart information concerning MILGO5G SID:

http://jardesign.org/forum/img/m/1278/t/p1a599jej3jmcgm105rluf1aapt.jpg

http://jardesign.org/forum/img/m/1278/t/p1a599jej3unb1lv631c2veuos.jpg

Complete chart: http://eaip.austrocontrol.at/lo/150724/ … 4-1_en.pdf

As far as I discovered, the issues above are not only a LOWG problem (I also had similar ones at other airports). It's a general JAR320 problem handling SIDs and FPLN.
I'll continue testing, hope this report was helpful.

Post's attachments

Attachment icon bbox_log.txt 2.4 kb, 318 downloads since 2015-11-29 

3 (edited by mruane 2015-11-29 10:34:11)

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Now that the A320 is using the GNS430 navigation data can anyone confirm whereabouts I should file updated PROC files. I have two PROC files that I have modified to add new STARS i.e. YSNF.TXT and NWWW.TXT. Should these updated TXT files be saved in:

..\Custom Data\GNS430\Navdata (as mentioned in the release notes)

or in

..\Custom Data\GNS430\Navdata\Proc

I don't want these files overwritten and any navdata updates.

Cheers Mike
iMac 27" Mid 2011, MacOS Sierra v10.12.1, i5 Intel 3.1Ghz, 16GB RAM, AMD HD 6970M 1024MB - Logitech Extreme Pro, X-Plane 10.51

4

Re: ver 2.6 beta 2 WIN/MAC 64 bit

mruane: If you update airac cycle, you need update every files and PROC folder in NavData folder

AUA1377: thanks, will check!

Please read a FAQ before you post a bug http://support.jardesign.org

5

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Hi !

Sorry, but this does not look ok...

more infos: look here: http://jardesign.org/forum/viewtopic.php?pid=7471#p7471

http://jardesign.org/forum/img/m/552/t/p1a59frh2m1ih03t2inae8i1ben3.png

best regards...

6

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Hi !

Just had a look at the diffrent datas:
included in your A320_2.5B1 (1210):
EDNY.txt:
SID,AMIK2E,06,5
FA,RW06,47.667250,9.501003,0,KPT,0.0,0.0,58.0,2,1800,0,1,0,0,0,0
DF,NY063,47.708733,9.608142,0, ,0.0,0.0,0,0,0,1,220,0,0,1
DF,NY064,47.646006,9.661478,2, ,0.0,0.0,0,0,0,1,0,0,0,0
TF,NY065,47.602808,9.549867,0, ,0.0,0.0,0.0,0.0,0,0,0,1,0,0,0,0
TF,NY066,47.600136,9.329775,0, ,0.0,0.0,0.0,0.0,2,6000,0,1,0,0,0,0
TF,NY046,47.558197,9.223356,0, ,0.0,0.0,0.0,0.0,0,0,0,1,0,0,0,0
TF,AMIKI,47.573889,9.037500,0, ,0.0,0.0,0.0,0.0,2,7000,0,1,0,0,0,0

1511:
SID,AMIK2E,06,5
CA,0,58.0,2,1800,0,0,0,0,0,0
DF,NY063,47.708733,9.608142,0, ,0.0,0.0,0,0,0,0,0,0,0,1
DF,NY064,47.646006,9.661478,2, ,0.0,0.0,0,0,0,1,220,0,0,0
TF,NY065,47.602808,9.549867,0, ,0.0,0.0,0.0,0.0,0,0,0,0,0,0,0,0
TF,NY066,47.600136,9.329775,0, ,0.0,0.0,0.0,0.0,2,6000,0,0,0,0,0,0
TF,NY046,47.558197,9.223356,0, ,0.0,0.0,0.0,0.0,0,0,0,0,0,0,0,0
TF,AMIKI,47.573889,9.037500,0, ,0.0,0.0,0.0,0.0,2,7000,0,0,0,0,0,0


thomas_99 wrote:

Hi !

Sorry, but this does not look ok...

more infos: look here: http://jardesign.org/forum/viewtopic.php?pid=7471#p7471

http://jardesign.org/forum/img/m/552/t/p1a59frh2m1ih03t2inae8i1ben3.png

best regards...

7

Re: ver 2.6 beta 2 WIN/MAC 64 bit

I test the new beta  with a flight LFML to LFST.

I noticed :
-IRS align should take 7 min but 1 min later the ND is already OK (is ti also so in real planes ?)
-no button sound when clicking on the APU fire test and ENG Fire (with BSS soundpack I had sound before)
-the same with the EXT power button
-the plane don't follow exactly the nav path (see photo)
http://jardesign.org/forum/img/m/1125/t/p1a59pqola1qto21v1a3k1i1d1bna4.jpg


-no sound when turning button on the FCU setting altitude, speed and heading
-Fuel Pred Page in MCDU is on 0 (at start or during the flight)
-it would be  great to have the possibilty to enter speed constraints on the MCDU and programming the Climb Page on the perf menu
-also as for the A330 it would be OK to enter the alt, baro set ... with the mouse
-no 320 NM range possibility with the display selector
-Top Of Climb Prediction from flight plan always 15 NM more then on the prediction Perf Menu (MCDU)
-Is it possible to have on the ND a symbol for the Intercept Point for actual aircraft descent path and FMGC computed flight path
-at start of the planes (mode Cold and dark) it is possible to have the orange cross symbol on the Upper Ecam
-When in cruise phase how to "recall" the cruise page" after having push on another page

Thanks a lot for all your great work

8 (edited by Le Docteur 2015-11-29 19:04:57)

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Hi !! Really really great job on Flight Plan and MCDU.
But I still can't have ATC from x plane anymore... any idea ?

This is also not working correctly with airfmc.
Flight Plan page is black, and some trouble on perf page.

9

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Le Docteur wrote:

Hi !! Really really great job on Flight Plan and MCDU.
But I still can't have ATC from x plane anymore... any idea ?

This is also not working correctly with airfmc.
Flight Plan page is black, and some trouble on perf page.

As soon as we complete new MCDU improvement, i will play around AirFMC.

About ATC.. No sound or no ATC?

2 amischkowitz: will take in account

Please read a FAQ before you post a bug http://support.jardesign.org

10

Re: ver 2.6 beta 2 WIN/MAC 64 bit

For AirFMC...did you update the plugin? There is an update on their website. Try it!
Thanks for the various corrections Jar.

I also experienced the "blinking" displays problems in previous beta. May be you can check it if you try to load the plane at night, then during flight switch to day, then back at night...and so on. This happened to me only during a flight where I changed a couple of times the x-plane hours.

11

Re: ver 2.6 beta 2 WIN/MAC 64 bit

J.A.Romanov wrote:

mruane: If you update airac cycle, you need update every files and PROC folder in NavData folder

AUA1377: thanks, will check!

Thanks J.A  Alas your response does not really help me. When I next update the navdata, it will update all of the files in the ..\Resources\GNS430\Navdata folder and also the PROC files in the Proc subfolder of that location. That is normal and expected. To protect the two PROC files that I have modified, should they be stored in the following path:

..\Custom Data\GNS430\Navdata  or in a PROC subfolder in that location. Will the A320 pickup the PROC files from the Custom Data folder if they are present and if so, does it expect my updated PROC files to be in a specific location?

Cheers Mike
iMac 27" Mid 2011, MacOS Sierra v10.12.1, i5 Intel 3.1Ghz, 16GB RAM, AMD HD 6970M 1024MB - Logitech Extreme Pro, X-Plane 10.51

12

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Good day,
can you merge the files like on a mac ? If so, then your modified file can be I do believe, the Nav files are so tricky so make a back-up before, going and doing any changing of files ...  and Q:2 / which Nav data are you using Naviagtiph or areosoft since, i know one has a mapping system for the files you can point the files to where you want them to be placed and it will up-date to that location I did on both aircraft and the A320Ne is pulling the data from the GNS430 .. but the A330 is pulling the nav data from it's own data source from the Navigraph data... I hope they help with the main question as for your modified files I would pull them if you don't feel safe and re-place them after the up-date...
captbullett

mruane wrote:
J.A.Romanov wrote:

mruane: If you update airac cycle, you need update every files and PROC folder in NavData folder

AUA1377: thanks, will check!

Thanks J.A  Alas your response does not really help me. When I next update the navdata, it will update all of the files in the ..\Resources\GNS430\Navdata folder and also the PROC files in the Proc subfolder of that location. That is normal and expected. To protect the two PROC files that I have modified, should they be stored in the following path:

..\Custom Data\GNS430\Navdata  or in a PROC subfolder in that location. Will the A320 pickup the PROC files from the Custom Data folder if they are present and if so, does it expect my updated PROC files to be in a specific location?

13

Re: ver 2.6 beta 2 WIN/MAC 64 bit

with AIRAC updated 15.12 vers.1 by Navigraph, LICJ airport most of the STARS missing : no any ILS 20 or 25 no STARS to RWY 25 at all , NO RWY 07 !!! what can i do ? beta 2 versiona little unstable on final ( Xplane 10.42 using)

14 (edited by mruane 2015-11-30 08:44:47)

Re: ver 2.6 beta 2 WIN/MAC 64 bit

captbullett wrote:

Good day,
can you merge the files like on a mac ? If so, then your modified file can be I do believe, the Nav files are so tricky so make a back-up before, going and doing any changing of files ...  and Q:2 / which Nav data are you using Naviagtiph or areosoft since, i know one has a mapping system for the files you can point the files to where you want them to be placed and it will up-date to that location I did on both aircraft and the A320Ne is pulling the data from the GNS430 .. but the A330 is pulling the nav data from it's own data source from the Navigraph data... I hope they help with the main question as for your modified files I would pull them if you don't feel safe and re-place them after the up-date...
captbullett

Thanks captbullet. My question though was related to saving modified versions of the PROC files (I have added SIDS and STARS). Your suggestion to back them up is well taken, but my understanding was that the Custom Data\GNS 430\Navdata folder will override what is stored in the Resources\GNS430\Navdata folder. In which case, any changes I make can be retained beyond a Navigraph update (where my changes would be lost otherwise) by placing the files in the Custom Data folder.

So my question was should the PROC files that I want to keep and not be updated, be placed in the root of Custom Data\GNS430\Navdata or should they be placed in a subfolder called PROCS?  Of course it may be that the A320 does not look for overrides in the Custom Data folder for PROC files. If that is the case then I can just store the files in that location and manually replace new files after the next Nav update.

Cheers Mike
iMac 27" Mid 2011, MacOS Sierra v10.12.1, i5 Intel 3.1Ghz, 16GB RAM, AMD HD 6970M 1024MB - Logitech Extreme Pro, X-Plane 10.51

15

Re: ver 2.6 beta 2 WIN/MAC 64 bit

good day,

I think your second part of you statement is right but this is why I would make a copy of your work and put it in a separate file and place it on your desk top  so, you can add it back to the PROC file ... just incase the Navigraph does not work as intended ... but you are right on the other counts.
captbullett

mruane wrote:
captbullett wrote:

Good day,
can you merge the files like on a mac ? If so, then your modified file can be I do believe, the Nav files are so tricky so make a back-up before, going and doing any changing of files ...  and Q:2 / which Nav data are you using Naviagtiph or areosoft since, i know one has a mapping system for the files you can point the files to where you want them to be placed and it will up-date to that location I did on both aircraft and the A320Ne is pulling the data from the GNS430 .. but the A330 is pulling the nav data from it's own data source from the Navigraph data... I hope they help with the main question as for your modified files I would pull them if you don't feel safe and re-place them after the up-date...
captbullett

Thanks captbullet. My question though was related to saving modified versions of the PROC files (I have added SIDS and STARS). Your suggestion to back them up is well taken, but my understanding was that the Custom Data\GNS 430\Navdata folder will override what is stored in the Resources\GNS430\Navdata folder. In which case, any changes I make can be retained beyond a Navigraph update (where my changes would be lost otherwise) by placing the files in the Custom Data folder.

So my question was should the PROC files that I want to keep and not be updated, be placed in the root of Custom Data\GNS430\Navdata or should they be placed in a subfolder called PROCS?  Of course it may be that the A320 does not look for overrides in the Custom Data folder for PROC files. If that is the case then I can just store the files in that location and manually replace new files after the next Nav update.

16

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Hi,
I was testing now several times the selected Speed vs. managed Speed in v2.5r1 and it would be great that the following Problem is not existent in the new Version 2.6. I did not find any bug Report about in the Forum for 2.5r1, and actually I do not want to be Beta Tester for 2.6. After reading the Airbus Operational Manual I am sure that I did not make a mistake in the handling:

FD = ON
AP1 = ON (or AP2 = ON)
As long the A/THR has not been disengaged the speed can be set and the Mode changes for "Managed Mode" to "Selected Mode",
the engine will be contolled by the A/THR and speed is reduced/raised according to the Pilots speed Settings.
But when once the A/THR has been disengaged, the Speed can not be controlled in selected mode....the AP is not taking into account the Speed Setting. No Change when FD and/or AP will be disengaged and enganged again.

Then the Speed can controlled only in managed mode or by using the thrust Lever, which is raising the work load in the Approach Phase.

17

Re: ver 2.6 beta 2 WIN/MAC 64 bit

I confirm blinking parts in cockpit (ND, METAR arr/dep Display, JAR logo...)
Here is video http://www.twitch.tv/ivota_hr/b/684391998
Look at 1h:50min.

Two test daylight flight were ok. No problem with blinking.

I just bought GndHandling Deluxe and did test flight but at night.
I get blinking.

18 (edited by tngarner 2015-12-01 02:43:05)

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Seeing an issue on the DP out of KSFO to KSAN.  Using AIRAC 1512 from Navagraph

Routing:  OFFSH9 MCKEY LAX BAYVU3

Issue is with the OFFSH9 DP No transition - see FMS.png

From SENZY you fly 203 to the 151 radial of PYE (Point Reyes)  If you map this out there is no way you will ever make the radial prior to WAMMY.  It does not look to me like WAMMY is a mandatory fly over point.

The MCDU seems to force the plane back over WAMMY.  See NAV.PNG


Here is a link to the DP.  https://skyvector.com/files/tpp/1512/pd … FSHORE.PDF

Post's attachments

Attachment icon fms.PNG 931.08 kb, 146 downloads since 2015-11-30 

Attachment icon nav.PNG 629.89 kb, 170 downloads since 2015-11-30 

19

Re: ver 2.6 beta 2 WIN/MAC 64 bit

good day,
wow only on some instruments are they blinking so, can you re-produce the video and when you get the blinking lights I want you to go to an outside view so, I can see where the light is on the aircraft in relationship to the blinking inside.. are you seeing where i am going with this i think this is from your external light but this is a new one for me so, let's take it one step at a time and please Log txt so this can be recorded as a bug! the Log.Txt is a Must on this issue no if and or buts ....!! I can't stress it enough.
thank-you for you help,
captbullett
ps nice set-up


ivota wrote:

I confirm blinking parts in cockpit (ND, METAR arr/dep Display, JAR logo...)
Here is video http://www.twitch.tv/ivota_hr/b/684391998
Look at 1h:50min.

Two test daylight flight were ok. No problem with blinking.

I just bought GndHandling Deluxe and did test flight but at night.
I get blinking.

20 (edited by captbullett 2015-12-01 03:00:46)

Re: ver 2.6 beta 2 WIN/MAC 64 bit

good day,
can i also have the take off runway and  landing RW will work on it now

this is the main route i will use and insert the SID and STARs you are using since, I use Navigraph also,

KSFO SID AVE J1 DERBB J7 REYES J1 FIM J7 LAX STAR KSAN

http://onlineflightplanner.org  is the planner I use I has a A320 FP txt designer already to download once you make your route also you can use it for the A330 also it make life easy ...




tngarner wrote:

Seeing an issue on the DP out of KSFO to KSAN.  Using AIRAC 1512 from Navagraph

Routing:  OFFSH9 MCKEY LAX BAYVU3

Issue is with the OFFSH9 DP No transition - see FMS.png

From SENZY you fly 203 to the 151 radial of PYE (Point Reyes)  If you map this out there is no way you will ever make the radial prior to WAMMY.  It does not look to me like WAMMY is a mandatory fly over point.

The MCDU seems to force the plane back over WAMMY.  See NAV.PNG


Here is a link to the DP.  https://skyvector.com/files/tpp/1512/pd … FSHORE.PDF

21

Re: ver 2.6 beta 2 WIN/MAC 64 bit

i think this is from your external light but this is a new one for me so, let's take it one step

I am going to deep test tonight.

22 (edited by ivota 2015-12-01 11:50:12)

Re: ver 2.6 beta 2 WIN/MAC 64 bit

I just watched my video form twitch TV again.
The blinking started at 0h:38min:33sec.

Possible problems:
1.In that moment, I bring (show) IVAP (IVAO pilot client).
2.Also, on ND there was  traffic, TCAS become yellow square.

23

Re: ver 2.6 beta 2 WIN/MAC 64 bit

The sound the "outer marker", "middle marker", "inner marker" don't work.

Airport: SBCT
STAR: ORANA 1
IAC: ILS W RWY 15

A320neo v2.6 Beta 2
Blue Sky Star A320 v1.1
Windows 10
X-plane 10.42r1
NavDataPro by Aerosoft AIRAC Cycle 1512 R.2

24

Re: ver 2.6 beta 2 WIN/MAC 64 bit

J.A.Romanov wrote:
Le Docteur wrote:

Hi !! Really really great job on Flight Plan and MCDU.
But I still can't have ATC from x plane anymore... any idea ?

This is also not working correctly with airfmc.
Flight Plan page is black, and some trouble on perf page.

As soon as we complete new MCDU improvement, i will play around AirFMC.

About ATC.. No sound or no ATC?

2 amischkowitz: will take in account


Ok thanks jar !

Sorry i mean atis... No sound and no message when settings the correct freq of The airport on rmp

25 (edited by captbullett 2015-12-01 14:59:19)

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Good day,
can you go into "special drop down list / then look for closest ATC that will bring up the list of ATIS also I do believe /// because it will tune your radios.

Le Docteur wrote:
J.A.Romanov wrote:
Le Docteur wrote:

Hi !! Really really great job on Flight Plan and MCDU.
But I still can't have ATC from x plane anymore... any idea ?

This is also not working correctly with airfmc.
Flight Plan page is black, and some trouble on perf page.

As soon as we complete new MCDU improvement, i will play around AirFMC.

About ATC.. No sound or no ATC?

2 amischkowitz: will take in account


Ok thanks jar !

Sorry i mean atis... No sound and no message when settings the correct freq of The airport on rmp