Re: ver 2.6 beta 3 WIN/MAC 64 bit
Hi,
How is it possible to "re call" on the lower ECAM display the "cruise display" after having push another mode ?
Thanks a lot in advance
Re: ver 2.6 beta 3 WIN/MAC 64 bit
amischkowitz wrote:
Hi,
How is it possible to "re call" on the lower ECAM display the "cruise display" after having push another mode ?
Thanks a lot in advance
Press the "ALL" button. This will loop through all ECAM pages. Once you see the CRUISE page, press "ALL" again.
Re: ver 2.6 beta 3 WIN/MAC 64 bit
Hi,
Happy new year to everybody
Thanks a lot Killerofwar for your advice 
)
Would it possible in a coming beta version to have full 320 NM range (like on the A330) on the display selector ?
Thanks a lot in advance
Re: ver 2.6 beta 3 WIN/MAC 64 bit
Cannot remove (clear) F-PLN DISCONTINUITY
Loaded flight plan file EPLBLOWG.txt with the following content:
EPLB SID LUKOX T709 KOTEK M984 MIKOV UM984 STO M725 DENUX M984 PUBEG STAR LOWGI selected DEP RWY 07 then and got this situation where clicking the CLR button and selecting LSK3 doen't remove the DISCONTINUITY:
Anything I can do or is it a bug?
SYSTEM: X-Plane 11.00pb9, Win 10 (64bit), Intel Core i7 6700K@4.5 GHz, NVIDIA GeForce GTX 1080 8 GB GDDR5X, 32GB RAM, 1.25 TB SSD, SAMSUNG SUHD 55'' TV@3840x2160px, TrackIR5; PLUGINS/ TOOLS: FS Global Real Weather, SkyMaxxPro v4.1, Real Weather Connector, Gnd Handl. Deluxe, X-Camera, NDP Charts, Navigraph AIRAC; A/C: JARDesign: A320neo & A330
Re: ver 2.6 beta 3 WIN/MAC 64 bit
I guess it's a bug. I reported it last year, concerning the A332. LUKOX is your first waypoint in the flightplan (it's in white). Getting rid of disco's before the first waypoint, is a no no. I'm confident JAR will correct this in the near future if it's in conflict with Airbus-philosophy.
Sierra 10.13.6 - 4.5 GHz i7 - Retina 5120 x 2880 - 16 GB - Radeon Pro 580 8 GB - X-Plane 11 - Ravcore Javelin - 767 FF - 777 FF - 787 Dreamliner - plugin tester Airbus A350 FF - A320Neo JD - A380 PH - A330 PH - alpha/beta tester A330 JD - CRJ200 - beta tester 747-8i SSG - IXEG 733 - EADT 737-800 v5 - 757 v2 FF - ZIBO 737-800 - SSG Embrear 195 - FF A320
Re: ver 2.6 beta 3 WIN/MAC 64 bit
Hi,
Flight GCTS to LEPA :
I noticed during the flight cockpit preparation that the :
-EXT PWR button and the APU TEST and ENG Test fire dont' produce more sound when clicling on the button (cf the beautiful BSS sound)
Thanks a lot for an upcoming correction if possible
Re: ver 2.6 beta 3 WIN/MAC 64 bit
Good day,
I don't like to change subjects but here is something that I have been teling everyone about and now the hard work of the team has paid off so here is a preview the video was done by AdvMichael
Re: ver 2.6 beta 3 WIN/MAC 64 bit
Hi !
Has anyone trying just to fly around with "A/THR" and a speed set?
I can't get it working - A/THR does anything but not hold the speed....
What I did: "Hot start", set "EDDL/EDDL" and started.
After start, Gear up, flaps up, set SPEED KNOB to 250kts, pressed "A/THR". AP1 and AP2 OFF. Thrust to "CL".
So I expected that "A/THR" hold the speed to 250, but the plane sets the engines to IDLE.
Is this a bug or am I missing something ?
Best regards,
Re: ver 2.6 beta 3 WIN/MAC 64 bit
I thought you had to push the throttle to TOGA and then back down to CL detent in order for the A/THR to engage. Just pushing A/THR alone I believe does nothing...UNLESS it's engaged at take off (automatically engaged by the system). If you never disengage it then you're fine...otherwise as I said above to re-enable it. I'm sure someone will correct me if I'm wrong.
Re: ver 2.6 beta 3 WIN/MAC 64 bit
Hi !
gpb500 wrote:
I thought you had to push the throttle to TOGA and then back down to CL detent in order for the A/THR to engage.
yes, I did exactly this. As far as I know it is enough to set the throttle to "CL", set the speed and press the "A/THR" button.
gpb500 wrote:
Just pushing A/THR alone I believe does nothing...UNLESS it's engaged at take off (automatically engaged by the system). If you never disengage it then you're fine...otherwise as I said above to re-enable it. I'm sure someone will correct me if I'm wrong.
Best regards,
Re: ver 2.6 beta 3 WIN/MAC 64 bit
hades.esp72 wrote:
Hi!
Have you installed the sounds Blue Sky Star Ssimulations?
I have that problem with this add, in certain special MCDU pages; but in normal use , I have no problem.thomas_99 wrote:Hi !
Another nice and annoying bug:
1) start xplane & load A320 2.6 B3
2) Press "Hot Start"
3) Click on MCDU "PERF" Page
4) Click "Page up"
Result:
It won't stop clicking :-)
click click click click click.... :-)
best regards,
Can confirm that (also havin BSS sounds installed).
SYSTEM: X-Plane 11.00pb9, Win 10 (64bit), Intel Core i7 6700K@4.5 GHz, NVIDIA GeForce GTX 1080 8 GB GDDR5X, 32GB RAM, 1.25 TB SSD, SAMSUNG SUHD 55'' TV@3840x2160px, TrackIR5; PLUGINS/ TOOLS: FS Global Real Weather, SkyMaxxPro v4.1, Real Weather Connector, Gnd Handl. Deluxe, X-Camera, NDP Charts, Navigraph AIRAC; A/C: JARDesign: A320neo & A330
Re: ver 2.6 beta 3 WIN/MAC 64 bit
AUA1377 wrote:
amischkowitz wrote:At approach descent from more than 6000 feet /min
Can confirm this bug, not only at this STAR. Already had it from time to time. My "workaround" was to use OP DES mode instead, but thats not the solution (and not realistic) - please fix that, thanks!
Can confirm that I always have issues with descent beginning at top of descent. Selecting new lower alt of first STAR waypoint and clicking (managed mode) altitude knob doesn't lead into good descent. acf doesn't descent quick enough. then i always use spoilers full. the result is, that the auto throttle controls engines going to to n1=40-50% and pfd annunciation is THR IDLE (which is not true).
The only solution i know is open descent with full spoilers or better disabling autopilot and auto throttle, pulling throttle lever to idle, leave spoilers full and push nose down. sometimes i can fulfill speed limit of 250kts with alt <= FL100 then. but only sometimes.
SYSTEM: X-Plane 11.00pb9, Win 10 (64bit), Intel Core i7 6700K@4.5 GHz, NVIDIA GeForce GTX 1080 8 GB GDDR5X, 32GB RAM, 1.25 TB SSD, SAMSUNG SUHD 55'' TV@3840x2160px, TrackIR5; PLUGINS/ TOOLS: FS Global Real Weather, SkyMaxxPro v4.1, Real Weather Connector, Gnd Handl. Deluxe, X-Camera, NDP Charts, Navigraph AIRAC; A/C: JARDesign: A320neo & A330
Re: ver 2.6 beta 3 WIN/MAC 64 bit
gpb500 wrote:
I thought you had to push the throttle to TOGA and then back down to CL detent in order for the A/THR to engage. Just pushing A/THR alone I believe does nothing...UNLESS it's engaged at take off (automatically engaged by the system). If you never disengage it then you're fine...otherwise as I said above to re-enable it. I'm sure someone will correct me if I'm wrong.
is that the real airbus behavior that one needs to push throttle lever to maximum and then pull it back to CL?
SYSTEM: X-Plane 11.00pb9, Win 10 (64bit), Intel Core i7 6700K@4.5 GHz, NVIDIA GeForce GTX 1080 8 GB GDDR5X, 32GB RAM, 1.25 TB SSD, SAMSUNG SUHD 55'' TV@3840x2160px, TrackIR5; PLUGINS/ TOOLS: FS Global Real Weather, SkyMaxxPro v4.1, Real Weather Connector, Gnd Handl. Deluxe, X-Camera, NDP Charts, Navigraph AIRAC; A/C: JARDesign: A320neo & A330
89 2016-01-05 23:33:30 (edited by Killerofwar 2016-01-05 23:37:23)
Re: ver 2.6 beta 3 WIN/MAC 64 bit
joomie wrote:
gpb500 wrote:I thought you had to push the throttle to TOGA and then back down to CL detent in order for the A/THR to engage. Just pushing A/THR alone I believe does nothing...UNLESS it's engaged at take off (automatically engaged by the system). If you never disengage it then you're fine...otherwise as I said above to re-enable it. I'm sure someone will correct me if I'm wrong.
is that the real airbus behavior that one needs to push throttle lever to maximum and then pull it back to CL?
No, it's not. Sadly, I don't have any FCOM documents to quote, but the JarDesign A/THR behavior is quite different from the real thing and I'm sure that many A/THR modes the real thing has are not simulated in the JarDesign model. I've been in a real A320-214 simulator last week (along with an AirBerlin pilot/F.O.) and we were able to engage A/THR anytime by pressing the button. However, the throttles should be in CL, otherwise A/THR will show "A/THR LIMITED" and/or will go in some unusal THR MODE and engine power will be limited to the position of the levers (example: you want to have one engine at IDLE and the other operating normally and you want to use A/THR - you would set one lever to idle, the other to FL(EX) and press A/THR) - ECAM will show "A/THR LIMITED" and will only control the power of the engine that is set to CL).
However, if you mess up the flight phases - like taking off without having the MCDU correctly configured - the A/THR might refuse work completly. A/THR will stay forever in "armed" mode - this is indicated by a white box around the A/THR symbol on the PFD or when the A/THR is colored blue.
If I understand the airbus philosophy correctly, pressing the A/THR button on the FCU should bring the autothrottle into armed mode - depending on the position (and movement) of the levers the A/THR will than engange in the desired mode (like THR CLB or THR LVR).
This document might give some more information about all the different "flight modes": http://www.airbusdriver.net/EFIS3.pdf
Re: ver 2.6 beta 3 WIN/MAC 64 bit
BSS is not working for me at all. Don't even show up in plugin menu. They work fine on v2.5
Also, AIRFMC is corrupted badly with text from previous pages /views showing up on it (not on the a/c MCDU).
MCDU still quirky with SID and STAR fixes (have to go back to FPLN screen and pick the SID/STAR again)
Also, the ATHR doesn't work at all. After take-off any position over than FLEX/CLB seems to be manual (doesn't show THR/CLB on ND). So I am having to completely control the throttle from then on, especially on descent where overspeed ALWAYS happens.
Many thanks,
Hans
Post's attachments
bbox_log.txt 16.98 kb, 297 downloads since 2016-01-05
Log.txt 63.37 kb, 434 downloads since 2016-01-05
iMac5K 27” (2015), i7 4GHz, OSX 10.14.6, 32GB, AMD M395X 4096MB, Saitek X52, TPM, Radio, Switch & Multi, TM MFD, XP11.35r1, FFA320v0.11.2-2305, ToLiSs A319 v1.3.3, JDA320 v3.4r1, JDA330 v3.2r1, XL v4_250719, FM v2.6r2, GndHdg v.4.010719, Air Plugin v4.8.3, FWL 2.7.19, 3jFPS-wizard, PI v2.73.06, NOAA v2.4.4, XSPs v2.75, XCL v1.37, BPB v0.47, SAM 1.1.0
Re: ver 2.6 beta 3 WIN/MAC 64 bit
laohu314 wrote:
BSS is not working for me at all. Don't even show up in plugin menu. They work fine on v2.5
Also, AIRFMC is corrupted badly with text from previous pages /views showing up on it (not on the a/c MCDU).
MCDU still quirky with SID and STAR fixes (have to go back to FPLN screen and pick the SID/STAR again)
Also, the ATHR doesn't work at all. After take-off any position over than FLEX/CLB seems to be manual (doesn't show THR/CLB on ND). So I am having to completely control the throttle from then on, especially on descent where overspeed ALWAYS happens.Many thanks,
Hans
BSS is working fine for me. You have some SASL errors in the log, like "Can't find sound /sounds/sound3D/jd_apu_l.wav". Are you sure that you have BSS correctly installed?
I have no idea what you mean with the MCDU issues with SID/STAR, could you describe exactly what you enter into the MCDU?
And about the A/THR. At takeoff the plane always shows some "MANUAL" mode to me (I either go up to FLEX or TOGA, depending on weather and weight conditions). At thrust reduction altitude I set the levers to CL(IMB) and A/THR operates normally.
Re: ver 2.6 beta 3 WIN/MAC 64 bit
Thanks Killerofwar!
I did have the sound folders in the wrong place, my bad.
About the MCDU, when I enter a SID (e.g. for this route KBOS PATSS4.PATSS PATSS NELIE NELIE.FLOSI3 KILMA EWR), sometimes the FIX I need isn't shown, so I go back to f-pln, click on the SID again and then the fixes would show up on the right.
I'll make a more precise observation next time and report. e.g. KBOS PATSS4.PATSS PATSS NELIE NELIE.FLOSI3 KILMA EWR
A/THR issue: I tried all this, there never is CL mode showing on the ND at thrust reduction when I pull back, it flickers for a millisecond but any throttle (Saitek X52 Pro) position I try, I can never capture it. FLEX and TOGA, no problem, but below that, nothing and no matter how often go back to FLEX, no joy.
Best wishes,
Hans
iMac5K 27” (2015), i7 4GHz, OSX 10.14.6, 32GB, AMD M395X 4096MB, Saitek X52, TPM, Radio, Switch & Multi, TM MFD, XP11.35r1, FFA320v0.11.2-2305, ToLiSs A319 v1.3.3, JDA320 v3.4r1, JDA330 v3.2r1, XL v4_250719, FM v2.6r2, GndHdg v.4.010719, Air Plugin v4.8.3, FWL 2.7.19, 3jFPS-wizard, PI v2.73.06, NOAA v2.4.4, XSPs v2.75, XCL v1.37, BPB v0.47, SAM 1.1.0
Re: ver 2.6 beta 3 WIN/MAC 64 bit
As said many times before. Jar's Airbuses read the metar.rwx file which is in the x-plane root folder. But the external wheater engines don't write into that file, so the jar busses can't display any information. To have the metar display working use x-plane real weather.
94 2016-01-06 09:34:40 (edited by thomas_99 2016-01-06 11:31:23)
Re: ver 2.6 beta 3 WIN/MAC 64 bit
Hi !
I got it. I'm not sure if this is a bug, but I think so.....
Maybe JAR can check if it's a bug:
1) Do exactly as I'm described that.
2) You have to set the Altitude in the FCU to something higher than you are, regardless to the number.
If you are at 5000 feet, set it to 8000. Don't need to push the "AP1" button, don't need to push or pull
the "Altitude Knob" it's enough just to set the number.
This will engage the "A/THR" (you will hear the engines working again), and from this point, it's working,
regardless of your own altitude.
thomas_99 wrote:
Hi !
Has anyone trying just to fly around with "A/THR" and a speed set?
I can't get it working - A/THR does anything but not hold the speed....
What I did: "Hot start", set "EDDL/EDDL" and started.
After start, Gear up, flaps up, set SPEED KNOB to 250kts, pressed "A/THR". AP1 and AP2 OFF. Thrust to "CL".
So I expected that "A/THR" hold the speed to 250, but the plane sets the engines to IDLE.
Is this a bug or am I missing something ?
Best regards,
- J.A.Romanov
- Admin
- Offline
Re: ver 2.6 beta 3 WIN/MAC 64 bit
thomas_99 wrote:
Hi !
So, I will provide you a step-for-step instruction:
0) Win10x64, XP10.42 release version.
1) I have installed the A320 2.6 b3 from the archive, no changes.
2) X-Plane 10\Resources\GNS430\navdata
-> updated cycle to 1511, using format xplane_gns430_777...prof_native
-> deleted the old one, copied the new one.remark: It does not only depend on 1511 version, older versions show same problem.
3) Created a flight plan "a320neo_2.6b3/FlightPlans/EDDFEDNY.txt"
containing:
EDDF SID ANEKI Y163 NEKLO Y171 INKAM T725 LAMGO T721 SUL T732 GARMO STAR EDNY
4) Start xplane, load A320neo_2.6b35) press hot start button.
wait until all comes up.
6) INIT PAGE: EDDFEDNY -> CO RTE
ALIGN IRS
Flt Nr: LH555
Cost Index: 30
Crz Flight: 250
-> next page
ZFW -> Click
Block -> Click7) F-Plan PAGE:
EDDF -> Click
Departure -> Click
07C -> Click
Here is first problem: ANEK1D is listed twice !!
Select first one: ANEK1D -> Click
No Trans -> Click
Tmp F-Plan -> Click, Insert -> Click
SID looks good !! :-)
EDNY -> Click
ILS06 -> Click
GARM1P -> Click
MOKOP -> Click
No Trans -> Click
tmp F-Plan -> Click
Insert -> Click
8) Ok, we have that nice picture :-)J.A.Romanov wrote:Hmm.. STAR?
Please privide
- STAR
- Runway
- ApproachI will check!
Ok, I just try this STAR with beta 4. Seems like Ok now.
Please read a FAQ before you post a bug http://support.jardesign.org
- J.A.Romanov
- Admin
- Offline
Re: ver 2.6 beta 3 WIN/MAC 64 bit
thomas_99 wrote:
Hi Mr. Romanov,
I'm relatively sure that bug#1 (double ANEK1D) are the SID constrains at EDDF (and other airports, too).
SID,ANEK1D,07C,4
SID,ANEK1D,ALL,5Start at runway 07C leads to the constraints "ANEK1D" because of "07C" matches "07C"
Start at runway 07C leads to the constraints "ANEK1D" because of "ALL" matches "07C"And now we have two "ANEK1D" displayed in the FMC. And nobody knows which one is which.
I have no idea how this is solved in "real live", but I think there must be some "priority handling"
which decides Runway 07C -> "ANEK1D/07C is shown because of "07C", ANEK1D/ALL is shown
because of "ALL" matches "07C" but not shown because of "ANEKI1D/07C" mached before, so priority
says "NOT SHOWN" -> do not display.best regards,
fixed for beta 4
thanks for issue!
Please read a FAQ before you post a bug http://support.jardesign.org
Re: ver 2.6 beta 3 WIN/MAC 64 bit
Hi !
This looks VERY VERY VERY GOOD !!!
Thank you very much !!
J.A.Romanov wrote:
Ok, I just try this STAR with beta 4. Seems like Ok now.
best regards,
- J.A.Romanov
- Admin
- Offline
Re: ver 2.6 beta 3 WIN/MAC 64 bit
AUA1377 wrote:
Hi JAR,
I did/tried a flight from ULMM to LOWW and found some very annoying bugs, please fix them...
Flight: ULMM-LOWW
Route: PELOR DCT KELEK DCT RENVI M857 TLL L729 LUTAL P870 BOKSU M985 EVINA N744 TUSIN DCT MIKOV
AIRAC: 1512 Navigraph
Windows 8.1 + XP 10.42ULMM
DEP RWY: 13
DEP SID: PELOR1
First bug, wrong route drawing, why is it not out rwy heading and direct to PELOR after the turn?
From Jeppesen chart ULMM (http://www.uvairlines.com/admin/resourc … s/ULMM.pdf):
Second bug, after taking off I got a few terrain warnings, I also had that with beta 1 and 2 at other airports, seems to be a main problem. (It happens very often after takeoff - but there should be no terrain warning)
Then, the aircraft followed the (incorrect drawn) route path.
But then, and this is the third bug, I inserted a direct to RENVI. The aircraft started turning to the left without any reason. It turned, turned, turned and stopped turning and heading a completely wrong direction. There was no chance to get back on the route, not by inserting further directs, not by pulling and again pressing the heading knob, not by disengaging and reactivating the autopilot - no chance! I had to cancel the flight... :-(
Thanks for fixing these bugs!
Merry Christmas!
thanks for issue!
talk about First this time -
We have NavData:
SID,PELOR1,13,2
CF,D131I,68.694167,32.912778,0,KIK,120.2,89.9,131.0,6.0,2,1890,0,0,0,0,0,1 (fly to FIX with hdg=131)
CI,2, ,0.0,287.0,0,0,0,0,0,0,0,0 (Course to Intercept Next Leg, Magnetic course=287.0, no other Data)
CF,PELOR,68.616667,31.780000,0,KIK,135.5,78.3,222.0,16.0,4,15000,8000,0,0,0,0,0 (to PELOR, but need turn from prev leg course=278)
So.. leg 2 follow us to hdg 287. Sure I am not see any hdg 287 in real chart. As result FMGS wrong draw leg 2. May be this is NavData problem, may be this is my brain issue, but.. have not idea how to fix this sorry.
Issue 2: "Terrain, Terrain" may happen cause sometimes terrain datas have fracture, like a crack in surface. If this happen, RA of aircraft may be too big in this point, but next point RA will be normal (small). So aircraft think what out RA decrease fast (from BIG to SMALL) and generate alert. I will think how to avoid this in future.
Issue 3: For this issue i need (if it possible, please)
- copy of tmpfpln.txt from flightplan folder just after this happen
- bbox_log.txt from a320 folder just after this happen
- log.txt file just after this happen
Please read a FAQ before you post a bug http://support.jardesign.org
Re: ver 2.6 beta 3 WIN/MAC 64 bit
Hi !
@AUA1377:
during takeoff, did you get the "100 Knots", "V1, Rotate" callouts ??
Usually, I got this "Terrain, Terrain" warnings during Takeoff when I'm not in "Takeoff" mode.
I like to link you to another posting: http://jardesign.org/forum/viewtopic.php?id=1231
-> - IF the markers in the PFD are not displayed, no voices.
Today I would like to add: "Terrain, Terrain" warnings.
Maybe you can check if these "Terrain" warnings appear when you make a takeoff without "RWY NAV".
J.A.Romanov wrote:
AUA1377 wrote:Second bug, after taking off I got a few terrain warnings, I also had that with beta 1 and 2 at other airports, seems to be a main problem. (It happens very often after takeoff - but there should be no terrain warning)
thanks for issue!
talk about First this time -
Issue 2: "Terrain, Terrain" may happen cause sometimes terrain datas have fracture, like a crack in surface. If this happen, RA of aircraft may be too big in this point, but next point RA will be normal (small). So aircraft think what out RA decrease fast (from BIG to SMALL) and generate alert. I will think how to avoid this in future.
Re: ver 2.6 beta 3 WIN/MAC 64 bit
Good evening,
Would it be possible in upcoming beta version to have :
-possibility to enter Speed constraints in the MCDU
-to have a full 320 NM range on the ND display
-before engine start, to have orange cross on the upper ECAM display (like on the A330 version)
-possibilty to have real Constraints display on the ND (with speed limits and altitude limits
Thanks a lot for all your beautiful work