You are not logged in. Please login or register.
JARDesign Group Board → Beta-versions (Download & Discussions) → ver 2.6 beta 4 WIN/MAC 64 bit
good day,
Yes, MD-80 has the same behavior as in the videos so, this is not a bug like everyone is trying to make out to be I watch just to see and compare the issue also the 767 by FF so everyone can put the issue to bed.
Brian
Hi !
Well, the picture is only to show that the plane does not go to HAM after GoAround.
The question is: should it go ?
If yes, that's a bug, and I will do that again and give you the logfiles.
If no, that's ok.
As I do not exactly know the real behaviour when doing a GoAround, I'm just asking if anyone
knows what the plane should do :-)
thomas_99 wrote:Hi !
Possible GoAround bug ?? Maybe someone can comment....
Short before ILS landing, I set new height (5000 ft), which was confirmed with "Go Around Height Set".
30 feet before touchdown I set TOGA-Power, which was confirmed with "Go Around".
The plane set ToGa Power and start to climb. AutoPilot 1+2 was on, plane goes to to HDS.
After HDS, I expect the plane to turn to HAM automatically, but the plane goes straight ahead.
Should the plane turn to HAM ?? I think yes, but I'm not sure.
best regards,
to understand what happen need check
log.txt
bbox_log.txt
tmpfpln.txtSorry, but one picture may be cant help.
Hi !
Well, the picture is only to show that the plane does not go to HAM after GoAround.
The question is: should it go ?
If yes, that's a bug, and I will do that again and give you the logfiles.
If no, that's ok.As I do not exactly know the real behaviour when doing a GoAround, I'm just asking if anyone
knows what the plane should do :-)
ND should be show GA flightplan as active flightplan. What we see at screenshot - not Ok. But to understand WHY, need check logs.
Hello,
the front location isn´t correct (to deep) and it´s not possible to load the plane that it is correct
20160110_171709.jpg 912.29 kb, 175 downloads since 2016-01-10
20160110_171748.jpg 1.16 mb, 190 downloads since 2016-01-10
20160110_171831.jpg 1.65 mb, 174 downloads since 2016-01-10
Hello,
the Airplane follow not the green line in the ND (SID)
turn too early
20160110_165442.jpg 2.51 mb, 187 downloads since 2016-01-10
Hello,
the front location isn´t correct (to deep) and it´s not possible to load the plane that it is correct
Hmm.. Еще один..
What did you mean "too deep"? How much deep? 1 mm, 1 sm, 1 km??? What are you compare with? Have you a doc to make this comparasion possible?
https://www.youtube.com/watch?v=n3TJMro_NzA
https://www.youtube.com/watch?v=ECV3IBkzZLc
look this videos and i hope you can see what i mean
the pfd centerline is not below the horizon
i can not load the A320 Neo (with payload or pax) that it is the same
when the plane is unload it must be a little bit higher
I don´t know how much it must higher
and it is not a joke
The picture is from a other a320 with corectly position
2me1oqq.png 54.24 kb, 169 downloads since 2016-01-10
@ivota thank you ! exactly what i was looking for too )
I noticed that it seems to take a lot longer to get to the desired altitude based on the previous version. Has this been adjusted in this beta?
Hi JAR,
Thanks for the update. Hand-flying of this model is quite awesome and feels great.
One thing to mention is that: when in selected mode (HDG) the active flight plan doesn't turn into dashed line.
The ND should draw the active fpln in dashed green as the pic shown below.
Will it get fixed in the future? Many thanks.
Shane
Hey!
I've found the time to record a video.
https://www.youtube.com/watch?v=U040LzV … e=youtu.be
It is a EPWA EPGD route, RWY 11 departure OLIL5A SID L621 GRUDA to EPGD. So after departure I enter first DIRECT to GRUDA at around 1:55, then plane does turn, that is ok but i don't get why it doesn't go straight to GRUDA (starting from current plane position). Then around 4:17 it should however start turning right, another DIRECT is around 7:20 -> observe what happens later.
also at around 6:45 you can see that CSTR WPT VOR.D NDB ARPT buttons doesn't work
hope that helps!
Bartek
Hi !
ND should be show GA flightplan as active flightplan. What we see at screenshot - not Ok. But to understand WHY, need check logs.
Ok, not OK. Looks like it is on every Airport, now tried in edny, same behaviour.
FlightPlan:
EDDF SID ANEKI Y163 NEKLO Y171 INKAM T725 LAMGO T721 SUL T732 GARMO STAR EDNY
EDDF: Runway 07C, SID=ANEK1D, NO Trans
EDNY: Runway ILS24, GARM1P, VIA MOKOP, NO Trans
Here are some images from the landing:
And the requested logs:
DEBUG.zip 52.74 kb, 244 downloads since 2016-01-11
Hi, if you click on MCDU EDNY appear another time a RWY for approach
As someone else posted, ILS glide slope capture is not working. Approach selected, ILS selected, VOR MODE selected (tried ILS mode too). Would not capture GS even though it was clearly visible in the HSI display.
Also, the KLAS SUNST3 STAR is still adding additional fixes after what should be the final fix: PRINO. Manually deleted them and no issues. This should be easy to recreate...KSFO SSTIK3 SUNST3 RWY 25R.
bbox_log.txt 4.18 kb, 263 downloads since 2016-01-12
Hi, not a bug as such, but on loading X-Plane yesterday was given the opportunity to update to 10.45r2. I did and after a flight with no problems on shut down from X-Plane the system CTD.
I appreciate this may well be an X-Plane problem or my system, but I've posted it for the information of others.
As someone else posted, ILS glide slope capture is not working. Approach selected, ILS selected, VOR MODE selected (tried ILS mode too). Would not capture GS even though it was clearly visible in the HSI display.
Also, the KLAS SUNST3 STAR is still adding additional fixes after what should be the final fix: PRINO. Manually deleted them and no issues. This should be easy to recreate...KSFO SSTIK3 SUNST3 RWY 25R.
Yeah! This is a cool example with black box inside.
Lets look at log:
>>> zulu 20:54:37
baro alt=5000 / rad alt=3553
air spd=180 / gnd spd=194 / mach=0.29
lat mode = APP NAV
vert wait = FINAL
>>> zulu 20:56:58
baro alt=4999 / rad alt=3298
air spd=139 / gnd spd=151 / mach=0.23
vert wait = ALT
vert mode = DES
vert wait = FINAL
thr mode = THR IDLE
thr mode = SPEED
What we can read here? Yes, that was not ILS approach. That was some NPA approach. For this approach no LOC/GS should happen. And yes, for this kind of approach "ILS glide slope capture is not working" And it is normal. Thanks for example, anyway!
Good Day,
My version on the name plate said '2.6B 4P' question where did P come from and why is aircraft acting funny ? won't follow flight path and won't delete DISCO points in Flight plan when in the air now I will have to try to remove DISCO points while on the ground but MCDU went blank and I had to recover Flight plan while in the air but could not remove DISCO to complete DISCO and then I had same issue as posted above where the aircraft did not want to ILS approach I had to land Manual.
hope this helps no CTD to give and I do not think a log.txt is need in this case maybe bbox.txt ?
captbullett
Hello everyone,
Could someone verify that Logo Lights (at tail) is working during flight.
I made two flights at night and the results are:
1. Before take off I turned on Nav & Logo + Wing lights - they are turned on and working
2. After take off and climb aprox 2000+ - Nav lights - worked, Logo lights - not worked, Wing lights - worked
3. After descending to aprox 3500 - Logo lights starts working again.
4. After landing - all light continue working without issues.
Hi, forgive me if I've missed this somewhere (or I am not doing this correctly).
In the previous stable version (2.5) I could execute a hold pattern with ease.
I am testing the BETA V2.6 and I cannot get the aircraft to start a hold pattern.
Before I go any further, is there a FMC guide to accompany V2.6? or should I be doing something different compared to V2.5.
Thanks,
Simon.
Good Day,
My version on the name plate said '2.6B 4P' question where did P come from and why is aircraft acting funny ? won't follow flight path and won't delete DISCO points in Flight plan when in the air now I will have to try to remove DISCO points while on the ground but MCDU went blank and I had to recover Flight plan while in the air but could not remove DISCO to complete DISCO and then I had same issue as posted above where the aircraft did not want to ILS approach I had to land Manual.
hope this helps no CTD to give and I do not think a log.txt is need in this case maybe bbox.txt ?
captbullett
Yes, at least need log.txt file.
"P" mean what it is a public beta (posted at official website)
Ok will send as soon as I get to computer I will look and see if info is saved from flight.
or I will send on next flight thank you for feed back.
Brian
PS yes you will see a SASL issue on the log.txt as follows;
[SASL ERROR] Error updating avionics: [string "/Users/brianhelip/Desktop/X-Plane/Aircraft/A3..."]:0: bad argument #1 to 'len' (string expected, got nil)
captbullett wrote:Good Day,
My version on the name plate said '2.6B 4P' question where did P come from and why is aircraft acting funny ? won't follow flight path and won't delete DISCO points in Flight plan when in the air now I will have to try to remove DISCO points while on the ground but MCDU went blank and I had to recover Flight plan while in the air but could not remove DISCO to complete DISCO and then I had same issue as posted above where the aircraft did not want to ILS approach I had to land Manual.
hope this helps no CTD to give and I do not think a log.txt is need in this case maybe bbox.txt ?
captbullettYes, at least need log.txt file.
"P" mean what it is a public beta (posted at official website)
Log.txt 471.34 kb, 247 downloads since 2016-01-14
Did not fly to next waypoint on a STAR just maintained heading after leaving last waypoint latest beta version
Screen Shot 2016-01-14 at 7.05.57 AM.png 416.18 kb, 150 downloads since 2016-01-14
Ok will send as soon as I get to computer I will look and see if info is saved from flight.
or I will send on next flight thank you for feed back.
BrianPS yes you will see a SASL issue on the log.txt as follows;
[SASL ERROR] Error updating avionics: [string "/Users/brianhelip/Desktop/X-Plane/Aircraft/A3..."]:0: bad argument #1 to 'len' (string expected, got nil)J.A.Romanov wrote:captbullett wrote:Good Day,
My version on the name plate said '2.6B 4P' question where did P come from and why is aircraft acting funny ? won't follow flight path and won't delete DISCO points in Flight plan when in the air now I will have to try to remove DISCO points while on the ground but MCDU went blank and I had to recover Flight plan while in the air but could not remove DISCO to complete DISCO and then I had same issue as posted above where the aircraft did not want to ILS approach I had to land Manual.
hope this helps no CTD to give and I do not think a log.txt is need in this case maybe bbox.txt ?
captbullettYes, at least need log.txt file.
"P" mean what it is a public beta (posted at official website)
If this error happen ([SASL ERROR] Error updating avionics: [string "/Users/brianhelip/Desktop/X-Plane/Aircraft/A3..."]:0: bad argument #1 to 'len' (string expected, got nil)) - yes, that was an error in internal a320 (in my code) calculation. Thanks for report.
Just tested b4, my bugs reported in beta 2 (http://jardesign.org/forum/viewtopic.php?pid=7511#p7511) still exist, confirm?
Another bug...
On the way to the runway (while taxiing) my aircraft started accelerating (seems to be TOGA) uncontrolled, I have no idea what happend. I did nothing, just taxiing with low throttle. Screenshot and logs are attached!
I had it several times with different versions, I just thought it would have been fixed with some of the last betas. but it's still present.
Hope to have an A320 without major bugs and working as the real one does soon :-)
a320neo_567.png 1.21 mb, 177 downloads since 2016-01-14
bbox_log.txt 2.65 kb, 265 downloads since 2016-01-14
Log.txt 60.74 kb, 360 downloads since 2016-01-14
JARDesign Group Board → Beta-versions (Download & Discussions) → ver 2.6 beta 4 WIN/MAC 64 bit
Powered by PunBB, supported by Informer Technologies, Inc.
