A320 FMGS beta 26

[kikigey89]

Sure, this is just a suggestion. AP VS behaviour is much more important than this

[jeehell]

Hello,

Ok B10 was probably a mistake

http://www.jeehell.org/A320FMGS_B11.zip

Now B11 is out, and a lot of bugs should be gone:
-Flight profile computation if FPLN DISCONTINUITY is present
-FOB under FS9
-Auto-trim when on ground
-Pseudo waypoints messing with the NAV mode
-Hopefully the big problem causing AP/FBW instability under FS9
-PERF TO page showing wrong RWY
-FO PFD now saves hide border/lock position/always on top settings
-MCDU 'green' error...
-Glide slope should be followed much better until touchdown. I still recommend flaring under manual control.

-Added more options and pages from the DATA page on the MCDU (POS,IRS and GPS monitor). When in flight, you can align the IRS in ATT mode through the MCDU IRS MONITOR page (the HDG you enter will not be used, only the real HDG, HDG and position drift will be taken into account later)
-OVHD graphics can now be changed. They are in the folder OVHD\Graphics. Only restriction: you need to keep the same size (size, not proportion) and position of switches!!
-I included the iFDG A320 I use in the package. The aircraft.cfg file has already been modified to suit the FMGS software, so only copy to your aircraft folder.

Have fun!

[kikigey89]

Hi,

maybe not a mistake but a bugfull release But it seems that all this bugs are away
Currently I'm on a testflight and it works perfectly until now.
Just one issue at this time: FO PFD shows "ATT" and no artifical horizon.

Chris

[kikigey89]

First of all thank you for this nice flight this evening with your FMGS! It was my first complete flight (including LOC and GS) with it.
There was no major bug! Just a few things:

• The SD error ("'-9223372036854775808' is not a valid integer value.") is still there and occurs also if FS is not paused.
• Reaching CRZ ALT "CRZ ALT" was displayed on PFD but the white border around it was also displayed in the space below CRZ ALT. But there is no message which could get a border.
• GW is available in MCDU but not on SD
• Actions of AP could be a little bit smoother (pax comfort)
• GS was perfect (!!!) but there were some problems capturing the LOC. The aircraft turned left and right until the LOC was captured.

[jeehell]

Hello!

Well great news!!

• I will look into the SD error, it never happened to me yet... Any idea on what might triggers it? (flight phase, action on FCU or OVHD ??)
• CRZ ALT: I need to check if the white box should appear when engagement of an armed mode happens.
• Ok will correct that
• AP smoother:It's on the lsit as well
• LOC*:How many times did it turn to fully capture? Usually, it should overshoot at most once, the second time it should follow correctly the LOC. Maybe your speed was a bit too fast? (I recommend speed less than 220knots)

Cheers,
JL

[kikigey89]

Hi,

No idea. Most time I recognized that some messages poped up in the background. I will try to find out when it happes.
My speed was around 200 knots. I think my aircraft made around 5 or 6 turns.

[jeehell]

Ok, 5-6 turns is way too much. I will see if I can do anything...

[kikigey89]

My train to university was cancelled so I decided to stay at home today
So I have time to perform a second testflight today.

Chris

[kikigey89]

Hi,

my second testflight was... let me say not as good as the first one The entire vertical stuff was never doing what I want it to do. First I made a lot of screenshots of that but then I noticed that the only thing which was different to my first testflight was, that I deactivated the FBW. So I activated it on descent and it seemed to work! But nevertheless the GS and LOC was not captured, maybe due to my overall bad approach. Maybe you can check if this happens, too, if you deactivate FBW. I wanted to test it on another flight but after entering origin and destination for this new flight IRS alignment was lost and CPT ND got an error message: "Access violation at address 00404F87 in module 'ND.exe'. Read of address 00000002.". I had to reset my computer because it had a complete crash with this message.

By the way the SD error message did not appear again.

Some other things:

• As far as I know from my cockpit visits (A320) and from Wilco series, airway and waypoint can also be entered in the format "airway/waypoint", e.g. "T207/BATEL".
• On SD appears only the left front door if opened. The others do not appear as open even there open in FS.
• Is there a RWY mode yet on take-off?
• Fuel used is not available (I think it's a FS9 problem)
• Suddenly MCDU has set a new CRZ ALT... (FL340 instead of my entered FL230)
• Push to level of did not work. VS was still 700 ft/min.
• As far as I know the ILS APP gets active if I activate the approach phase in MCDU and not if I select an approach route.
• VOR DME on ND: if decimal place is 0, the zero does not appear. Example: Instead of 45.0 only "45" is displayed.
• Still some graphical issues concerning the flightpath lines on ND.

[jeehell]

Hello,

Ok I will check that FBW thing.
When you tried a second flight, you didn't restart the FMGS server? I think it is safer to do so for the moment, probably some messy code somewhere...

• AWY syntax: never heard of that, I'll check thanks.
• SD doors page: FSUIPC offset for doors is not exactly exhaustive...
• no RWY mode yet on TO
• indeed fuel used is not available in FS9. I'll see if I can add an accurate fuel calculation based on instantaneous fuel flow.
• MCDU CRZ ALT: I never had this error. From my code point of view () the only way to get this in the MCDU is to increase the FCU altitude above the CRZ level, which is normal.
• Level off: I will check/correct that
• This is actually obscure in the FCOM, I need to read it more carefully
• DME decimal: will correct that
• ND curves: this is a very old bug, but very tedious code there. If I am in the mood someday...

Thanks for the report,
JL