Re: ver 2.6 beta 4 WIN/MAC 64 bit
it´s possible you have planed a to high Fl
No. In the navigation display the T/D and T/C shouldn't be marked as a FIX in "To wpt/track".
You can get the distance and ETA from the CDU
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
it´s possible you have planed a to high Fl
No. In the navigation display the T/D and T/C shouldn't be marked as a FIX in "To wpt/track".
You can get the distance and ETA from the CDU
Eugeny,
Testing 2.6b4 I am getting occasional Spurious TCAS alerts.
Also in managed Approach Mode after selecting Flaps 1 Speed is Not reducing automatically to Flaps 2 speed as it previously did.
Regards
Steve
Steve - this is exactly the problem I am having with this release. Others are reporting the they do not have this problem! In my case, this happens in every flight when descending in managed mode.
Underparts wrote:Eugeny,
Testing 2.6b4 I am getting occasional Spurious TCAS alerts.
Also in managed Approach Mode after selecting Flaps 1 Speed is Not reducing automatically to Flaps 2 speed as it previously did.
Regards
Steve
Steve - this is exactly the problem I am having with this release. Others are reporting the they do not have this problem! In my case, this happens in every flight when descending in managed mode.
Yeah exactly and if you try to set flaps 2, the fo will say you are to fast. Then the speed drops to the speed for flaps 3 and suddenly jumps back to the speed for flaps 2...
The behavior of the reflections has changed. Now it's disabled by default. Is this the expected setting now?
Is possible shared cockpit?
Thx
Good day!
Yes, it's posible.
http://xsmart-plane.com/smartcopilot/
Is possible shared cockpit?
Thx
Some know Why i get both wingtips at the same time (beta2.6r4 +hf1)
Hi all, i encountered a bug whereby the speed brakes/spoilers won't deploy (by pressing #4) if the AP gets disconnected during flight.
Re-engaging the AP won't fix the problem either. Is there a fix for this bug? My Flight Factor 777 spoilers/speed brakes works just fine so it's not the joystick nor keyboard mapping. I also confirm that this same bug exist in the A330.
Log files are attached.
Hi all, i encountered a bug whereby the speed brakes/spoilers won't deploy (by pressing #4) if the AP gets disconnected during flight.
Re-engaging the AP won't fix the problem either. Is there a fix for this bug? My Flight Factor 777 spoilers/speed brakes works just fine so it's not the joystick nor keyboard mapping. I also confirm that this same bug exist in the A330.
Pictures are ok but, must have a log.txt to help then you will get answered.
captbullett
Zeke*Earl wrote:Hi all, i encountered a bug whereby the speed brakes/spoilers won't deploy (by pressing #4) if the AP gets disconnected during flight.
Re-engaging the AP won't fix the problem either. Is there a fix for this bug? My Flight Factor 777 spoilers/speed brakes works just fine so it's not the joystick nor keyboard mapping. I also confirm that this same bug exist in the A330.Pictures are ok but, must have a log.txt to help then you will get answered.
captbullett
Hi, log files are attached. I also discovered that i have to disengage AP, bank the aircraft left/right to 'force' the control surfaces to work. Spoilers/speed brakes work after doing so. Thank you.
Hey. Earlier version 2.4v3 used without problems . Established 2.6v4 . Do not operate the switches and buttons sounds , except for IRS switches. What is the cause ? Translation from Russian if not correct - sorry .
We just tried the A320 2.6B4hf1 with the SmartCopilot plugin and found some things not working correctly:
When the ADIRS knob "Enter" is pressed, the dataref "sim/custom/xap/adirs/knob_ent" is changed from 0 to 1.
But this does not seem to work when you have to confirm "STS-ENTER PPOS" message.
Before and afterwards the STS-message the dataref is updated correctly when pressing the button.
The Smartcopilot "satellite" datarefs of the "click" datarefs to control the MCDU are not written when clicking a key.
For example, "sim/custom/xap/mcdu/click_a" becomes 1 while pushing the A button on the MCDU, but according to smartcopilot wiki the dataref "sim/custom/xap/mcdu/click_a_SCP" should also be written to 1 (so smartcopilot can reset it to 0 after recognizing it).
We checked the *_SCP datarefs with Datarefeditor and could not see any changes, even with SCP-plugin disabled).
Maybe it's something that can be fixed.
Landing at rwy 17R SCEL on ILS approaching, AP doesn't follows ILS.
I've got to land in manual mode.
Best Regards
After takeoff pushing PERF button, then F-PLN button led first to a dark MCDU screen and after pushing again F-PLN flightplan was lost.
something wrong, and co-route f-plans working bad (f-plans discontinuinity)
something wrong, and co-route f-plans working bad (f-plans discontinuinity)
Discontinuinitys are normal (I've seen alot in the real thing), you just have to complete the route (normally: Enter [predicted] SID & STAR) and delete the Discontinuity.
Discontinuities are completely normal. Delete the last discontinuity in the plan before entering the STAR. Unless you're route is not properly planned then you just delete the discontinuity where it occurs.
Sorry for the question...is this aircraft still in development?
Hi!
I think, yes...
Sorry for the question...is this aircraft still in development?
After takeoff pushing PERF button, then F-PLN button led first to a dark MCDU screen and after pushing again F-PLN flightplan was lost.
Wasn't able to reproduce with the same flight plan, etc. Maybe a pilot error? Will continue testing.
Got a few bugs.
1) The EICAS will go into a frenzy and just auto switching itself through every function page. Happens randomly. Can't stop it no matter what I hit unless I exit and re-enter x-plane.
2) The baro calls out got stuck in a loop. All the way to landing the baro reference was being called out... VERY ANNOYING.
3) The checklists are wrong. Pretty sure they shut the APU down once engines are running. Yet the takeoff checklist requires APU on lol.
4) WX radar does not display. Yes, I was in a big storm. Yes, the WX system was on. I hold an A&P and worked for Jetblue on the Airbus I beyond know the WX system.
5) the HD terrain does not switch off easy once switched on.
6) the Baro will not dial in .1 changes sometimes. For example it will go from 2992 to 2994 and will keep skipping 2993 no matter how I try to dial it in.
1) You pressed the "ALL" button which scrolls through every EICAS page until pressed again. This is an accurate feature of Airbus but the real aircraft scrolls through slower.
2) What do you mean by the Baro reference being called out? What exactly do you hear and how often?
3) You may well be right about the checklist. I find it much easier and realistic to turn the F/O off and follow my own checklists.
4) What version of the A320 are you using? The Wx radar does work and needs to be angled appropriately. If there's green/yellow/red on the X-Plane map in the weather menu then it will be displayed on the ND. I think on one of the previous versions it only worked when set to 20nm display.
5) You need to hover over the Terrain button with the down arrow displayed before clicking.
6) it is slightly difficult to accurately dial in Baro but if you make tiny mouse movements should be no problem.
1) You pressed the "ALL" button which scrolls through every EICAS page until pressed again. This is an accurate feature of Airbus but the real aircraft scrolls through slower.
2) What do you mean by the Baro reference being called out? What exactly do you hear and how often?
3) You may well be right about the checklist. I find it much easier and realistic to turn the F/O off and follow my own checklists.
4) What version of the A320 are you using? The Wx radar does work and needs to be angled appropriately. If there's green/yellow/red on the X-Plane map in the weather menu then it will be displayed on the ND. I think on one of the previous versions it only worked when set to 20nm display.
5) You need to hover over the Terrain button with the down arrow displayed before clicking.
6) it is slightly difficult to accurately dial in Baro but if you make tiny mouse movements should be no problem.
Re: 6)
Even using a .lua script dialing at 0.01 mmHg accuracy, I am sometimes not able to do so as reported by locvirtual. I am, however, able to dial single digit accuracy in hPa. Might be some conversion rounding glitch. hPa should be used universally, in my mind. Even in the US, theoretically the metric system is the law (very obviously unenforced )
After a long beta-test period we publish 2.6 release 1
Please enjoy http://jardesign.org/forum/viewtopic.php?id=1882
JARDesign Group Board → Beta-versions (Download & Discussions) → ver 2.6 beta 4 WIN/MAC 64 bit
Powered by PunBB, supported by Informer Technologies, Inc.