You are not logged in. Please login or register.
JARDesign Group Board → Download, Updates → a320neo JARDesign ver 2.6 r2 WIN/MAC 64 bit
At the end of my post you'll find a link with the fixed texture. Click on it, then click over the image with right mouse button and download it. Put the file in the object folder of the A320 NEO and overwrite the overhead.lit file
At the end of my post you'll find a link with the fixed texture. Click on it, then click over the image with right mouse button and download it. Put the file in the object folder of the A320 NEO and overwrite the overhead.lit file
Thank you so much Mad Mat!
Gracie mille!
You are the MAN!
I've found a situation, where a F-PLAN discontinuity cannot be cleared.
The route is EDDV SID WRB UN850 NATOR N850 TITIX UN850 TRA M858 SRN UM858 VOG STAR LIMJ
Initial departure runway was 9L and SID was WRB2Y, but ATC told be to change to runway 27C. Then it was not possible to clear the occured F-PLAN discontinuity .Please check the video: https://youtu.be/1jGT4JV3qbo
As there are some users at the org forums reporting similar issues, I'd like to know if this issue is adressed and possibly solved for the next update?
On arrival too. If ATC send you to a fix (directo to) that is not in your flightplan, you get a discontinuity impossible to clear.
Stefan wrote:I've found a situation, where a F-PLAN discontinuity cannot be cleared.
The route is EDDV SID WRB UN850 NATOR N850 TITIX UN850 TRA M858 SRN UM858 VOG STAR LIMJ
Initial departure runway was 9L and SID was WRB2Y, but ATC told be to change to runway 27C. Then it was not possible to clear the occured F-PLAN discontinuity .Please check the video: https://youtu.be/1jGT4JV3qbo
As there are some users at the org forums reporting similar issues, I'd like to know if this issue is adressed and possibly solved for the next update?
In my experience, when the F-PLAN is entered with correct SID and STAR there is no problem clearing discontinuities. I would always advise to ignore ATC when you have studied the charts and know a particular SID and/or STAR is correct. Also, in the latest version you can request the runway you believe is right.
Hi.
Is it possible to have the FMGS "ovefly" key working ?
According the THALES Pilot Guide (page 12 of the MCDU description), when you press the OVFY key, it puts a triangle in the scratch pad, so you have to press the LSK adjacent to the waypoint to be over-flown, and vice versa, if you click on a waypoint still on ovfy state, it disable the ovy for this point.
Thks ! 
The overfly function would be really useful in the A320 as I find managing RNAV Approaches after vectors is near impossible due to the fact that within a certain distance the waypoints skip to the next causing a strange intercept heading
Hi, a small problem, when flying through cloud I see flashing white lines along the straight bottom edges of the front panel gauges. I'm using the default X-Plane weather generated from the net. It also happens when the scenery below is landscape, although it doesn't show so much. It looks as if there are gaps in the panel.
It only happens when viewing the front panel straight on, if you turn slightly to the right the lines go into small dots, which aren't so obvious. I can't remember seeing before 2.6r2, although I may be mistaken.
Hi Eugeny, is it possible to manually insert MISSED APPROACH points into the MCDU? Last time I tried to but unsuccessfully as all altitudes and constraints got broken. Navdata are often missing missed approach points, either with Aerosoft or Navigraph, so for now the only solution I've found is to hit TOGA and manually follow the published procedures.
Thanks!
Cris
Hello,
I will place my problem here hoping that many people will see and maybe understand it.
Maybe 15 to 20 minutes after take off, nearing cruise altitude, sometimes it occurs further during the flight, the 2 big screens (horizon + nav/gps screen) just turn black. It's as simple as that, it turns black. Every other function in the plane work perfectly. Along with those screens turning black, on the left of the screen, the menus controlling fuel, tow, cat etc also disappears. As if part the plane and the software/ mechanics making the plane work just shut down.
It is quite annoying ... if anybody else experienced that, I'll be glad to hear news from it.
I posted in Xplane.org forum and a member said it could be SASL soft crash.
Kind regards,
Tiakyt
Stefan wrote:Stefan wrote:I've found a situation, where a F-PLAN discontinuity cannot be cleared.
The route is EDDV SID WRB UN850 NATOR N850 TITIX UN850 TRA M858 SRN UM858 VOG STAR LIMJ
Initial departure runway was 9L and SID was WRB2Y, but ATC told be to change to runway 27C. Then it was not possible to clear the occured F-PLAN discontinuity .Please check the video: https://youtu.be/1jGT4JV3qbo
As there are some users at the org forums reporting similar issues, I'd like to know if this issue is adressed and possibly solved for the next update?
In my experience, when the F-PLAN is entered with correct SID and STAR there is no problem clearing discontinuities. I would always advise to ignore ATC when you have studied the charts and know a particular SID and/or STAR is correct. Also, in the latest version you can request the runway you believe is right.
The point is not about getting a workaround for this issue by choosing another SID. Actually this is what I did then. It is all about the occasional impossibility to clear the discontinuity. This should not be.
laohu314 wrote:Stefan wrote:As there are some users at the org forums reporting similar issues, I'd like to know if this issue is adressed and possibly solved for the next update?
In my experience, when the F-PLAN is entered with correct SID and STAR there is no problem clearing discontinuities. I would always advise to ignore ATC when you have studied the charts and know a particular SID and/or STAR is correct. Also, in the latest version you can request the runway you believe is right.
The point is not about getting a workaround for this issue by choosing another SID. Actually this is what I did then. It is all about the occasional impossibility to clear the discontinuity. This should not be.
Using 'direct to' and celar discontinuity
Hello JAR team,
Do you plan on having a sale on the A320neo soon?
I'd love to use this Airbus!
JAR не возникало желание профили крыла сделать не линейными, с более правдоподобными характеристиками? Или он с такими профилями посыпется весь как тот робот от глотка чистой воды? Я могу попробовать, в тем более у меня есть некий
опыт в этом, уверен что смогу сделать его управляемым как "уточка! " будет приятен и предсказуем, будут и срывы потока
и ламинарный угол и в общем твой ответ нужен...
full flight-envelope protection не отвечай, а то я уже твои мысли читаю
Hello,
I will place my problem here hoping that many people will see and maybe understand it.
Maybe 15 to 20 minutes after take off, nearing cruise altitude, sometimes it occurs further during the flight, the 2 big screens (horizon + nav/gps screen) just turn black. It's as simple as that, it turns black. Every other function in the plane work perfectly. Along with those screens turning black, on the left of the screen, the menus controlling fuel, tow, cat etc also disappears. As if part the plane and the software/ mechanics making the plane work just shut down.
It is quite annoying ... if anybody else experienced that, I'll be glad to hear news from it.
I posted in Xplane.org forum and a member said it could be SASL soft crash.
Kind regards,
Tiakyt
Yes, since the last update I cannot use this plane. It's too unreliable. FMC FPLN screen goes blank, PERF page shows for a nano-second then goes blank, FPLN discontinuity won't remove. I'm afraid the IXEG 737 has got my attention now - because that one works flawlessly.
Good day,
So, everyone is having issues and we want to fix the issues but how to fix the issues without Log.txt and bbox.txt these will help to tract the issues and fix the Airbus you like so much.
Oh and I know posting at forum is good but here is better... so JAR can keep track of bugs and work to debug I have seen a spike in the frame rates up to 200/ 500 <+-> when trying to land so we need to stare aggressively work on this issue by posting log.txt and bbox.txt to solve issue.
Happy Flying,
Brian
[SASL ERROR] Error updating avionics: [string "D:\X-Plane 10\Aircraft\_Mis aviones\JARDesign..."]:0: attempt to perform arithmetic on a nil value
LELC - LEAS
bbox_log.txt 16.31 kb, 248 downloads since 2016-06-12
Log.txt 277.74 kb, 264 downloads since 2016-06-12
HI,
when fmc will follow the route? i mean that on display if you don't use the arrow key you don't see the current point of route.
Have had 2 trouble-free flights with the new update Very very pleased about that.
I do have a slight issue (that I can live with) with the nose wheel and its strange behaviour at low taxi speed. The nose wheel seems to brake (not break) the plane at very low speed when a left or right input is applied. At slightly higher speed, when full left or right rudder, the nose wheel does a complete 360' and at higher taxi speeds the nose wheel is fine.
Anybody else seen this problem?
I would imagine all aircraft in the real world slow down when turning due to the weight of the aircraft. you have to have sufficient energy to keep the turn. I'm sure if you watch the speed during a turn at a slightly higher speed (for example 30 knots groundspeed) the speed will drop but not enough to stop the aircraft completely.
A problem with Pitch Trim.
I´m using X-Plane 10.50b2 and A320neo 2.6 r2.
After take off the pitch trim is changing automatically from example DN0.1 step by step to UP11.0
So the aircraft can not be flown.
Any idea?
WoDi
Edit: A330 works fine.
it is the same for me
It is same for me
I would like to say at first - The A320neo is great. It's an development achievement on a high level - Appreciated!
I actually never thought that I would ask any questions here at this forum. But I am flying this domestic flight all the time (EKAH/EKCH) in Denmark. The problem is that EKAH does not have any SID, so it automatically add "F-Plan discontinuity" on the FMC. I know that you have to punch the CLR button first and then pick the "F-Plan discontinuity" you want to delete. But nothing happens. I have tried everything - Tried to add more waypoints to close the gap, but nothing helps. I simply can't get rid off the "F-Plan discontinuity".
Please help!
/Michael
Did you put at least a runway for landing?
JARDesign Group Board → Download, Updates → a320neo JARDesign ver 2.6 r2 WIN/MAC 64 bit
Powered by PunBB, supported by Informer Technologies, Inc.