[ Closed ] JD320 Airliner ver 3.1r1,r2 WIN/MAC 64 bit (X-Plane 11) (Page 4 of 9)

Hello.. updated 320 yesterday and seem to have an issue with the overspeed warning staying on even when landed... also plane seems to want to constantly overspeed at no given reason. I also have the 330 and this has no such issues ?

Can't confirm the "flight plan part fixed" feature of this version:

I'm having slight problems with the A320 MCDU. I'm trying to program a STAR arrival to EDDN ILS28, coming from EDDH. So I chose the available ILS28-Z in the MCDU, chose the "NIBIL 6T" STAR and then I would take VIA "PIVIR 28 RNAV", but only the "ERLANGEN" is available, which would be for non FMS aircrafts.

a320neo_6.thumb.jpg.c7c75d18a7542bda175d0718a1437ccf.jpg

So I went back to the F-PLN, again took "ILS28-Z", "NIBI6T" and now the other VIAS were shown. So I took the "PIV28", no transition and inserted it to the plan. When I checked the Plan I saw, that the way points were mixed with other STARs and so completely useless.

After that I started searching through the forum, and found out, that this is nothing special, when the A320 MCDU misses a STAR / SID or has some wrong way points in it, because it uses the NAV-data from X-Plane in first place. But after that I tried to build the exact same approach in the 737-800 from Laminar and it worked out without any problems.

So I'm a bit confused. How can be there a difference in the way points, when both MCDUs use the same data? Is there a way to fix this by copying any NAV-data or something like that?
I also checked the way point txt.file in the A320 nav-data folder and the points are set correctly like they should be according to the Navigraph chart:
APPTR,I28-Z,28,PIV28
IF,PIVIR,49.667081,11.416064, ,0.0,0.0,0,0,0,0,0,0,0,0
TF,DN411,49.731758,10.756347,0, ,0.0,0.0,0.0,0.0,0,0,0,0,0,0,0,0
TF,DN422,49.632925,10.734056,0, ,0.0,0.0,0.0,0.0,0,0,0,1,240,0,0,0
TF,DN425,49.589167,11.184889,0, ,0.0,0.0,0.0,0.0,2,8000,0,0,0,0,0,0
TF,DN426,49.572725,11.349400,0, ,0.0,0.0,0.0,0.0,0,0,0,1,220,0,0,0
TF,DN429,49.541742,11.652786,0, ,0.0,0.0,0.0,0.0,0,0,0,0,0,0,0,0
TF,DN436,49.443103,11.628714,0, ,0.0,0.0,0.0,0.0,0,0,0,0,0,0,0,0
TF,DN435,49.453503,11.527817,0, ,0.0,0.0,0.0,0.0,2,5200,0,0,0,0,0,0
CF,CF28,49.471444,11.350611,0,INUW,96.6,11.7,277.0,7.0,2,4000,0,0,0,0,0,0

The NAV-data from X-Plane is updated to N1705 by Navigraph and the A320 MCDU also shows this as the active nav data base.

Also created a ticket for this, but maybe anyone else had this and knows a solution.
Thanks for any help / answer!

The BSS Sound Pack for A320 V4 is now out! Not sure about the wind sounds though.

The issues I'm having is that displays dim during nighttime flying, and the autopilot stops following the flight plan if there's a sharp turn in the flight plan.

Just installed BSS v4 here.

There is an strange air flow sound when you raise the thrust lever until 50% N1. Strangely it follows the lever position and not the actually N1 RPM.

Anybody else noticed that?

I didn't know about that. Sounds promising! 100% of the paywares I bought (a320 included) has problems with the FMC/FMGC, mainly regarding VNAV, LNAV, holds...

Hope this new SDK open some possibilities.

Do you have any more info about this?

The statement that JAR use the same nav data as XP11 is wrong. The AIRAC 1410 data used by JAR when there is no GNS430/navdata folder is the same format as the XP10 GNS430/navdata and is located in the JD320/330 _navdata folder
Understanding is indeed important, and lack thereof it is misleading...

@AlexK
Hi

In XP 11 there is no GNS430 exept if you install it yourself ...
When you load JAR A320 you can see on FMGC the two utilised data bases  ...
if up to date  Airac 1705 on first line
and if you have not changed anything in _navdata folder  Airac 1410 ...on the second line

So JAR utilizes same data as XP 11 ...

Please don't complain before understanding ...

jcdp

My observations:

After takeoff the aircraft does not follow FPLN, but HDG is pushed to managed mode ..... PULL and PUSH the HDG and it follows the FPLN. Maybe some initialization problem ?

During climb with autothrottle and managed mode it overspeeds below 10000, this looks not good in PIREPs for virtual airlines

During descend it does not decellerate enough before passing 10000, giving overspeed below 10000, this looks not good in PIREPs for virtual airlines

The copilote message "reaching top of decend" comes very early, i would prefer to hear it max. 20-30 nm or some minutes before TOD and not greater 100 nm and 1/2 hour before

Hi SinusJayCee, you must do a clean install and re-enter the serial. The official instructions on how to update are the first post in this thread. There it say right in the beginning "Please not mix files with other version".

Thank you for your reply, AlexK! I've read the note about not mixing files. However, I also have read that there is only a limited number of 5 activations per key. So I was wondering whether this is affected by activating an updated version.

Just updated to 3.1r1,r2 and I've noticed a few issues. It's too bad as I think they are things that were working well before update. I did a "clean" install by removing old JAR320 folder and adding new.

1. Normal start procedure for A320 is to start right engine first then left. I did this as I've done in previous versions, Engine shot up to nearly full thrust. Shut down right started left, same. On third attempt, I disconnected ATHR and normal start with no full thrust surges. After start, I re-engaged ATHR. It is not normal to have ATHR inactive. it is always on.

2. After startup, looking at FCTL page, aileron indicator fluttering all over the place. No joystick calibration issue, tried no luck. On visual model, Ailerons are in extreme positions up/down. On FCTL page, rudder also showed full left and on visual model. Although I had full rudder control via controls, surfaces did not respond.

3. On taxi out. (like the change in the FADEC mapping btw), if you pull the thrust to idle, as normal, ATHR disconnects. Not normal.

4. after takeoff, very aggressive pitch up. I had initial altitude set at 8,000. Aircraft leveled at around 3,000' for no reason. I had to PUSH the alt knob to get CLB mode. Not normal.

5. Upon reaching 8,000, Thrust overshoots target 250kts, then aggressively reduces thrust to undershoot 250kts. Then a gradual thrust increase to hold 250kts thrust normally. NOT normal.

At this point I gave up. I wish I had copied of the previous version before installing this one. This version is simply not flyable anymore.

Aaron

I noticed some problems in 3.1 r2:

1. When taking off and after activating the autopilot it levels and only rises again after pressing the altimeter knob.
2. It has a very aggressive reason and climb, out of the ordinary and out of the way levels before the established altitude even without having restrictions in the area.
3. On landing even with a touch of -190, -200 it goes around and disarms the landing mode completely, forcing you to attack without even bouncing on the lane, otherwise it will not brake nor in the manual mode, the safe reverse Much less the aircraft than before it advertised go around.
4. Below 10.000ft it should stabilize at 250kt from mild out, but it will aggressively overrun and "cut" the acceleration to reestablish the speed, with that it drops sharply to less than 240kt and then yes it gradually accelerates up to 250kt.
5. During the descent and near the approach and landing it does not slow down until it enters the approach mode, thus it does not respect in automatic mode the fixed speeds established in letters and the current airac.

One suggestion is to make the latest version available in this case 3.0 which was working better in my opinion, so that until they hit the bugs of that we can be as "round" as possible.

If someone has and can make the link available, I am grateful because I did not keep the version.

Thank you.
Júlio

Curious,

Would it be possible to put a link back for the previous version? I'd like to keep flying while the latest release is sorted.

Thanks,

Aaron