You are not logged in. Please login or register.
JARDesign Group Board → Download, Updates → JD320 Airliner ver 3.2 r1,r2 WIN/MAC 64 bit (X-Plane 11)
Has the bug where the aircraft stops climbing after reaching 10.000ft to increase the speed to cruise speed been fixed? I don't see anyone talking about that. The plane should continue climbing and increasing speed , not stop climbing.
Has the bug where the aircraft stops climbing after reaching 10.000ft to increase the speed to cruise speed been fixed? I don't see anyone talking about that. The plane should continue climbing and increasing speed , not stop climbing.
I'm not sure you're right.
While plane shouldn't completely level-off after FL100, it must reduce v/speed to quickly accelerate past 250kts restriction to actual climb speed. It's simply a matter of efficiency.
Mystical_DC3 wrote:Has the bug where the aircraft stops climbing after reaching 10.000ft to increase the speed to cruise speed been fixed? I don't see anyone talking about that. The plane should continue climbing and increasing speed , not stop climbing.
I'm not sure you're right.
While plane shouldn't completely level-off after FL100, it must reduce v/speed to quickly accelerate past 250kts restriction to actual climb speed. It's simply a matter of efficiency.
??? That's what i said, it shouldn't level off, it should reduce vspeed but continue climbing. And it doesn't, it levels off at 10.300ft for 10 or 15 seconds and only after it reaches cruise speed it starts climbing again. That's wrong and people already reported about that before.
Hi i drop my cpu overclocks all down and i get JDa320 activation window pop up and error for activation ? does cpu clock change computer identity? i try reinstall aircraft and try again. I cant activate this product. Filghtfacror A350 ask activation also but this activation works. Ty for JAR problem solved.
I am still encountering the issue that ILS approaches do not include the IF. For example, I was flying the following route from KIAD to KBOS:
JCOBY3 SWANN DCT BROSS J42 RBV J222 JFK ORW6
The terminal ILS approach to RW15R at KBOS should be: SWIGG (IF) WOBUR MALDY but the FMC only generates WOBUR MALDY after the STAR. So I had to insert SWIGG manually. That maybe due to the fact that NORWICH 6 (ORW6) is not the ideal STAR and GARDNER 4 (GDM4) would be better but still, SWIGG should be inserted in this case as well.
Another small issue that has been around for a while is that the runway pictogram on the ND always is at an angle to the final approach direction. Not a real issue but it looks odd and unreal.
Check out http://www.flytampa.org/forum/viewtopic.php?p=29832.
Your final issue looks like it might be caused by an offset localiser. i think that one of the Nice runways, 04R i think it is, has a similar issue. Try R15L instead. as that might be better aligned with the localiser.
Anyone else getting this with 3.2R1?
[SASL INFO] "mcdu_fpln" get(alt_crzft)=36000
[SASL INFO] "mcdu_fpln" toc_i=9
[SASL INFO] "mcdu_fpln" tod_i=10
[SASL INFO] "mcdu_fpln" --> Set active WPT to VA1527 for DetectActualWaypoint reason
[SASL INFO] "mcdu_fpln" --> Switch active WPT from 27R to VA1527 by internal FMS
[SASL INFO] "bbox"
[SASL INFO] "bbox" >>> zulu 15:9:17
[SASL INFO] "bbox" baro alt=712 / rad alt=0
[SASL INFO] "bbox" air spd=4 / gnd spd=0 / mach=0
[SASL INFO] "bbox" GW=61739 / FOB=5739 / CG=25
[SASL INFO] "bbox" new fpln full = 1 KATL (APT) >>> 2 27R (DEP_RWY) >>> 3 VA1527 (CA) >>> 4 SLAWW (WPT) >>> 5 WESEK (WPT) >>> 6 CUTTN (WPT) >>> 7 HANKO (WPT) >>> 8 DISC (DISC) >>> 9 (T/C) (pseudo) >>> 10 (T/D) (pseudo) >>> 11 (CROSS) (pseudo) >>> 12 (RED250) (pseudo) >>> 13 (LIM) (pseudo) >>> 14 (DECEL) (pseudo) >>> 15 (SPD220) (pseudo) >>> 16 KSLC (APT) >>> DIST=1385.62032
[SASL INFO] "mcdu_fpln" --> Switch active WPT from VA1527 to SLAWW by internal FMS
[SASL INFO] "bbox"
[SASL INFO] "bbox" >>> zulu 15:9:18
[SASL INFO] "bbox" baro alt=712 / rad alt=0
[SASL INFO] "bbox" air spd=4 / gnd spd=0 / mach=0
[SASL INFO] "bbox" GW=61739 / FOB=5739 / CG=25
[SASL INFO] "bbox" active wpt = 4 SLAWW
[SASL INFO] "mcdu_fpln" --> Switch active WPT from VA1527 to SLAWW by internal FMS
[SASL INFO] "mcdu_fpln" get(alt_crzft)=36000
[SASL INFO] "mcdu_fpln" toc_i=9
[SASL INFO] "mcdu_fpln" tod_i=10
[SASL INFO] "mcdu_fpln" --> Set active WPT to SLAWW for DetectActualWaypoint reason
[SASL INFO] "bbox"
[SASL INFO] "bbox" >>> zulu 15:10:13
[SASL INFO] "bbox" baro alt=712 / rad alt=0
[SASL INFO] "bbox" air spd=4 / gnd spd=0 / mach=0
[SASL INFO] "bbox" GW=61733 / FOB=5733 / CG=25
[SASL INFO] "bbox" new fpln full = 1 KATL (APT) >>> 2 27R (DEP_RWY) >>> 3 VA1527 (CA) >>> 4 SLAWW (WPT) >>> 5 WESEK (WPT) >>> 6 CUTTN (WPT) >>> 7 HANKO (WPT) >>> 8 DISC (DISC) >>> 9 (T/C) (pseudo) >>> 10 (T/D) (pseudo) >>> 11 (CROSS) (pseudo) >>> 12 (SPD220) (pseudo) >>> 13 HELPR (WPT) >>> 14 GOSHU (WPT) >>> 15 SPANE (WPT) >>> 16 LEEHY (WPT) >>> 17 BLUPE (WPT) >>> 18 KAMMP (WPT) >>> 19 PLAGE (WPT) >>> 20 VM3410 (VM/VA) >>> 21 (RED250) (pseudo) >>> 22 PEDLE (WPT) >>> 23 ZEPOG (WPT) >>> 24 KERNN (WPT) >>> 25 WEEEL (WPT) >>> 26 FORXS (WPT) >>> 27 RW35 (ARR_RWY) >>> 28 KSLC (APT) >>> DIST=1409.19669
[SASL INFO] "mcdu_fpln" get(alt_crzft)=36000
[SASL ERROR] Error updating avionics: not enough memory
[SASL INFO] "mcdu_fpln" get(alt_crzft)=36000
[SASL ERROR] Error updating avionics: not enough memory
[SASL INFO] "mcdu_fpln" get(alt_crzft)=36000
[SASL ERROR] Error updating avionics: not enough memory
[SASL INFO] "mcdu_fpln" get(alt_crzft)=36000Hi !
Anyone else getting this with 3.2R1?
[SASL INFO] "mcdu_fpln" get(alt_crzft)=36000 [SASL ERROR] Error updating avionics: not enough memory [SASL INFO] "mcdu_fpln" get(alt_crzft)=36000 [SASL ERROR] Error updating avionics: not enough memory [SASL INFO] "mcdu_fpln" get(alt_crzft)=36000 [SASL ERROR] Error updating avionics: not enough memory [SASL INFO] "mcdu_fpln" get(alt_crzft)=36000
You do not have enough memory. You now can:
a) enlarge/switch on your swap space (cheapest way)
b) buy more memory (more expensive)
best regards,
dimkzr wrote:Mystical_DC3 wrote:Has the bug where the aircraft stops climbing after reaching 10.000ft to increase the speed to cruise speed been fixed? I don't see anyone talking about that. The plane should continue climbing and increasing speed , not stop climbing.
I'm not sure you're right.
While plane shouldn't completely level-off after FL100, it must reduce v/speed to quickly accelerate past 250kts restriction to actual climb speed. It's simply a matter of efficiency.??? That's what i said, it shouldn't level off, it should reduce vspeed but continue climbing. And it doesn't, it levels off at 10.300ft for 10 or 15 seconds and only after it reaches cruise speed it starts climbing again. That's wrong and people already reported about that before.
What happens is that at FL100 vspeed is reduced to about 500-800 fpm until climb speed is reached and then increases again to 2500-3500 fpm. This is exactly what happens IRL. I have been on A320's a few times recently and saw exactly that. Sitting in the cabin the lowering of vspeed is hardly noticeable but I was following the flights on Flightradar24 and the change in fpm was exactly what I described.
After purchasing A320 on mycommerce i have no activation code where can i find it.
After purchasing A320 on mycommerce i have no activation code where can i find it.
Hi,
I think you should receive by mail soon...
Regards
I really would love to hear about future of this product. Every patch seems to be improving something but something else goes down. I do not know if they have done some to FADEC but in this patch it once again seem to be quite accurate (not there yet). Also would love Jar to tell do they have plan to improve features of this aircraft. Especially now we have announcement of Flight Factor A320 and I think it is quite sad truth that if this product do not improve then FFA320 will take over.
I did first test flight EDDF - EHAM with this update and latest X-Plane 11 (11.05RC1) and everything wen't as usual. Didn't see too much improvements (well I've never had any crash so I don't know about that). Aircraft is still very unstable on approach (I don't think it should) But it is great to see that product is not forgotten and instead developer just had other things going on. I am looking what future of this aircraft will be and I do hope that you can make it to be on level that buying FFA320 is not needed!
EDIT: I got huge bug on second flight.. I activated DESC and aircraft just put nose down like 30 degrees and started to descent with about 7k fpm?
@Bruns:
You are using 11.05RC1!? This aircraft is not compatible with your version:
- be sure, that you use X-Plane 11.00-11.01 (see: http://jardesign.org/forum/viewtopic.ph … 063#p18063)
@Bruns:
You are using 11.05RC1!? This aircraft is not compatible with your version:
- be sure, that you use X-Plane 11.00-11.01 (see: http://jardesign.org/forum/viewtopic.ph … 063#p18063)
Oh yeah looks so! I think I have to rollback to previous version. Maybe next time I should read a little bit more careful 
@Bruns:
You are using 11.05RC1!? This aircraft is not compatible with your version:
- be sure, that you use X-Plane 11.00-11.01 (see: http://jardesign.org/forum/viewtopic.ph … 063#p18063)
It's a precaution rather than requirement.
At the time JAR wrote that, 11.01 was the latest stable version.
I'm not having any (new) issues with J320 and 11.02beta.
And 11.05rc1 doesn't contain anything special, just a bunch of new airports.
I confirm using xp11.05rc1 and jd320v3.2r1 without any pb.
Aircraft very stable on approach and ils landing...
I confirm using xp11.05rc1 and jd320v3.2r1 without any pb.
Aircraft very stable on approach and ils landing...
Are you flying under real weather conditions? If yes how strong was the head (or side) wind during approach? What was the target airport?
enrigolan79 wrote:I confirm using xp11.05rc1 and jd320v3.2r1 without any pb.
Aircraft very stable on approach and ils landing...Are you flying under real weather conditions? If yes how strong was the head (or side) wind during approach? What was the target airport?
yes real weather with smp4.5
last airport LFOT ils rwy20
yesterday afternoon 220°/12kt
Hi !
There is another bug in the checklist. The "After Start" checklist is broken at the end.
It ends with "if you are ready to go below the line, click it again", but we are already in the air :-)
Best regards,
Hi !
There is another bug in the checklist. The "After Start" checklist is broken at the end.
It ends with "if you are ready to go below the line, click it again", but we are already in the air :-)
Best regards,
I'm not following... You should check below the line items before taxi.
Hi !
thomas_99 wrote:Hi !
There is another bug in the checklist. The "After Start" checklist is broken at the end.
It ends with "if you are ready to go below the line, click it again", but we are already in the air :-)
Best regards,
I'm not following... You should check below the line items before taxi.
Oh, sorry, not "After Start", it's "After Takeoff" Checklist. It's where checked that "gear up" and so on,
and this ends with "if you are ready to go below the line, click it again".
best regards,
Hi !
dimkzr wrote:thomas_99 wrote:Hi !
There is another bug in the checklist. The "After Start" checklist is broken at the end.
It ends with "if you are ready to go below the line, click it again", but we are already in the air :-)
Best regards,
I'm not following... You should check below the line items before taxi.
Oh, sorry, not "After Start", it's "After Takeoff" Checklist. It's where checked that "gear up" and so on,
and this ends with "if you are ready to go below the line, click it again".best regards,
This is where you pass the transition altitude, which you obviously can't do with the whole checklist. Thus, the last item is the altimeter setting, which must be changed upon passing the transition altitude.
Hi !
dimkzr wrote:thomas_99 wrote:Hi !
There is another bug in the checklist. The "After Start" checklist is broken at the end.
It ends with "if you are ready to go below the line, click it again", but we are already in the air :-)
Best regards,
I'm not following... You should check below the line items before taxi.
Oh, sorry, not "After Start", it's "After Takeoff" Checklist. It's where checked that "gear up" and so on,
and this ends with "if you are ready to go below the line, click it again".best regards,
This checklist also has one "below the line" item: to check for the Barometer to be set to STD after reaching Transition Altitude.
Test flight ULLI-EETN, A320 v.3.2R1, XL v. 2.6R1: No serious occurrences. Aircraft unstable during decent at moderate head winds.
XL and ATC working well. I experienced two incidents during take-off and landing making simulation much more exciting:
Comments welcome.....
Always throw away from an autopilot. Catastrophe
JARDesign Group Board → Download, Updates → JD320 Airliner ver 3.2 r1,r2 WIN/MAC 64 bit (X-Plane 11)
Powered by PunBB, supported by Informer Technologies, Inc.