You are not logged in. Please login or register.
JARDesign Group Board → Beta-versions (Download & Discussions) → ver 2.6 beta 2 WIN/MAC 64 bit
Noticed something while updating the navdata cycle, but feel free to ignore it since i'm running on linux.
I need to rename the navdata files (Waypoints.txt, Airports.txt ... etc) into lower case or the FMC won't find any data. Expected it somehow since, unlike on windows, the case of the letters matters under linux.
Just a small quirk, keep up your amazing work on this plane. :-)
Airport: KPSP PALM SPRINGS INTL
Procedure: CATH1 CATHEDRAL ONE
Runway: 13R, 31L
AIRAC: 1513
Provider: Navigraph
Remarks: CATH1 is listed twice for departure procedures.
Airport: KPSP PALM SPRINGS INTL
Procedure: RNAV (RNP) Z RWY 13R
Runway: 13R
AIRAC: 1513
Provider: Navigraph
Remarks: Using PSP transition.
Airport: KPSP PALM SPRINGS INTL
Procedure: RNAV (RNP) Y RWY 31L
Runway: 31L
AIRAC: 1513
Provider: Navigraph
Remarks: Using BALDI transition.
+AirFMC compatible fixed for beta 3
+FUEL prediction indication fixed for beta 3
I plan to post beta 3 on next week (middle, i hope)
Dear Pilots, thanks for ALL your posts and testing, i read ALL, sure. Not answer for most of them, but take in account.
Hi !
Really good news :-) thank you very much !!
+AirFMC compatible fixed for beta 3
+FUEL prediction indication fixed for beta 3I plan to post beta 3 on next week (middle, i hope)
Dear Pilots, thanks for ALL your posts and testing, i read ALL, sure. Not answer for most of them, but take in account.
best regards,
Hi, this beta is working very well, in my opinion. There are still a couple of small bugs, may be easy to solve:
- Standby compass light is not working (this is a loong lasting bug)
- Console/floor light is not working
- Front gear turns too much (till the opposite desired direction) when the tiller and the pedals are operated simultaneously
cheers
I am experiencing an issue with Flaps deployment whilst in Approach Mode. Its a bit complicated to explain so I will try my best:
When I select Approach Mode in a Managed Descent, the speed starts to decay to 210knots as expected. I then deploy Flaps 1 and the speed decays further but I expected the target speed indicators to display the target for Flaps 2 once I reach the Flaps 1 target speed, which they no longer do in this release. To get the speed to reduce below the Flaps 1 target I need to select Flaps 2 much earlier than my airspeed allows resulting in a Speed not Ok message. After that message the new target speed indicators appear and I can reduce speed using speed brakes. The remaining flap deployment schedule works as expected.
In Open Descent mode the flap deployment is normal and works as expected.
Has no one else has noticed this?
I did a few flight with airbus.
There is problem to Direct TO ...
Look this video at 00:26:42.
http://www.twitch.tv/ivota_hr/v/29236477
Maybe, I think algorithmic problems ( calculating route line to reach intersection).
I hope you understood me.
Good day,
well , one question as I don't have a log.txt so I am reading your mind you'er running 10.11 OS X and so may people on the .org have said in so, many different ways that you will experience unusual behavior when running 10.11 and as an Apple developer that also beta tested the 10.11 version and could not certify the OS as one that should be released I can only telling you there have been fixes by downloading a fresh copy of the latest version of the beta aircraft 2.6bx if you are not already running it. I hope this helps ,
captbullett
I had a another vision, you are on a version of XP that should be updated the 10.42r1 is a very good platform for Mac and this is why you are having issues wrong version of XP and wrong version of OS ...
I am experiencing an issue with Flaps deployment whilst in Approach Mode. Its a bit complicated to explain so I will try my best:
When I select Approach Mode in a Managed Descent, the speed starts to decay to 210knots as expected. I then deploy Flaps 1 and the speed decays further but I expected the target speed indicators to display the target for Flaps 2 once I reach the Flaps 1 target speed, which they no longer do in this release. To get the speed to reduce below the Flaps 1 target I need to select Flaps 2 much earlier than my airspeed allows resulting in a Speed not Ok message. After that message the new target speed indicators appear and I can reduce speed using speed brakes. The remaining flap deployment schedule works as expected.
In Open Descent mode the flap deployment is normal and works as expected.
Has no one else has noticed this?
3 flights and 3 time were i'm unable to activate the AP, i 've flight the same FP with 2.5r1 and i can activate AP withouot problem...about me this version is totaly unsable and bad then previous
JARDesign Group Board → Beta-versions (Download & Discussions) → ver 2.6 beta 2 WIN/MAC 64 bit
Powered by PunBB, supported by Informer Technologies, Inc.