Airbus A320neo (A319,A320,A321)

[bicyus]

Boeing, test the new version

Airbus A320neo V2.2 Beta 2C

- New 3D sound updated
- New sparks efect on Belly landings (gears up)

Give me feedback on how Aircraft sounds now, and get a try on belly landings with out gears, you'll see sparks comming from engines

[bicyus]

Update
Navigation Display:
- ARC Mode NAV bugs Corrected
- Flight track Path added ARC + ROSE
- Aircraft Align bug added ARC + ROSE
- New Mask
- Ground Terrain Radar added & fixed from 787-8

https://gitorious.org/airbus-aircraft/a320neo/archive-tarball/master

[omega95]

- Ground Terrain Radar added & fixed from 787-8

Cool, btw what do you mean by 'fixed'... If it turns out better than the positional ground radar in the 787, I'd love to replace the 787 ground radar.

Oh and I also tested the A320neo from git (pulled yesterday) and it's a pretty awesome aircraft now... But then the FDM acts kinda weird when you pitch down to much... And I couldn't get the fly-by-wire working properly either... I did a couple of tests and logged some properties.. Also found the relation b/w gspeed, g-force and pitch-rate. I'll try out a different fly-by-wire system for the neo soon.

EDIT : http://flightgear.org/forums/viewtopic.php?f=4&t=15947

[Sorcerer]

Hi,

great updates

But one thing that is still missing is some navigational data like waypoint, distance and eta.
I added this information in the currently empty page-NAV.xml

page-NAV.xml

Code: Select all

<?xml version="1.0"?>
<PropertyList>
    <name>NAV</name>
    <w-base>256</w-base>
    <h-base>256</h-base>
    <layers>

   <!-- right top corner, line 1: display waypoint id and bearing  -->
   <layer> 
            <name>Waypoint ID</name>
            <type>text</type>
            <font>arial_black</font>
            <point-size>8</point-size>
            <color>
                <red>1.0</red>
                <green>1.0</green>
                <blue>1.0</blue>
            </color>
            <chunks>
                <chunk>
                    <type>text-value</type>
                    <property>autopilot/route-manager/wp/id</property>
                </chunk>
            </chunks>
            <transformations>
                <transformation>
                    <type>x-shift</type>
                    <offset>40</offset>
                </transformation>
                <transformation>
                    <type>y-shift</type>
                    <offset>115</offset>
                </transformation>
            </transformations>
        </layer>
   <layer>
            <name>Waypoint Bearing</name>
            <type>text</type>
            <font>arial_black</font>
            <point-size>7</point-size>
            <color>
                <red>0.0</red>
                <green>1.0</green>
                <blue>0.0</blue>
            </color>
            <chunks>
                <chunk>
                    <type>number-value</type>
                    <property>autopilot/route-manager/wp/bearing-deg</property>
          <format>%3.0f</format>
                </chunk>
            </chunks>
            <transformations>
                <transformation>
                    <type>x-shift</type>
                    <offset>100</offset>
                </transformation>
                <transformation>
                    <type>y-shift</type>
                    <offset>115</offset>
                </transformation>
            </transformations>
        </layer>

   <!-- right top corner, line 2: display distance to waypoint and the unit (NM)  -->
   <layer>
            <name>Waypoint Distance</name>
            <type>text</type>
            <font>arial_black</font>
            <point-size>7</point-size>
            <color>
                <red>0.0</red>
                <green>1.0</green>
                <blue>0.0</blue>
            </color>
            <chunks>
                <chunk>
                    <type>number-value</type>
                    <property>autopilot/route-manager/wp/dist</property>
                    <format>%4.0f</format>
                </chunk>
            </chunks>
            <transformations>
                <transformation>
                    <type>x-shift</type>
                    <offset>75</offset>
                </transformation>
                <transformation>
                    <type>y-shift</type>
                    <offset>100</offset>
                </transformation>
            </transformations>
        </layer>
   <layer>
            <name>Waypoint Distance Unit (NM)</name>
            <type>text</type>
            <font>arial_black</font>
            <point-size>7</point-size>
            <color>
                <red>0.5</red>
      <green>1.0</green>
      <blue>1.0</blue>
            </color>
            <chunks>
      <chunk>
                   <type>literal</type>
                   <text> NM</text>
                </chunk>
            </chunks>
            <transformations>
                <transformation>
                    <type>x-shift</type>
                    <offset>100</offset>
                </transformation>
                <transformation>
                    <type>y-shift</type>
                    <offset>100</offset>
                </transformation>
            </transformations>
        </layer>


   <!-- right top corner, line 3: display ETA to waypoint  -->
        <layer>
            <name>ETA</name>
            <type>text</type>
            <font>arial_black</font>
            <point-size>7</point-size>
            <color>
                <red>0.0</red>
                <green>1.0</green>
                <blue>0.0</blue>
            </color>
            <chunks>
                <chunk>
                    <type>text-value</type>
                    <property>autopilot/route-manager/wp/eta</property>
          <format>%s</format>
                </chunk>
            </chunks>
            <transformations>
                <transformation>
                    <type>x-shift</type>
                    <offset>100</offset>
                </transformation>
                <transformation>
                    <type>y-shift</type>
                    <offset>85</offset>
                </transformation>
            </transformations>
        </layer>
    </layers>
</PropertyList>


This should also be added to the ARC mode like in the real airbus (video on the previous page at 3:25)

[omega95]

My Jabiru J-170 and Boeing 787-8 projects are on hold till I get any info on camera view (and terrain view) to texture from Rembrandt, so I'm re-visiting the A320neo project.

I mean big time, I started working on a new flightdeck and'll soon do some nasal stuff, systems (like hydraulics, maybe a new electrical, pneumatics, fuel etc.) and of-course, the airbus mCDU soon..

Here're a couple of shots of the main cockpit panel so far, started work on this about an hour ago.





About time the Airbus A320/A330/A340 cockpit got some serious attention.

[bicyus]

[Cool, btw what do you mean by 'fixed'... If it turns out better than the positional ground radar in the 787, I'd love to replace the 787 ground radar.

Omega95, the Aircraft was on bottom left, in the terrain that was represented. I fix it so the A/C is in the Bottom/Center position of the represented Field.
https://gitorious.org/fg-boeing-787-8/fg-boeing-787-8-main/commit/db9b273cad7e2d5a9d88a801e4a0b51917e10236

And that cockpit looks AWESOME!!!!

Sorcerer:

your right, Page-NAV.xml Updated!

[omega95]

[omega95]

[Muffinman]

Lookin' good Omega!!

[omega95]

Lookin' good Omega!! (5 smilies here)

Thanks

And some more work...

[bicyus]

GO GO GO!!!

Looking very good Omega95!

just hopping it is poly optimized i'm going to need a new Graphic card! my computer is getting old!

Keep Going mate!
I'm on Airbus FBW, mixing you work and mine.

[bicyus]

Hi Guys,

As on every "open" project, many people has worked on "A320neo". But surprisely it doesn't have any license.

I would like the airplane to be added to FG-DATA so it is published in next release, for that we need to be GPL license.

So, is there any objections on releasing as GPL? if there is any, please come up. otherwise i'll go ahead.

I'm adding an Authors.txt too.

Thanks

[Figaro]

Well considering it's practically all evolved from the A320-family in FG, I see no reason why not.

[omega95]

Jon, can you give me a brief idea of what systems already exist (the XML stuff you've done) so that I can work on remaining nasal systems for the aircraft.

[bicyus]

- fuel is fully done on JSBsim (but electrical part missing, like pumps only work on electrical power)
maybe adjust Engines FDM for fuel consumtion.
Add a Jetison valve switch, just the switch, it's already on system but don't know were this is done on Airbus. Maybe on CDU?

- electrical, should need a review, engine1 generator not working (RAT MISSING)

- Hidraulic... what is that? xD to be done i think (blue, green, yellow systems)
- CDU/FMGU (we sould wait for 787-8 framwork or something like that)
- ND needs some work, for Waypoints or Radar TCAS, actualy in only use the WXRADAR image.

it would be grate to have something like Co-Pilot from 787-8 and that Announce for every system

INTERESTING: ECAM Actions and Alarm Systems, we need something new here.