A320 FMGS B38

Okay, I've tried to get B38.3 working again but with a fifth Win7 PC only for the MCDU to reduce CPU load on the PFD/ND PC.
Started as administrator, power on, system okay (still without the non-function buttons CSTR, WPT etc), APU started, IRS aligned, MCDU programmed, taxied to RWY and took off, 7 minutes fun in the skies......... then no reaction on the PFD/ND any more! Flight cancelled mid-air! :roll:
Now I have only the PFD and ND software on a clean and powerful computer, a fast and stable network but the disconnections still appear. What has changed to the previous version? I'll not make any tests with 38.3 any more and will drive 37 until a new one is out. Takes too much time to spin around.

Best regards,
Bon

@Mike,
The old download link doesn't work any more. I have the old B37 exe on an usb stick but it's not here at home. Have to look for it on Monday.

Hi Bon,
that would be cool if I could have the B37.
Many thanks in advanced!

Would be nice if JH could find the problem
It's such a nice and good software!
If any help is required please let me know!!

Hi,

The latest version is out.
http://jeehell.org/A320FMGS_B38.4.exe

I have no idea what may cause the network issues. Lots of people dont have those, so I can only guess something is wrong with the setups of those who have that issue. It could be a lot of different things:
- Anti virus
- admin rights
- router issues
- firewall issues
- port conflict with other software
- various things I will never think of...


(this might be a key linked to the error 10053 one of you had:
http://www.altn.com/Support/FAQ/FAQR...mber=KBA-01510
http://support.microsoft.com/kb/204594
)

Regards,
JL

JL,
once again thank you for your hard work, we appreciate that very much!
You are our hero! I will test 38.4 asap.
I wish you and all other guys here a nice weekend!

Bon

I don't have any issues with connectivity..but then again I am just running from one computer at the moment.

Test flight with 38.4 and everything is ok, even the autolanding (it was sluggish before due to scenery complexity turn to max, decreasing this allowed FMGS to sync with the aircraft).

Thanks again JL, we know you are only a one man team.

Dear JL,
I just would like to thank you for your hard work....

Quote:

---

Originally Posted by jeehell

Stefan, the files are created by the FMGS Server in C:\A320FMGS\Navdata (default installation folder).

JL

---

Hi JL

thank you for your quick response and for that great software which brings my sim alive. I found out and now it is working.

Regards
Stefan

For all those having black screens with latest update:
It seems the updater missed the auto update for 38.4....

Try installing that one :
http://www.jeehell.org/A320FMGS_B38.4.exe
then do the auto update...

JL

Hi all,

JH thanks for the new version I've tried now but I still have no NDB, VOR APRT or WPT on the remote PC's
I've tried serveral WIN 7 64B pc's and all have the same issue. If I start the ND on the FSX computer where the
server is running I can see all the NDB, VOR APRT and WPT...

The actions I did:


removed the anti virus software
turned off the fire wall
disconnected the router

but no luck....

I'Ve tried the default port configuration and I saw a error on Port 8005

**12:3:42.720**port 8005:192.168.0.163 connected
**12:3:42.720** fmaps send timeout.
**12:3:55.125**port 8005:192.168.0.167 connected
**12:3:55.125** fmaps send timeout.

after this I've changed the ports to

9610, 9613, 9621 and 9622 because they should be free accoding to the internet steatments

I did start everything but still the same issue no NDB, VOR APRT or WPT.

Here my error logs:

*****WideFMGSserver started at:13:55:48.156
**14:1:35.802** port 9610:192.168.0.167 connected
**14:1:35.803** port 9613:192.168.0.167 connected
**14:1:35.803** port 9621:192.168.0.167 connected
**14:2:44.755** port 9610:192.168.0.163 connected
**14:2:44.755** fmaps send timeout.
**14:2:44.756** port 9613:192.168.0.163 connected
**14:2:44.756** port 9621:192.168.0.163 connected

First CLient PC

*****WideFMGS client started at:14:1:29.142
Create result:1
Host IP: 192.168.0.10
**14:1:30.534** Port 9622: connected
**14:1:33.576** Port 9621: connected
**14:1:33.576** Port 9610: connected
**14:1:33.576** Port 9613: connected

Second Client PC

*****WideFMGS client started at:14:4:3.338
Create result:1
Host IP: 192.168.0.10
**14:4:4.648** Port 9622: connected
**14:4:7.487** Port 9621: connected
**14:4:7.690** Port 9610: connected
**14:4:7.690** Port 9613: connected

ANd NAV Data Log




*13:55:49* Navdata module launched Server
*13:55:49*
*13:55:51*
*13:55:51* Navdata1:
*13:55:51* -ARPTliste:15372
*13:55:51* -NavaidListe:18180
*13:55:51* -FIXliste:186502
*13:55:51* -AWYsegments:97710
*13:55:51* -MarkerList:2505
*13:55:51*
*13:55:51* Navdata2:
*13:55:51* -ARPTliste:15372
*13:55:51* -NavaidListe:18180
*13:55:51* -FIXliste:186502
*13:55:51* -AWYsegments:97710
*13:55:51* -MarkerList:2505
*13:55:51*
*13:55:51* server started on port:9622
*14:01:32* Client connected: 192.168.0.167
*14:01:34* Client connected: 192.168.0.167
*14:02:41* Client connected: 192.168.0.163
*14:02:43* Client connected: 192.168.0.163
*14:02:43* Client connected: 192.168.0.163

Can someone help me with this? What do I wrong here?

Many thanks in advanced!

Mike

forgot the say that the rest is working absolutely perfect!


Maybe something is wrong on the remote pc's FSscenery.cfg

that's the content:

[Scenery]
scenery.cfg=C:\ProgramData\Microsoft\FSX\scenery.cfg
FSfolder=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X
AerosoftPath=C:\Users\STH\AppData\Roaming\JeeHellWare
ip=192.168.0.10

and the log says:

*14:01:29* Navdata module launched WideFMGS
*14:01:29* NavDB files not found!

Maybe here is the problem?

Thank's again ;)