A320 FMGS beta 26

[jeehell]

Hello Rob,

just a quick first feedback regarding the new&fixed V23.2. I just had the chance to take a short flight... GREAT!!!! The ILS autotuning works. The pitch seems to remain abit more stable in neutral stick position. Even the first ILS approach test worked. Have you changed anything with the ILS behaviour or was it pure coincidence? However, its great & I am really thankful!

No coincidence at all This is also why I turned over to the xplane database, it allowed me to completely recreate the ILS beam (LLZ+GS) outside FS, thus allowing much more precise ILS deviations. ANd much smoother AP on the APPR

- When you enter descent you have this magenta dot on the right side of the pfd which is based on the planed decent profile. It seems to works ok until you get to pass FL100. Then I have the feeling that this displayed vertical profile does not consider the speed reduction to 250kts. So the planed profile continues to steep while the AC has to reduce the vertical speed in order to maintain the speed limit below FL100. Do you know what I mean or am I completly wrong?

The VNAV is one of the msot difficult thing in the FMGS, I have rewritten that part 4 or 5 times already, and I began tonight the next rewriting
So yes I'm aware of those issues, I am working on it, and I hope I can find a solution soon!

- I am not sure about the real AC but when switching to VOR or ILS mode on the ND the top of climb and decent arrows remain on the display and keeping moving like in the other map modes in the background. Just the route disappears. I assume these arrows should disappear as well.

Yes indeed, it should be fixed with next rewrite of VNAV...

-and a performance issue. When I turn on the waypoints on the ND even at lower ranges the frame rate of the ND drops way below 1FPS. It really becomes a slide show. Even just turning waypoints on and off takes some seconds to update the ND. Before you ask: I run FSX on an I7-920. 6GB RAM. Without the ND-display options everything is really smooth.

Do you run everything on that computer?
On mine (i7-860) I do also have FPS drop on the ND, but it's still acceptable. Anyway, this option is not used that often I think on the real A/C.


Cheers,
JL

[AirFan]

Seems like you never go to sleep ... It's quater past one in the morning and I though I am alone here
Really great news and I am sure you made many people very happy this weekend.

Yes, I run it on one PC at the moment. Here the ND framerate is not acceptable but as you said you dont really need it that often. Thats only nice to have... there are other things which are way more important like VNAV

many thanks buddy & good night.
Rob

[tom19]

HI JL,

one bug in new version. When inserting flightplan, FMGS server freezes when trying to enter new waypoint via airway. In this case from EFHK to EFTU, after ARTUR, Q1 MEDOT. When I try to insert MEDOT server stops. Also route EFHK/EDDF is quite difficult to insert in INIT page - needs more than one click of RSK1...

Regards,

Tommi

[jeehell]

Hello,

OK Tommi, I'll look at the AWY issue, I advise you enter the AWY manually for now....

Regards,
JL

[jeehell]

Hi all,

The B23.21 is just out, hopefully correcting most of the big bugs of the B23.2.
The problem with AWY remains, I have to rework the whole thing to adapt to X-plane AWYs database format...

http://www.jeehell.cockpitpassion.fr...MGS_B23.21.exe

Best regards,
JL

[AirFan]

Hi JL,

really nice... last night I performed a flight from A to B with V23.21. Again, no issues. The ILS seems to be way more stable! No reversion to GS*. Thumbs up! Only the flare needs some refinement. now its more a hard 3-point landing. I know you are aware of that.

Only the MCDU went abit crazy. The waypoint altiudes showed some 7 or 8 digit values changing their state all the times and there was not estimated arrival time (0:01). At about 2/3 of the way the arrival time has been updated correcty. Then also the waypoint altitudes showed their correct value. I guess it will be rework anyways with your new VNAV part.

2 questions:

- could you please explain the corrected altiude indicator wrt engines not running for a long time? I didnt get that.

- whats the logic of the auto retraction system of the flaps after take-off? Should it retract from 2 to 1+F after passing retraction speed? and then completly retract after passing the corresponding speed? Do I have to be in managed speed?

Thanks & regards,
Rob

[jeehell]

Hello,

2 questions:

- could you please explain the corrected altiude indicator wrt engines not running for a long time? I didnt get that.

- whats the logic of the auto retraction system of the flaps after take-off? Should it retract from 2 to 1+F after passing retraction speed? and then completly retract after passing the corresponding speed? Do I have to be in managed speed?

-In previous versions, if engines were not running, and batteries in FS were empty (can happen if you didn't select battery life unlimited in full version FSUIPC options, and you only had EXT PWR or APU), the artificial horizon dropped like on a C172 without gyro suction... I corrected that by using a different FSUIPC offset to get the attitude data.

-The flaps auto retracts from 1+F to 1 (this is not a physical position on the real flap lever) when speed is above 210kts, like the real acft.

regards,
JL

[AirFan]

Hello JL,

thanks for your explanations. Now I got it.

[AirFan]

Hello again,

again some feedback wrt V23.21:

- ATHR disconnect at thrust red alt. - when changing the levers from FLEX to CL autothrottle need to be engaged again. Can you confirm this behaviour?

- regarding lateral navigation I sometimes notice some strange looking routes... the turn isnt tangential to the outbound track as shown on the attached pic.

nd-bug.jpg

Thanks & regards,
Rob

[pdpo]

Jeehell,

you must have a profound knowledge of the airbus systems but some days ago I was looking for some answer which I did not find yet. I has to do with the flap logics talked about above.
As you say, at 210 knots the flaps autoretract to slats only but which speed is used as input.
I assume the following but could not find anyware the answer :
SFCC1 gets speed from ADR1 , SFCC2 gets speed from ADR2
But what happens if just after takeoff ADR1 fails. Pilots can select source ADR3 to take over for there display but what about other systems in need of speed input.
I read also somewhere that SFCC1 is a blocking issue for takeoff as it gives input to landing gear logic. While SFCC2 isnt blocking in MEL.

Greetz Peter