Jump to content

ajcbakker

Members
  • Content Count

    26
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Alex, Many thanks for your fast reply. Good to hear it is a known problem and not a problem with my installation. I will try to play something with the update rates in the simulator connection as you suggested. I'll see if we can make some progress with this issue. Again, many thanks and kind regards, Alje Bakker
  2. Hi Alex, I am running LNM 2.4.4 in a networked environment and connected with Prepar3d v4.5 hotfix 2. Everything works great except the weather icons on the map and the METAR's in the "Airport" tab of the "Information" panel. When I select "Flight Simulator" in the "Airport Weather Source" menu no icons appear on the map and no METAR's from Prepar3d appear in the "Information" panel. When I select "NOAA" or "VATSIM" they appear immediately on the map. METAR's from "NOAA" and "VATSIM" always appear in the "Information" panel. For a correct understanding of this issue: the "Prepar3d" computer is connected via littlenavconnect with the "LNM" computer and also WideFS (WideServer on the "Prepar3d" computer and WideClient on the "LNM" computer) is running. This is specially strange because a few weeks ago it worked fine. That was after the first start of LNM 2.4.4. When I started LNM for a second time it did not worked anymore. Do you have any idea what could be the cause of this? Many thanks and kind regards, Alje Bakker
  3. Hi Alex, Thanks for your reaction. I will follow your suggestion to share the AS directory and then point the AS weather path in LNM to this share. Many thanks again. Kind regards, Alje Bakker
  4. Hi Alex, I have read the thread and did some testing. However this is not the solution in my situation. On the "Prepar3D" computer I am using Active Sky. When I select "Active Sky" on the connected "LNM" computer nothing shows up. Only when i select "NOAA" or "VATSIM" the icons appear. As I told you before both computers are connected with eachother by littlenavconnect. Do you have any clue about this issue? Thanks and kind regards, Alje Bakker
  5. Hi Alex, Thanks for your answer. I will read that thread and will do some more testing. I will keep you informed about the results. Kind regards, Alje Bakker
  6. Hi Alex, I am running LNM 2.2.3 in a networked environment and connected with Prepar3d v4.4. Everything works great except the weather icons on the map. When I select "Flight Simulator" in the "Airport Weather Source" menu no icons appear. When I select "NOAA" or "VATSIM" they appear immediately. For a correct understanding of this issue: the "Prepar3d" computer is connected via littlenavconnect with the "LNM" computer. Do you have any idea what could be the cause of this? Many thanks and kind regards, Alje Bakker
  7. Hi guys, Many thanks for all your responses. We will continue to perform RNAV approaches with the 777 and take into account the remarks you have made downscc. Hopefully things are going smoother and no level off anymore at DA(H) or MDA(H). At ph-cxz: our fma displays spd. We keep you posted with the results. Kind regards, Alje Bakker
  8. Dear sir/madam, After a long period of performing ILS approaches we started recently to perform RNAV approaches with the PMDG 777. A/T, FD, LNAV and VNAV on. However we encountered some problems here. Every time when we reach the MDA the A/T will increase throttle so the descent has to be aborted because the plane does not descend anymore. We use a throttle quadrant but at that moment the levers are on idle. Surely we do something wrong but we can not figure it out at this moment. Can someone help us with this? Many thanks in advance. Kind regards, Alje Bakker
  9. Hi Alex, Many thanks for your response and your intention to add exclusion of single files in LNM. I love the program very much. Many thanks again. Kind regards, Alje Bakker
  10. Hi Alex, Thanks again. In the case of the Bonaire scenery however it is not necessary to exclude a single file because this directory contains only one bgl-file (the flatten file AFX_TNCX.bgl). So exclusion at directory level is sufficient in this case. I can imagine that there could been situations in which it is necessary to exclude single files. Therefore I really appreciate your intention to add exclusion of single files in LNM but seriously hope you will not remove the current functionality of exclusion of directories in LNM. Kind regards, Alje Bakker
  11. Hi Alex, Many thanks for your reply. I really appreciate your help and investigation on this issue. I understand your statement that you cannot do much about it. So I decide to continue to exclude this layer from loading into the LNM database. Or do you have other alternatives?. Kind regards, Alje Bakker
  12. Hi Alex, Thanks for your reply. I will send you that flatten file as soon as possible. Kind regards, Alje
  13. Hi Alex, After further investigation I detected the cause of this problem. The problem was the scenery layer "Bonaire_Alfa" which contains an AFX_TNCX.bgl file (that is a so called "flatten" file for TNCB). I have excluded this layer from loading into the LNM database and everything is fine now. Kind regards, Alje Bakker
  14. Hi Alex, Many thanks for your help and advice. I will perform a further investigation as you proposed. I will keep you informed. Thanks again. Kind regards, Alje Bakker
  15. Hi Alex, Thanks for your reply and all your help. I really appreciate that. As you probably know the scenery of Bonaire (from Aerosoft) contains two layers in the scenery.cfg. There is "Bonaire_Bravo" which contains the AFX_TNCB.bgl file. Above these layer there is the "Bonaire_Alfa" which contains an AFX_TNCX.bgl file (that is a so called "flatten" file for TNCB. The Alfa layer has a lower priority number in the scenery.cfg as the Bravo layer and therefore this Alfa layer has a higher layer number (higher priority) and will be read over the Bravo layer. Could it be possible that this has something to do with this issue? Kind regards, Alje Bakker
×
×
  • Create New...