[ Closed ] ver 2.6 beta 1 WIN/MAC 64 bit (Page 3 of 4)

ok, good info, fixed for beta 2

Hi, the navdata used by this version is a bit odd...the updates goes normally in the "custom data" folder, the folder /resources/GNS430/navdata is used only when xplane updates itself, and at the moment is fixed at 1405 AIRAC.

Please consider to use the custom data folder instead of the standard xplane folder, cause otherwise it will be necessary to update manually each time, instead of using, for example, the Navigraph software (that correctly uses the custom data folder)

cheers!

fixed for beta 2

thanks!

Hi!
Thanks. J.A.Romanov.
Is possible set automatically transponder on/off (on takeoff and landing) on Auto mode?.

Hello, Mr. Romanov

Doing some tests whit the new version, i found these problems:

- When attempting to load an approximation, loads a mismatch for instance. Example:

Trying to load RNAV Z RWY 30 from SCSE:

Data from navigraph:
APPTR,R30-Z,30,ANDAK
IF,ANDAK,-30.243633,-71.119122, ,0.0,0.0,4,9000,7500,0,0,0,1,0
TF,CRITA,-30.181986,-71.113886,0, ,0.0,0.0,0.0,0.0,2,6500,0,0,0,0,0,0
TF,TALCA,-30.120333,-71.108669,0, ,0.0,0.0,0.0,0.0,2,5600,0,0,0,0,0,0
TF,LOICA,-30.084619,-71.083761,0, ,0.0,0.0,0.0,0.0,2,5000,0,0,0,0,0,0
TF,RALES,-30.043525,-71.055133,0, ,0.0,0.0,0.0,0.0,2,4200,0,1,200,0,1,0

MDCU load the following procedure:

SID,EDRON1,30,5
CA,0,295.0,2,2500,0,0,0,0,0,0
DF,UMBUX,-30.087414,-71.286181,1, ,0.0,0.0,2,7500,0,0,0,0,0,0
TF,SE270,-30.271117,-71.291908,0, ,0.0,0.0,0.0,0.0,2,12000,0,0,0,0,0,0
TF,SE350,-30.555603,-71.300772,0, ,0.0,0.0,0.0,0.0,2,20000,0,0,0,0,0,0
TF,EDRON,-30.794808,-71.151794,0, ,0.0,0.0,0.0,0.0,2,21000,0,0,0,0,0,0

I am doing some tests, i discovered that the problem is the name of the procedure, by eliminating - cotained in the AIRAC (example: APPTR,R30-Z,30,ANDAK by APPTR,R30Z,30,ANDAK) fix the problem and the MCDU load the corresponding approach.

- The MCDU not read the RF(Radius to Fix) drawing an incomplete approximation (Picture 1)

APPTR,R30-Z,30,ANDAK
IF,ANDAK,-30.243633,-71.119122, ,0.0,0.0,4,9000,7500,0,0,0,1,0
TF,CRITA,-30.181986,-71.113886,0, ,0.0,0.0,0.0,0.0,2,6500,0,0,0,0,0,0
TF,TALCA,-30.120333,-71.108669,0, ,0.0,0.0,0.0,0.0,2,5600,0,0,0,0,0,0
TF,LOICA,-30.084619,-71.083761,0, ,0.0,0.0,0.0,0.0,2,5000,0,0,0,0,0,0
TF,RALES,-30.043525,-71.055133,0, ,0.0,0.0,0.0,0.0,2,4200,0,1,200,0,1,0

FINAL,R30-Z,30,G,4
IF,RALES,-30.043525,-71.055133, ,0.0,0.0,2,4200,0,1,200,0,0,0
RF,PELIC,-30.001003,-71.048519,1,ARC01,317.9,3.2,2,3400,0,0,0,0,0,0
RF,SEREN,-29.967384,-71.080678,1,ARC01,294.4,3.2,2,2560,0,0,0,0,2,0
TF,RW30,-29.920292,-71.190556,0, ,0.0,0.0,295.0,6.4,1,531,0,0,0,0,3,1
TF,BARCA,-29.816667,-71.432222,0, ,0.0,0.0,0.0,0.0,2,3000,0,0,0,0,0,1
HM,BARCA,-29.816667,-71.432222,1, ,0.0,0.0,115.0,04,0,0,0,0,0,0,0,0,0

If i change the RF by TF in the AIRAC, MCDU loading it properly but without the ARC

-When you load the flight plan, if the path is very long whitout inserting the temporary plan, path goes blank. To not miss this, is necessary to keep adding points and go inmediately inserting the temporary path.

- ZFW and BLOCK are somethat displaced

- In the SID DONTI1B from SCEL departing from the procedure indicates that you must start the turn by passing 4000 feet, so the MCDU inmediately crank the plane without passing 4000 feet.

SID,DONT1B,17L,4
CA,0,175.0,2,4000,0,0,0,0,0,0
DF,SEKSU,-33.472489,-70.985972,2, ,0.0,0.0,4,9000,7500,0,0,0,0,0
TF,EL370,-33.202808,-71.091550,0, ,0.0,0.0,0.0,0.0,2,11000,0,0,0,0,0,0
TF,DONTI,-32.950097,-71.189867,0, ,0.0,0.0,0.0,0.0,2,13000,0,0,0,0,0,0

Everything else looks good, thank you very much for the great work and updates

As I see, AUTO position just limit displayed traffic for intruders only. For now, i am done this for beta 2. Please check how correct it will work.

Possible do delete DISC after you insert runway w/o SID etc.

Thanks for other info, but.. you are not attached any docs, what will be useful to start discussion, cause i am not agree with many points, sorry.

I dont have any docs but a video of the real a320 , please start watching from minute 6

https://youtu.be/9fqy8uPzW90

pay special attention to the pitch part which currently is where the most problem relies

Good day,
X-plane A320Ne (this video is done in parts for Up-loading)  this is the first flight of the JAR beta 2.6.1 A320Ne the route is a VOR route from,
         //*  LEPA/LEBL : LEPA SID ESPOR W2 NEPAL STAR LEBL ///                  The MCDU worked very good and I found the improved route to work well saying that I never had any issues before but the curved arching flight plan is more natural as you do not want to bounce the PAX around ... I say good job JAR ... i hope this might help if you are having issues  you might see something that will help you out ...
your friend,
captbullett X-Plane.org 

Once you click on the link just click on my name and it will take you to my channel which has all the videos   

https://youtu.be/nhTyl0ZVwqo
https://youtu.be/sYXHFRyszPY
https://youtu.be/Dk9M2uT5BCU
https://youtu.be/41VJqP8rLm4
https://youtu.be/Kd1_QiaAVz8
https://youtu.be/NgBCIlUtZLM

or go to my channel ; https://www.youtube.com/channel/UCY6Y_3 … ji6Q3NMG4Q

Testing v2.6 from SAEZ to SCEL.
Everything was fine, but between UMKAL to LOSAN I've need to correct heading manually because A320neo lost airway to SAFEL. After the correction was made and heading was recovered, AP1 & AP2 can't follow GS for landing (SCEL).
Can't set Go Around Altitude.

good day,
this also goes for the A320Ne Ok this way we can better serve more people ... this is a re-post ... and when it come to navigation we need the whole route take-off runway and landing runway you plan to use then we can give you something to use ... ok...
thank-you
Hello all together,
well the A330 is released and now every day there are multiple topics poping up in the forum.
So to keep the work for Jar and Slava easy and structured, I would kindly ask all users to use a standardized bug reporting.

We used that in the alpha/ beta phase and it was quite well because you clearly could see which bug was fixed, if there is a discussion about bug and so one.
So my suggestion are:
1.Search the forum before you open a new topic. Your bug might be already reported.
If your bug is already reported:
Post your findings to this existing topic.
If your bug wasn't reported before:
2. Open a new topic
3. Choose a Topic subject which describes your bug in the most shortest form and use one of the following to identify your problem in front of your topic subject:
[sys] for bugs concerning the aircraft's systems
[fpln] for bugs concerning flight plan
[vis] for bugs concerning the outside/ inside look of the 3D objects
[other] if you can't put your bug into one of these categories
4. Describe your bug precisely as possible in the write message field.
5. Attach X-Plane Log.txt and A330 bb_log.txt.
6. If possibile add sources from FCOM, POH, AMM proving JarDesign's A330 is wrong.
And last the most important point for a fast fixing of bugs is that you please post only one bug into one topic

To my mind if we all spent the time to do our bug reporting like that way, JarDesign could easily work through the reported bugs
Best Regards
Lukas