Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by natcret

  1. Urs, Understood. Thank you very much for the explanation. Since this is solved may I recommend locking the topic. Great support as always!
  2. Again, I apologize for the delayed response (real life at work). I re-tested by assigning the keys back to their original settings and the issue returned. I also did another test by assigning new number keys (6,7,8,9,) to the Zoom Auto and User settings. Well, 1,2 3, and 0 now work, however 6,7,8, and 9 does not. Again, this is all using the keyboard. When I use the Keypad on the keyboard, all is well. Regards Nat
  3. As a follow up, I uninstalled and reinstalled the client. Unfortunately the issue still persists...however... On a whim, I went into settings and removed the default zoom key settings (D0, D1,D2,D3) and then tried again. Everything worked! So it seems, at least in my case, that there is a conflict between the default zoom keypress settings and the ability to enter the numbers to Adj CRUZ ALT using a keypress instead of the keypad. Regards.
  4. I tried the test editor. No issues..typed just fine. i have no other issues with any other add-ons or applications. I can live with using the keypad. I will try a reinstall, however, and see if it clears up. Thank you again! I will let you know what happens.
  5. I apologize for the long delay. I have checked through everything. All hardware disconnected, no applications running. Just the server and client and it flat refuses to accept keyboard entry of the numbers 1-3 and 0. And as stated earlier, when entering numbers using the numeric keypad instead, no issues at all.
  6. Thank you Lonewulf. Yes, I will probably continue to use the keypad, however, that does not address the issue. Maybe mine is an isolated case as no one else seems to have this issue.
  7. Thank you for the response. Nope, no changes to any of the shortcut settings. The Flight Plan Window is the Active Window (Black border around the window). I tried again this evening wiht nothing loaded simulator-related and I had the same issue. Steps I took: 1. Start the Server then the Client...no issues. 2. Clicked on FPL and loaded a Company Route. All ok. 3. The Flight Plan Window opens with the route legs shown. 4. I click on "Adj CRZ ALT" and I cannot type in the numbers 1, 2,3 or 0 using the top of the keyboard. However, I can enter the numbers using the numeric keypad. Again this is the strangest thing I have ever seen and I am no stranger to the flight sim word and add-ons. Just to make sure I cover all items, while flying, climbing to my cruise altitude and then clicking on "Adj CRZ ALT" via the RSB works as advertised (page 36 of the Flight Plan Doc). Regards
  8. It appears that there may be a bug related to adjusting the cruise altitude. If I try to use the normal keyboard numbers to adjust the altitude, I can only use numbers 4-9 as the numbers 1-3 try to zoom or reset the map display in the map window. Zero (0) works intermittently. However, If I use the keypad, everything works fine. Using FSX. Regards, Nat
  9. Big supporter since v1. Very happy with version 2. Geat work and well done! Nat
  10. Thanks guys. However, Navigraph Charts, both the current version and the current Cloud Beta that is being tested both show SIDS. So that seems odd why Navigraph would show that when the actual NATS AIS for UK does not.
  11. Ahh... I see. That is strange as the airport does have an actual SID.....hmmm Thank you for clarifying tho.
  12. Have come across a peculiar problem. When trying to use EGHI as the departure and access the SID, the runways screen is greyed out. The default runways in FSX are 02/20, EFB shows 02/20. Using Navigraph's cycle 1706, it shows EGHI as part of its SIDSTARS folder. When I set up EGHI as the arrival airport, I have access to all of the STARS for both runways. Any ideas? Regards, Todd
  13. Ahhh...that was it....AS soon as I hit moving map, it came up. Thanks!
  14. For some reason, the wind display is missing. The Wind Box on the screen where you can enable and disable the display is enabled on all screens, yet there is no display. I even toggled the box to make sure there was a yellow outline surrounding the box. This is very puzzling. Regards, Todd
  15. Hey guys.... Let's do one more check..... I went and checked the UK2000 website just to make sure there wasn't anything odd. If the default FSX scenery is working fine then it means that there is something within the UK2000 scenery that is not being recognized by EFD. Double check the following: 1. Shut down FSX, then start the EFB DataProvider. Under the Data menu, select the and run the Simulator Scenery Data Update. When done....then start the EFB DisplayUnit. Go to Settings/Miscellaneous/Reset Airport Data Cache 2. If this doesn't work again then the issue may be how the scenery itself is being read. If the EFB it is showing the runways using the default FSX scenery then EFB is working fine as well as Navigraph information. This would mean, however, that there may be something in the EGKK scenery that is causing a conflict. I can only guess.
  16. Is there anything still within your runway.txt file? Is the scenery working within FSX by itself?
  17. Dbuck, Did you open the EFB Dataprovider and then select the Simulator scenery data update from under the Data Menu which allows EFB to update its scenery database? Regards, Todd
  18. Brian, The runways for LEMG under P3D v3.1, unfortunately, do not reflect the real life runways that exist. P3D only has 14/32 which is now 13/31 and 12/30 was added a few years ago. If you are looking to have both runways, then you will need to download scenery that would add the addtional runway. Take a look at this post below for more info, however, keep in mind that the post was for FSX and may or may not work for P3D. http://aivlasoft.ipbhost.com/index.php?/topic/2147-what-i-have-learned-about-adding-runways-and-scenery/ Regards, Todd
  19. Scenery location should be: C:\ProgramData\Lockheed Martin\Prepar3D v3 Your Flight Plan folder should be under your Documents folder. Your Install folder should be however you set it up. For example, mine is C:\Prepar3D v3 Did you also check your navigation data folders and where they are pointing? Regards, Todd
  20. I recently purchased EFB and wanted to pass on some tips related to runways and scenery in FSX and EFB. I too was having problems with the whole runway.txt thing and getting EFB to recognize runways I had installed within FSX. I did review the Forum FAQ (Runways.txt / Runway identifiers are greyed out), the documentation within the runway.txt document itself, and scoured the forums. I was utimately able to figure out what the issue was and corrected it. So I thought i would share my discoveries. Most importantly, the examples I show follow the FAQ and text documentation, however, I hope my explanations help to provide a better understanding of those documents. I created a multi-leg flight from Indira Gandhi Intl (VIDP) to Abu Dhabi (OMAA) and then from Abu Dhabi to Cairo Intl (HECA) as part of a world tour. The default FSX runways for those airports are as follows: VIDP: 09/27 and 10/28; OMAA: 13/31; and HECA: 5L/23R, 5R/23L, 16/34 In real life, VIDP added runway 11/29; OMAA added 13L/31R and changed the existing 13/31 to 13R/31L; and HECA added a new 5R/23L and changed the old 5R/23L to 5C/23C. So, as you can guess, errors came up within the DataProvider as the new runways just did not exist. In the case of OMAA I had to add a line in the Runway.txt as follows: OMAA 13 13R OMAA 31 31L Basically, the designator of 13/31 in FSX has been changed to 13R/31L in real life. So by adding the two lines, it allowed the Display Unit to recognize 13R/31L at OOMA. Unfortunately, for the new runway (13L/31R), just as the instructions state, there was nothing I could do... unless I had scenery that matched the changes. I think this is the biggest question that I saw from scouring the forums: If I install scenery in FSX, will it recognize and be correct in EFB. The true answer is that it depends on how accurate the scenery is that you installed along with the what cycle navigation data that you may be using. So I did a test. I downloaded the three following scenery files. Be mindful of the dates: Cairo International - HECA - by Matthew Brooks and Ray Smith, May 2010 Abu Dhabi Intl Airport (OMAA) United Arab Emirates by Victor Nauta & Ray Smith, December 2014 Indira Gandhi Intl (VIDP) India by Craig Scott, June 2014 I installed the files into their correct locations under the FSX Addon Scenery folder. I then started FSX and added the scenery files via the FSX Addon Scenery dialog. I then made sure that the scenery updated and worked correctly in FSX (meaning that when I selected the airport in FSX I was able to select the new runways, etc...). When I was sure that it all worked, I shut down FSX and then started the EFB DataProvider. I then selected the Simulator scenery data update from under the Data Menu which allows EFB to update its scenery database. After about five minutes, everything finished. I then started the EFB DisplayUnit and reloaded the routes I had created. No error messages came up and all of the new runways were in place. Additionally, the taxiways and stand locations seemed to match what had been installed in FSX. The only thing I had to do was remove the OMAA modification I had placed in the Runway.txt file and then Reset the Airport Data Cache which is a button located under Display Unit/Settings/Miscellaneous. After reseting the data cache again and checking the airport, both 13L/31R and 13R/31L were in place. I tested this by taxiing from Terminal 3 at VIDP, which is close to the new runway 11/29, all the way over to runway 28. I then departed VIDP and landed runway 13L at OMAA and taxied to the terminal. The moving map was on for all phases and I also verified against Navigraph Charts (current cycle). The *only* issue I came across was at Cairo (HECA). Rwy 16/34 is a closed runway and per the FAQ, "if a runway in real world has been closed but is still available in FSX, you will no longer find navigation data for such a runway. In such a situation use the word "nil" for the third column, e.g.: ABCD 22L nil." I did that, however, I still saw runway 16 come up for departures. However, 16/34 did not come up for arrivals. Also, as a heads up, HECA has no SID/STARS within the Navigraph Charts DB (current cycle) and no SIDS or STARS were available in the Dataprovider (just in case you were wondering). So I know this is long-winded but the point to all this is that it appears that EFB will read installed runways, provided that: 1. The scenery itself has been designed to account for the real life additions and changes. 2. Your navigation databases are current or at least contain the real life changes. 3. The scenery has been installed correctly into FSX and is working correctly. This is very important. 4. If the scenery is working, then shut down FSX and start the EFD DataProvider and run the Simulator scenery data update. 5. Once complete, remove any modification you may have made to runways.txt first. 6. Start the EFB DisplayUnit. Go to Settings/Miscellaneous/Reset Airport Data Cache 7. Put in your flight or look up an the airport and see if you get errors, e.g., runway assignment warnings, If no errors then all is good. Start FSX. 8. If you do get errors, then retrace the steps I have tried to outline above. In some cases, you may have to add the specific changes to the Runway.txt file. I did have an initial problem, but when I retraced my steps, I discovered that I had not installed the scenery into FSX correctly. Once I did that, everything worked great. Now understand that this may not work for everyone because there are some many variables that could affect FSX scenery and EFB. Hopefully, as I stated above, this will help clarify some of the information. Lastly, my sincere thanks to all the folks at AivlaSoft for developing an excellent program that has been a great addition to my flight sim hobby. I would not have taken the time to write this if i did not feel the program was well worth it. Regards, Todd
  • Create New...