A320 FMGS B31

[jeehell]

no, did you try to close it and restart it manually?

[Stephan Schwarz]

Yes, I restarted both the server and client computers, started the ND.exe manually and deleted the ND.ini. In all cases this single window remains dark. It is started, no question. But just a dark spot on the screen ...

[jeehell]

The ND.exe is longer used. Search the EIS folder, there you'll find a shortcut to launch the ND (using the single EIS.exe as main executable).

JL

[OmniAtlas]

ben, from my experience with TOPCAT and ifdg 320 model (which is actually used by jl) when transferring fuel and payload figures to the sim topcat screws up something and if after loading with topcat u check the sim "fuel & payload" page u'll find an aircraft with a totally upset center of gravity totally out of range!
can u check this?
regards
fil

Fuel and weights are all in range. No problems with TOPCAT, I even tried different weights.

I have reinstalled FMGS -- same problems occur - the aircraft climbs very slowly. Above 10,000 alt it is unable to pick up speed <250 knkts.

I have run the updater and everything is current (A320FMGS_B32.2.exe is downloaded, do I have to run this also?).

I will try one last flight this time with default fuel without using TOPCAT.

I don't know what else is the problem.

[jeehell]

When you say you reinstalled the FMGS, which version was the base one?
Try download the B32.2 from here: http://www.jeehell.org/A320FMGS_B32.2.exe and do a full install from scratch (including controls etc, keep a backup of old install).

JL

[OmniAtlas]

When you say you reinstalled the FMGS, which version was the base one?
Try download the B32.2 from here: http://www.jeehell.org/A320FMGS_B32.2.exe and do a full install from scratch (including controls etc, keep a backup of old install).

JL

Using the one on the first page of this thread, and then updating. I will reinstall with A320FMGS 32.2.exe and retest

Note -- I am using P3D 2 .1 with the latest released hotpatch (this shouldn't affect FMGS).

[jeehell]

Also, default fuel is too much.
In FSX fuel and load planning, put 75% of fuel in wing tanks and 50% in center tank.
ALso, make sure ZFW is around 55t.

JL

[OmniAtlas]

Also, default fuel is too much.
In FSX fuel and load planning, put 75% of fuel in wing tanks and 50% in center tank.
ALso, make sure ZFW is around 55t.

JL

Reinstalled from new 32.2 and also used the auto-update.

Still unable to climb or exceed speeds past 250 knots using weights from TOPCAT. I will try again tonight with 75% wing tanks, 50% center tanks with ZFW around 55 tons.

[GlobalGentleman]

Reinstalled from new 32.2 and also used the auto-update.

Still unable to climb or exceed speeds past 250 knots using weights from TOPCAT. I will try again tonight with 75% wing tanks, 50% center tanks with ZFW around 55 tons.

FWIW, Omni you're not alone. I have also been experiencing problems with climb rate and sometimes the altimeter not advancing at all until I change the Baro ref to STD, then presto! then the altimeter reflects accurately....also, I have a very slight 100-200ft V/S bounce while in Cruise. This all seems to be happening only when I use the Topcat 'injection' method via network.

I have not tried adjusting weights in the fsx fuel/payload menu afterwards...this is purely Topcat data injection into the sim, finish all other necessary preparation, then fly. I have also not yet tried any different weights such as JL recommended above. I simply wanted to add some info which might help narrow down the issue....and it seems like Topcat might be at fault as it interacts?! fyi, my topcat a/c profile is the PM Airbus as ToTom had suggested a while back. I've been using that for about a month now.

Hope this can help in some small way.

~Alan

[OmniAtlas]

Hi Alan -- at least I know I'm not the only one going crazy!

I have tried loading the a/c with the recommended weights by JH -- no TOPCAT involved. A/C is still unable to climb, and only does so very slowly < 1000 after taking it out of TOGA/FLX -> CLB

Initial climb out is okay even with A/P involved.

What else could be the problem? I have a feeling it may be the .air or aircraft.cfg file, but everything seem to work perfectly before.