HI Jean Luc and at all ,
with last b61.9 and last AIRAC LIML airport is present on your database?
to see it, XXXX/LIML in FROM / TO init page
thanks for your quick response, I'm going crazy....
best regards
Gilles
LIML
-
- Posts: 86
- Joined: Fri Nov 04, 2022 5:36 pm
Re: LIML
thank's JL for this info,
Where do you think the problem could come from?
Gilles
Where do you think the problem could come from?
Gilles
-
- Posts: 86
- Joined: Fri Nov 04, 2022 5:36 pm
Re: LIML
I all , after make update at home (test machine) B61.9 and Navdata upon publication, LIML was in the Database.
few days after i want make this on the cockpit , LIML : scratchpad write NOT IN DATABASE.... i have bought a new scenery, test twice to regenerate the database ... same problem.
the day after i delete at home my database and re update this.... here no LIML
i suppose that navrecord.dat is corupted...
can I ask you to kindly to make this:
save the folder C:\Users\xxxxxx\AppData\Roaming\JeeHellWare, delete it
save the folder X:\A320FMGS/ Navdata, delete all .bin files
re-download the Nanigraph FMS Data Manager update (Jeehell A320 FMGS V2.1).
restart FMGS server stand alone with admin rights.
wait few minutes, see that your .bin files have been recreated, make a copy of these files on the PCs running ND and MCDU.
run your simulator and test LIML/LIML.
Thank's in advance for your help and information.
best regard
gilles
few days after i want make this on the cockpit , LIML : scratchpad write NOT IN DATABASE.... i have bought a new scenery, test twice to regenerate the database ... same problem.
the day after i delete at home my database and re update this.... here no LIML
i suppose that navrecord.dat is corupted...
can I ask you to kindly to make this:
save the folder C:\Users\xxxxxx\AppData\Roaming\JeeHellWare, delete it
save the folder X:\A320FMGS/ Navdata, delete all .bin files
re-download the Nanigraph FMS Data Manager update (Jeehell A320 FMGS V2.1).
restart FMGS server stand alone with admin rights.
wait few minutes, see that your .bin files have been recreated, make a copy of these files on the PCs running ND and MCDU.
run your simulator and test LIML/LIML.
Thank's in advance for your help and information.
best regard
gilles
Re: LIML
to be honest I doubt the file is corrupted, if you can see other airports then it is unlikely. Make sure you do not have issues like a space character added by mistake or else... Also post you fsscenery.cfg file.
Regards,
Jean Luc
Jean Luc
-
- Posts: 86
- Joined: Fri Nov 04, 2022 5:36 pm
Re: LIML
Hi ,Thanks JL for your feedback and comments.
Ok I want to hear your opinion, however it is a shame that other users cannot say whether or not they have the problem.
I called a user like me (JLA320) based in the north of France. He noticed me the same problem.... This problem is not blocking but just curious and maybe it will be resolved in a future update of navigraph. I am attaching the FSscenety.cfg. All the paths seem correct, my A320FMGS folder is D:\A320FMGS on all PCs.
[Scenery]
scenery.cfg=C:\ProgramData\Lockheed Martin\Prepar3D v4\scenery.cfg
FSfolder=D:\Prepar3D v4\
AerosoftPath=C:\Users\Utilisateur\AppData\Roaming\JeeHellWare
Add-ons.cfg=C:\Users\Utilisateur\AppData\Roaming\Lockheed Martin\Prepar3D v4\add-ons.cfg
Add-ons.cfg2=C:\ProgramData\Lockheed Martin\Prepar3D v4\add-ons.cfg
ip=127.0.0.1
here: logNDB.txt:
*22:44:16* Navdata module launched Server
*22:44:16*
*22:44:18*
*22:44:18* Navdata1:
*22:44:18* -ARPTliste:14415
*22:44:18* -Navaidliste:16209
*22:44:18* -FIXliste:241722
*22:44:18* -AWYsegments:105184
*22:44:18* -MarkerList:1046
*22:44:18* -Holds:28334
*22:44:18* -RWYS:36088
*22:44:18* -PPs:7369
*22:44:18*
*22:44:18* Navdata2:
*22:44:18* -ARPTliste:14425
*22:44:18* -Navaidliste:16232
*22:44:18* -FIXliste:241234
*22:44:18* -AWYsegments:105251
*22:44:18* -MarkerList:1049
*22:44:18* -Holds:28342
*22:44:18* -RWYS:36109
*22:44:18* -PPs:7338
*22:44:18*
*22:44:18* server started on port:8006
*22:44:18* Client connected: 127.0.0.1
*22:44:18* Client connected: 192.168.1.111
*22:44:24* Client connected: 192.168.1.116
Ok I want to hear your opinion, however it is a shame that other users cannot say whether or not they have the problem.
I called a user like me (JLA320) based in the north of France. He noticed me the same problem.... This problem is not blocking but just curious and maybe it will be resolved in a future update of navigraph. I am attaching the FSscenety.cfg. All the paths seem correct, my A320FMGS folder is D:\A320FMGS on all PCs.
[Scenery]
scenery.cfg=C:\ProgramData\Lockheed Martin\Prepar3D v4\scenery.cfg
FSfolder=D:\Prepar3D v4\
AerosoftPath=C:\Users\Utilisateur\AppData\Roaming\JeeHellWare
Add-ons.cfg=C:\Users\Utilisateur\AppData\Roaming\Lockheed Martin\Prepar3D v4\add-ons.cfg
Add-ons.cfg2=C:\ProgramData\Lockheed Martin\Prepar3D v4\add-ons.cfg
ip=127.0.0.1
here: logNDB.txt:
*22:44:16* Navdata module launched Server
*22:44:16*
*22:44:18*
*22:44:18* Navdata1:
*22:44:18* -ARPTliste:14415
*22:44:18* -Navaidliste:16209
*22:44:18* -FIXliste:241722
*22:44:18* -AWYsegments:105184
*22:44:18* -MarkerList:1046
*22:44:18* -Holds:28334
*22:44:18* -RWYS:36088
*22:44:18* -PPs:7369
*22:44:18*
*22:44:18* Navdata2:
*22:44:18* -ARPTliste:14425
*22:44:18* -Navaidliste:16232
*22:44:18* -FIXliste:241234
*22:44:18* -AWYsegments:105251
*22:44:18* -MarkerList:1049
*22:44:18* -Holds:28342
*22:44:18* -RWYS:36109
*22:44:18* -PPs:7338
*22:44:18*
*22:44:18* server started on port:8006
*22:44:18* Client connected: 127.0.0.1
*22:44:18* Client connected: 192.168.1.111
*22:44:24* Client connected: 192.168.1.116