Jump to content

Airbus X version 1.20


Mathijs Kok
 Share

Recommended Posts

  • Root Admin

Version 1.20 contains the following updates/ This will not be shipped as an update but as a full new build.

FIXES AND CHANGES IN VERSION 1.20

  • AUTOBRAKES CHANGED
    Should not work even when flaps are retracted too soon and when wheel brakes are just used for a short period of time. We still advice the flaps to be retracted when leaving the runway, not before.
  • OUTER WING TANK QUANTITY GOING NEGATIVE BUG REMOVED
  • ADDED AUTOTHROTTLE DISCONNECT SOUND ADDED
    When Autothrottle is disarmed the caution light will go on and caution chime will sound.
  • AUTOLAND IMPROVED
    Flare is now smoother, but make sure you are at a suitable weight!
  • WING VIEW ISSUE SOLVED
    The whole wing is now visible.
  • QNH IN MCDU NOW ACCEPTS InHg
  • LAN LIVERY INCLUDED
    With thanks to Carenado!
  • BETTER CLIMB PERFORMANCE, BETTER TAKE-OFF PERFORMANCE
    climb to 30.000 feet in 15 minute now possible, see below.
  • NOSEDIVE ON MANUAL LANDING SOLVED
    Disabling AP on final no longer a problem.
  • SPEED TAPES CORRECTED
  • WHITE BOX FOR 10 SEC AROUND FMA-ANNOUNCEMENT
    For 10 seconds after each change there will be a white box around the FMA announcement.
  • ND NOW HAS HDG BUG
    The ARC mode now also shows the HDG bug.
  • SPOILER ARMING REDONE TO NON FSX STANDARD
    Allowing spoiler arming under all conditions with the right mouse button.
  • MCDU PERF PAGE NOW SHOWS DURING PREFLIGHT
  • THR RED ACC & ENG OUT ACC ALTITUDES NOW DEPEND ON ALTITUDE
  • SPEED CONTROL ADDED FOR APPROACH STAGE
    Approach mode will automatically be armed once starting descend with all AP functions in managed mode. Start of descend must either be triggered automatically when reaching TOD (A lower FCU altitude than Cruise altitude should be set) or when starting the descend in managed mode by pressing the EXP button. It can also be armed on the PERF APPR page by pressing LSK6L - "ACTIVATE APPROACH PHASE" will then change to "APPROACH PHASE ACTIVATED". This also happens when changing automatically. Once below 7200 ft AGL speed will be reduced to flap 1 speed setting, extending flaps will reduce speed further until flap 4 where speed is set to Vapp.
  • DAYTIME LIGHT ARTIFACTS REMOVED
  • PFD AND ND DISPLAYS NOW REFRESH FASTER
  • FLIGHT DIRECTOR HEADING CORRECTED
  • ROLL-OUT MODE INCLUDED
  • IN MANAGED MODE, THE FMA SHOULD SHOW [sPEED] AND NOT [THR CLB] AFTER REACHING CRUISE LEVEL.
  • IF "CONF 3" IS CHOOSEN ON PERF APPR PAGE, THEN LANDING CHECKLIST WILL COMMAND FLAPS 3 INSTEAD OF FLAPS FULL

    KNOWN ISSUES
    These issues are scheduled to be fixed after the 1.20 release (no guarantee though)
    • VLS is always higher than Vapp, this is not correct
    • A/SKID switch triggers seat belts sign
    • Airbus X Connect update

    KNOWN ISSUES

    These issues are know but are not easy to solve.

      [*]ND-range from "20" to "10", the flight-track gets cut off [*]Note that the F/O displays do not show all information, this is by design to lighten fps load

  • Upvote 2
  • Downvote 2
Link to comment
Share on other sites

This is wonderful, thank you for your continued efforts. I was wondering however, if you noticed my post on a previous thread regarding this factor and whether it will be fixed?

When on the ground, the flight controls appear to be realistically sensitive - you can look at the outside and see the ailerons/elevators moving in-conjunction with the ECAMs FLTCTRL page. However, once airborne the ailerons/elevators don't appear to move as quickly/sensitively as when you where on the ground - and if you check the ECAMs FLTCTRL page, you'll see the ailerons/elevators animations no longer match. It does kind of make it feel like you are flying a larger plane, but a plane of this small size I'd expect it to be a fairly sensitive.

Link to comment
Share on other sites

This version will also be included in the boxed version. This will not be shipped as an update but as a full new build.

Who bought the first version will have the right to update right?

Another issue would be a big step in FMGS add a patch that allows to modify the speed and altitude in fixes.

Being possible to insert correctly the sid and their star's altitude and speed restrictions inserted.

Thx

Link to comment
Share on other sites

  • Root Admin

This is wonderful, thank you for your continued efforts. I was wondering however, if you noticed my post on a previous thread regarding this factor and whether it will be fixed?

Sorry part of this as the aircraft systems work and part of the problem is how FSX handles FBW systems. Nothing we can do.

Link to comment
Share on other sites

  • Root Admin

This sounds very good! But please don't forget to make the gauges smoother in VC, it's like in FS9 - horrible. And please correct the GPWS like discussed here http://www.forum.aer...showtopic=38073 and here http://www.forum.aer...showtopic=38185

Thank you !!!

Regards, Chris

Sorry we'll keep that as we got it. The sounds we use are standard, all others are optional when you order an Airbus and some companies do not use them because they cause confusion when the aircraft remains level for a while. The gauges are smoother.

Link to comment
Share on other sites

  • Root Admin

This version will also be included in the boxed version. This will not be shipped as an update but as a full new build.

Who bought the first version will have the right to update right?

Another issue would be a big step in FMGS add a patch that allows to modify the speed and altitude in fixes.

Being possible to insert correctly the sid and their star's altitude and speed restrictions inserted.

Thx

Every customer will always be able to update, but this one will be a full new build to make it simpler.

We do not intend to change the way the SIDs and STARs are handled. See this topic for more information: http://www.forum.aerosoft.com/index.php?showtopic=38888

Link to comment
Share on other sites

Glad all of that will be taken care of. Here's a few things I've noticed that aren't listed for 1.20

  • FSX Crashes on End Flight, Reload, Aircraft Change, and Exit.
  • From/To cannot be changed in MCDU for second flight.
  • Flight Number in MCDU clearing results in CLR entering into your flight number.
  • Batteries will drain if APU gen. is on.
  • Taxi light is far too dim.
  • Takeoff Inhibit and Landing Inhibit warning still shows up on upper ECAM after completing the takeoff and landing memos.

Link to comment
Share on other sites

  • Root Admin

What happened to the disappearing TOC and TOC arrows when you've got more than 5 waypoints before TOC or more than 5 waypoints after TOD? Was listed in previous list of known issues ....

Very complex issue. It is still a known limitation and I am pretty sure the 1.20 fix will not change it. Not forgotten though.

Link to comment
Share on other sites

  • Root Admin

Glad all of that will be taken care of. Here's a few things I've noticed that aren't listed for 1.20

  1. FSX Crashes on End Flight, Reload, Aircraft Change, and Exit.
  2. From/To cannot be changed in MCDU for second flight.
  3. Flight Number in MCDU clearing results in CLR entering into your flight number.
  4. Batteries will drain if APU gen. is on.
  5. Taxi light is far too dim.
  6. Takeoff Inhibit and Landing Inhibit warning still shows up on upper ECAM after completing the takeoff and landing memos.

1) if anybody can show us what's wrong we can fix it. I know it's a nasty one but we are far from the only complex aircraft that suffers from it. We are sure it's a bug in FSX that has to do with memory but it simply can not be debugged without the help from MS. And that.....

2) will check.

3) will check

4) see http://www.forum.aerosoft.com/index.php?showtopic=38162. I simply do not see that (I am on APU for two hours now) and it's an issue we can't understand. None of the testers or devs have it. We would appreciate any help in this.

5) that's because we use a system that works far better from the VC then from external view (as we intended). We will not change that, what we got it too superb too loose.

6) will check that, but I did not see that. You see this after you followed the Vol6 step by step guide?

Link to comment
Share on other sites

Sorry we'll keep that as we got it. The sounds we use are standard, all others are optional when you order an Airbus and some companies do not use them because they cause confusion when the aircraft remains level for a while. The gauges are smoother.

Thanks for the info. Ok, some of us simmers have there own call outs and its very easy to replace the original sound files, so there is no problem. But please let the "retard - call" start after 20Ft, that's all. It's must be very simple to do that and there is a little bit time till monday :rolleyes:

Thank you !!

Chris

Link to comment
Share on other sites

  • Root Admin

Thanks for the info. Ok, some of us simmers have there own call outs and its very easy to replace the original sound files, so there is no problem. But please let the "retard - call" start after 20Ft, that's all. It's must be very simple to do that and there is a little bit time till monday :rolleyes:

Thank you !!

Chris

Hold on, you say the retard call does not come at the right time? That's not an issue on my list and I did not see anything wrong with it (but I am the world worst pilot).

  • Upvote 1
  • Downvote 1
Link to comment
Share on other sites

Thanks for all the hard work guys, and especially for your responsiveness to bug reports.

I have never seen any major FSX add-on development team be so publicly responsive to bugs in a 1.0, and release patches and fixes so quickly. The open dialogue about the product that was happening in this forum was a major reason I decided to go ahead and buy, despite known problems & limitations.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use