Bina

Hi Maurice, Indeed, that's how the maps are designed by the publisher (FAA) to work. The maps you mentioned are free, publicly available and cover the US territory only. AFAIK, sectional charts of other countries are payware. Your best bet is to use topographical maps (1:50000), which can be found online for different countries. If you know which tile server they use, you can add them to LNM easily using the procedure described here: https://albar965.gitbooks.io/little-navmap-user-manual/content/en/MAPTHEMES.html As to greyed out areas, I still need to explore the capabilities of Marble to see whether it's possible to blend two or more map/texture layers. I've experimented with this before publishing the map themes but didn't find the result satisfactory. Hope it helps!

Captains, I don't know if you have been using them already, but I have made a bunch of new maps for LNM, which make some widely popular map and chart data accessible from LNM. I think you'll find them useful too. To install the maps, download and unzip the file, then copy and paste the folder data found inside it to the location where you have your copy of LNM installed. Say yes to overwrite, when asked. You'll find my maps in a drop-down list of available maps, below all other ones and marked Custom, as shown on the image below. Maps included: Google Maps (Default) Google Maps (Satellite) Google Maps (Terrain) U.S. VFR Sectionals U.S. IFR Enroute Low U.S. IFR Enroute High U.S. IFR Area Charts U.S. Terminal Area Charts (TAC) U.S. Helicopter Route Charts Disclaimer: All map data is provided free of charge and publicly accessible. Enjoy!

Russell, I think what Alex suggests (and has programmed so far) works well, although what you think of as a problem actually is not. I guess LNM recognises any airport not included in default sim scenery files / folders as addon airports (Alex knows the best). In other words, I think what you see on the map and consider as not addon airport (e.g., such as AEC airports installed by Orbx Global Vector) in fact is an addon airport for LNM, or as Scott said above, any AEC "triggers a false positive". What you can do in this case is to first filter addon airports using the tip I described in my previous post, then select the filtered addon airports to make them visible (yellow circles on the map). Like I did for my Norway addon airports. I know, it's still a PITA, as clicking on any of them will deselect all, but as long as you keep the filter with wildcards in the scenery search box and/or until Alex comes up with a better solution (such as using RegEx in the scenery search box to filter out Orbx Global Vector airports), this might help.

It's already there... This tip from LNM online manual may come in handy. Scroll a little bit down looking for the tip title "Search for Add-On Airports" and check the image below. In a nutshell, for example, I have all my addons installed in a single folder "FSX root folder/MyAddons". So, I just enter *MyAddons* (the title of my addons folder with asterisks) into the relevant LNM search box called Scenery Path and have all my addon airports listed similar to the one shown on the image.

Before Alex replies, just my 2c... You can change the radius of range rings under Options -> Map -> Range ring radii for red range rings (nm) Hope this helps!

Thank you, guys! That's very helpful indeed. I'll keep in touch if I have more questions, if you don't mind... :)

Hello there, I'm not using X-Plane yet, so I cannot test it on my rig for the app that I'm working on now. But can you guys please explain: 1. Is there a default flight plans location in X-Plane (like a single folder for FSX flight plans in C:\Users\{username}\Documents\Flight Simulator X Files)? 2. I've read somewhere that X-Plane can store flight plans made with FMC in aircraft-specific folders. Is this true? If so, it means that the possibilities are endless depending on different aircraft equipped with FMC. In this case default location will be enough to know for now. Thank you!

Indeed, I have a relatively old rig with Win7 64-bit and FSXA onboard but I didn't expect that aircraft development has advanced so much... It's not my intention to set up a discussion here comparing your work with the aircraft of other well-known developers out there but hey, 7-8 FPS just on the first launch at an empty Texan airport just to test the birdie (no 3rd party objects, traffic, real-time weather etc.) means just no way for the Beaver for me... Alas! :( Even the aircraft with complex systems and VC coupled with 3rd-party addon sceneries and real-time weather that I often fly in FSX are not as resource hungry as the Beaver... And given the age of my machine, my normal FPS indicator rarely drops below 28-29 FPS which is quite OK for me. My specs in case anyone is interested: ASUS Rampage II Gene -|- Intel Core i7 920 @ 3.0GHz -|- HP 23" LED Display -|- NVIDIA Geforce GTX285 @ 1.0Gb -|- Creative SB X-Fi Gamer -|- 8.0Gb OCZ DDR3 RAM -|- Western Digital WD10EADS 1.0Tb HDD @ 7,200rpm -|- Seagate Barracuda 2Tb xHDD @ 7,200rpm -|- Windows 7 SP1 x64 Ultimate -|- FSX Acceleration -|- Saitek X52 Pro -|- TrackIR 5 Pro Anyone with the same problem? Any advice except "change your rig" (I know that anyway but am not ready to do this now)? Thanks!

Yet another video explaining the start-up procedure from a real Russian pilot (Aviabars Flying School). I've added captions in English. Enjoy!

Thank you, Alex! Not necessary anymore :) After some trial and error, it worked... finally! That's what I did, in case somebody has a similar issue: 1. Restarted my wifi-router and the "flying" computer. Took a note of a new IP from the Network and Sharing Center (Windows 7). 2. Launched FSX on "flying" computer. 3. Launched NavConnect on the same computer. Double checked that the IP I have and the one shown in NavConnect window is the same and one. 4. Launched LittleNavmap on the remote computer; then Main Menu -> Tools -> Flight Simulator Connection and selected options as described in the manual. 5. Inserted new IP address into Flight Simulator Connection of LN launched on the remote computer. That's it! Thanks again for your great assistance and LN, of course!!! Please keep it up!

That's correct! After installing LN on both flying and remote computers and after LN completed the database creation on flying computer, I just moved the folder C:\Users\...\AppData\Roaming\ABarthel\little_navmap_db to the remote computer replacing the 'empty' SQLite files. I also checked that LN on remote computer correctly reads database files, i.e. shows airports/navaids, etc. Yes. And inserted IP address of the local computer leaving port number (51968) untouched. It is. Actually, with LN running on both computers, I laucnhed NavConnect on the local (flying) one to make sure that IP address inserted in Main Menu -> Tools -> Flight Simulator Connection of the remote one is correct. Basically following your instructions here. Also, I added littlenavconnect.exe and littlenavmap.exe on both computers to the firewall exception list of my antivirus. I don't remember the error message but it was number (7) I guess. But I can check if you still need it. The other thing is LN on remote is trying to connect to the local one using NavConnect for XPlane. I guess it's because I don't have any sim on the remote and NavConnect is instructed to use XP as default option for the sim. Thanks for trying to help!!!

Hi Alex, Sorry if this has been asked before but is it somehow possible to run LN on a separate computer using it as a 'moving map'? If yes, how can I achieve that? My FSX is running on a desktop computer while I suppose I can run LN as a moving map through a Wi-Fi connection / Simconnect to desktop? EDIT: I try the procedure as explained in the manual to no avail yet. Is it required to have the same simulator (FSX) on BOTH computers - local and remote? The thing is I don't have FSX on a remote computer, only the database files taken from the local one (with FSX). But the NavConnect message on remote comp says it's trying to connect to XPlane (?) by default although IP address is provided correctly. Thanks!

Hi Alex, Indeed, they both show up in LN but I'm not sure about FSX, need to check. But after reading your reply and Jon's (ADE developer) explanation on duplicate navaids, I'm more than convinced that there is no other way in FSX to modify this behavior... until I shift to P3D and get advantage of their new Exclude Property. Further investigation revealed that the scenery developers do not necessarily need to include navaids such as VORs and NDBs into their AFCAD files (my case) unless these navaids are wrongly positioned or have updated frequencies since the release of FSX. Or the last resort is to modify stock airport files or delete the duplicate navaid from the addon scenery. Period. Thanks!

Bingo! Thank you, Alex! It worked OK after I installed the pre-release version above without excluding scenery folders.

I have exactly the same problem but using LNv144 on FSXA. It's never happened with previous versions of LN and with the same scenery addons. Sorry I can't send you my log file as I don't know where it's located on my rig but can do that later, if required. So far I've tried to reduce the number of chars in folder names but it didn't help. But then I reverted the scenery folder name back since I had the same folder name with previous version of LN, so I don't think this is a problem associated with long folder names. Here is the pic with error message: