[ Closed ] a320neo JARDesign ver 3.0r1-6 WIN/MAC 64 bit (X-Plane 11) (Page 7 of 11)

Totally agree with you.

Mr. Romanov, it`s a bit frustrating to pay the same amount of the entire x-plane 11 simulator (60 usd) for a single aircraft and the most essential function of its FMS is failing to do its job. Please, don`t get me wrong, I`m totally ok with bugs. Every software have bugs, every payware have bugs and addressing them are part of development process.

But ignoring them and blaming on the user, oh boy... this completely piss me off.

Confirm about thrust behavior, initially it jumps to higher value and then settle down to lower n1

You probably are already doing this i expect but since i haven't got this problem since the r3 release i will ask and say what i'm doing.

You are inputing your route before you input the FL right? I usually insert the whole route (without SID's and STARs) and it has accepted every FL i choose, I went FL310 in 293 nm, trip.

(the new release v3r4 is working perfectly for me! .... but it keeps bothering me that the same Versions are doing different things for each of us.... @_@)

I can't speak for everyone, but you're pretty much wrong about my experience with A320. And no, I earned it not from some youtube videos, but from the actual handbooks for this aircraft (QRH, FCOMs, etc). /brag mode off.

You see, the global problem with JAR320 in its current state is that you have to be very lucky to fly it.

Lucky to input correct CRZ LVL.
Lucky not to die with boredom while entering long flight plan leg by leg by leg by leg by leg (yes, I know about .txt routes, but this is a workaround, not a solution).
Lucky not to wander off course because of the autopilot not working properly.
Lucky to maintain (poorly calculated) vnav profile on descent without jerking speedbrakes up and down.
Lucky not to crash at any given time of your flight.

I can go on and on. But my point is, the real A320 is a very fool-proof aircraft, and JAR's A320 is quite the opposite - it's unreliable.

It doesn't matter, it could glitch with the both ways. Inserting FL after entering route simply increasing your chances to get what you expecting from JAR's FMC.

Correct me if I'm wrong, but per real procedure you can (and probably should) complete the whole INIT page (yes, FL included) before entering FP.

You may also correct me on this one (by quoting real documents), but as far as I know A320' FMC simply cannot, under no circumstances, replace your FL with some own gibberish. It is not your phone auto-correct. It either takes it or refuses it.

Well, I'm going to open a Support Ticket on this. I don't believe this these forum posts count as official bug reports.

Regarding the problem I had with STAR insertion, I had a 1h Skype call with JAR. He found a bug on the FMS on which it gets confused in cases where there are two procedures with same name but for different runways (very common in Brazil).

Dimkzr, you seem to be very "experient" at this CRZ FL bug. Don't you want to maybe take an hour or two to show JAR the details of it? Like in my case, it might enlighten him to find out where the problem is laying.

I believe you are correct, and to clarify i'm not saying that i'm giving correct solutions, i'm like you said provinding an attempt of workaround, while trying to understand why it's not accepting the FL, because if it accepted it after you enter the FP, we would know why that was happening, but if it just doesn't accept the FL at all it's a different story

--------------------

each time i delete a a320 folder and paste a new one it feels like rolling the dices

Like when in the previous version there were posts about SASL... i never got an error about it and i got the plane on the version v3b7

I always had the problem with the NEW CRZ FL until the v3r3 as i said it got fixed for me i can input my CRZ FL before or after it doesn't matter. Now, why it's working properlly for me and not for others? I have no clue...

In the v3r3 i got weird black lines in the plane windows wich you had said that they were fixed in the r1... and i had never seen them before... they got fixed for me now in r4, why? luck?...

don't get me wrong, i love the plane, just pointing the inconsistency

As I said, JAR A320 is not yet 100% stable. I am one of those who try to help to get the optimum out of this model.
After perfect flight I also experienced a malfunction with the MCDU. After changing landing data (RWY, APPR...) during flight, I saw the new route on ND but the route wasn't display any more on MCDU.

Regarding the NEW CRZ FL thing:

Everybody who have this problem – on more or less frequency – please open a Ticket on support. Maybe this way we get his attention on this.

Flying from EGCC (Manchester) to EGLL (Heathrow) on a LISTO departure from 23R I got the departure showing in the completely the wrong direction. The route loaded correctly through X-Life, no problems there, but the takeoff runway heading was behind me and there where a couple of strange waypoints giving odd turns before LISTO. I have airacc 1704 loaded correctly and this doesn't happen in the A330, the takeoff is runway heading and then turning to LISTO. The problem a couple of updates ago, not sure what's going on. I'm wondering if anyone else has had the same problem
In the attached screenshot I'm just about to turn right onto the runway and as you cane see the route is behind the aircraft.

Long story short.

Check if your FP file have named SID and STAR, and replace those with the words "SID" and "STAR".
E.g. change this:
EGCC LIST2Y LISTO L612 HON N859 KIDLI ASTR2B EGKK
into this:
EGCC SID LISTO L612 HON N859 KIDLI STAR EGKK

More detailed answer.

You need to make sure you're using more or less recent AIRAC cycle (the current is 1704).
Open "cycle_info.txt" file found in your YOUR-JAR320-FOLDER/_navdata folder and look at the very first line, it should say something like "AIRAC cycle: XXXX".
If you need to update your AIRAC, I wrote a mini-guide on this subject: http://jardesign.org/forum/viewtopic.ph … 365#p16365

Next, for the flight plans.
JAR is using a very basic flight plan format: FROM SID WAYPONTS STAR TO
When exporting your FP from Simbrief via "Download FMS", pick "JARDesign Airbus" file format and put downloaded .txt into YOUR-JAR320-FOLDER/FlightPlans
Then make sure that this .txt doesn't contain actual SID/STAR names.
Lastly, fire up your sim and put the name of your .txt file (just the name, without ".txt" part) into CO RTE field. Then manually pick your SID and STAR from FMC menu.

Hi !

You do not need to update navigraph.

You should update navigraph if:
  - you are going to fly online and are forced to use the latest navigraph.
  - you want to use a special navigraph cycle.

So if you have the standard navigraph cycle (140x or something like that) go to your favorite flight planner,
select the navigraph cycle you have and that's it.

Sure, if you use an old navigraph cycle in the plane and generate a route with the latest cycle, you might run into
problems.

best regsrds,