A320 FMGS B31

[jeehell]

Hi,

I think you messed up the installation completely after updating probably from an older version. I do not know exactly. The software DOES work.
You can try to uninstall the software completely. Then start again from B31.2 package and update to latest versions.
Remember to ONLY install what you need (DO NOT install SERVER on clients!!!).

Tomorrow I will try to make a new release with all the latest files. You'll have to uninstall everything then install that new version if it still does not work by then.

JL

[Space]

Hmm, i did all the autoupdate on Server and 3 Clients. I did not install a Server on Clients. and i install only that modules i Need. And i changed the ports in Network Connection, all 1 up. Is it righ that the 66MB navdata file is only needed on Server in Navdata 1 & 2 Folder and NOT on the Clients running CS ND and FO ND?

[jeehell]

Yes navdata is required only on Server PC.

Why did you change the ports? do you use those for another application? You're sure you set the ports correctly on all computers?

What does not work exactly on the NDs?
What is your computer distribution?

JL

[Space]

I Heard from Problems with the default Ports some versions before, so i did change them since them. I will Check again the Ports, but if wrong, the network won't rund at all, wouldn't it? i use the whole setup only for FSX.
The Route is not displayed, but airbus is following it. Also waypoints, ndb etc are not displayed.
Pc is a 3ghz dualcore with 4gb RAM and 256mb grafic. At Version b30 all was Fine and i had no Problems, than the non displayed Route fault Starts, i droped here a Thread and you answered that you will no longer Support the old one.

[janinp]

Hi JH,
Still not resolved the display of the wpt vor ndb arpt on client ND. IP is ok. Log on navdata folder on the Server pc is :
RootPath=D:\A320FMGS\Navdata\
Thread1 launched
-BGL scan:
-ScenerycfgPath:C:\ProgramData\Microsoft\FSX\scenery.cfg
-FSroot:\FSX\
-Folders Nb:208
Thread2 launched
Server init OK
-FS ILS Nb:5

NavDB1 done:
-ARPTliste:14484
-NavaidListe:18236
-FIXliste:177692
-AWYsegments:94492

NavDB2 done:
-ARPTliste:14484
-NavaidListe:18236
-FIXliste:177692
-AWYsegments:94492

1179834: connected
1179834: error
1179834: disconnected
393316: connected
393316: error
393316: disconnected
458852: connected

does this ring any bell ?


Pierre

[jeehell]

@Space: to test if the issue is on your network, did you try to run the ND on the server computer?

@Janinp: you do not have the latest update, please update.

JL

[buentead]

I have an MCDU question: I do have two MCDU's from FlightDeckSolutions configured to work with ProjectMagenta. Hence, some of the key assignments are not the same as with FMGS MCDU.

Is there a possibility to assign different keys inside FMGS MCDU, e.g. instead of Shift-F1 like Ctrl-F1?

Adrian

[jeehell]

If you use FDS MCDUs, you must use the dedicated hardware module you'll find in my package. I won't support any method with FDS interfaceIT MCS software or else.

Regards,
JL

[OmniAtlas]

I don't have a subscription to Aerosoft NavDataPro -- is there a way we can use a trial version or an alternative substitute?

[jeehell]

Hello,

For now there is no alternative. Navigraph will maybe add support, but they still haven't decided yet.

JL