Black spaces
Samamax opened this issue · comments
Hi,
even though I have updated AIRAC, *openflightmap the map image disappears and it remain black spaces. Why? Thanks and good day.
T
The map cache needs to be cleared in order for the new map tiles to be loaded. You can do this in LittleNavmap directly or remove the cached files manually.
In LittleNavmap:
Go to: Tools -> Options -> Cache and Files, then click on "Clear Disk Cache".
Manually:
Remove all contents in the following dir and restart LittleNavmap:
%localappdata%\.marble\data\maps\earth\openflightmaps
Hi,
similar problem here: AIRAC Cycle 2203 rev.1, latest LNM, latest LNMOFMTheme, all installed according to instructions. Only black maps where they shouldn't (e.g. around EDDS, as shown in the screenshot)
@rippy65 please report if you have you done what @AmbitiousPilots suggested.
@rippy65 please report if you have you done what @AmbitiousPilots suggested.
sure. Cache cleared before that screenshot.
Works fine here (LittleNavmap v2.6.18, LittleNavmapOFMTheme v1.0.14):
Works fine here (LittleNavmap v2.6.18, LittleNavmapOFMTheme v1.0.14):
Glaubischo :) ...I've setup OFMTheme on 3 different boxes - always and everywhere black...I must be doing something wrong - but what? Are there any win11 firewall exceptions necessary?
Yes, when the cache is cleared and it's still not loading the map tiles it might indeed be a firewall blocking the traffic. Make sure to allow network access for LittleNavmap. The map tiles are loaded from the following domain, so try to white list it when possible:
https://nwy-tiles-api.prod.newaydata.com
Thx - I'll try that shortly. Meanwhile I tried an LNM/OFMtheme install on another laptop (I have a lot here... ;) ) - and there OFM showed up "out of the box")...will have to check the different install processes for 100% consistency.
I'll report here ASAP.
The map cache needs to be cleared in order for the new map tiles to be loaded. You can do this in LittleNavmap directly or remove the cached files manually.
In LittleNavmap: Go to: Tools -> Options -> Cache and Files, then click on "Clear Disk Cache".
Manually: Remove all contents in the following dir and restart LittleNavmap:
%localappdata%\.marble\data\maps\earth\openflightmaps
I cleared the cache from the disk and disabled antivirus and firewall. I'm sorry the problem remains
I'd recommend to clear the cache manually from the disk. The clear cache command in LNM uses the Marble widget function which takes some time running in the background.
Clearing manually (close LNM before) also allows you to keep other cached map files like OpenStreetMap.
I'd recommend to clear the cache manually from the disk. The clear cache command in LNM uses the Marble widget function which takes some time running in the background.
Clearing manually (close LNM before) also allows you to keep other cached map files like OpenStreetMap.
I tried, I cleared manually and it didn't work.
Thx - I'll try that shortly. Meanwhile I tried an LNM/OFMtheme install on another laptop (I have a lot here... ;) ) - and there OFM showed up "out of the box")...will have to check the different install processes for 100% consistency.
I'll report here ASAP.
Ok...I have OFMTheme now up and running (=showing) on the FS Computer aswell as on different networked machines.
On all FAILED setups there was a coincidence: I had LNM installed in my /username/documents folder, which was synced by MS OneDrive over the internet with all my boxes inside my private network.
So I had an idea: Maybe the fact that OneDrive syncs my /documents folder gave issues... anyway : I deleted all LNM folders (also Username/AppData/Local/.marble AND Username/Appdata/Roaming/ABarthel) and did a fresh LNM install inside a new dir D:/FSData (which is not synced by OneDrive). Voila... - THAT worked. OFMTheme (aswell as all others...) is showing up perfectly.
Phew. ;)
Thanks to all who tried to help!
I'd recommend to clear the cache manually from the disk. The clear cache command in LNM uses the Marble widget function which takes some time running in the background.
Clearing manually (close LNM before) also allows you to keep other cached map files like OpenStreetMap.I tried, I cleared manually and it didn't work.
Isn't there another solution? The black spaces remained!
I'd recommend to clear the cache manually from the disk. The clear cache command in LNM uses the Marble widget function which takes some time running in the background.
Clearing manually (close LNM before) also allows you to keep other cached map files like OpenStreetMap.I tried, I cleared manually and it didn't work.
Isn't there another solution? The black spaces remained!
To clear the cache in .maple isn't the solution. How to do?
I have the same issue the map keeps dark.
Problem back here also - on two different networked boxes...As I didn't change anything on them since I solved the "black maps" issue on April 14th, I suspect it has something to do with a code change from MS/Asobo (latest mandatory update - > "TG Maverick"). This update fixed another bug on my MSFS setups - exe.xml not loading - but presumably broke the through littlenavconnect perfectly working OFM . Or anything has changed on the OFM server side...? Any clues, anyone?
Ok, i took a look at this again. Seems the problem was only with the base-tiles (OFM is dual-layered, "base" and "aero" map). So i deleted the cached base-tiles, in my case located in C:\Users\andre\AppData\Local.marble\data\maps\earth\openflightmaps
i kept the aero Folder in there because aero-tiles are not affected by this issue.
When i start LNM again all tiles are loaded correctly. Maybe rendering of the 2205 base tiles look longer than usual this time. But now it look like everything is available.
So clear you caches manually (while LNM is not running) and try again.
(@rippy65 , MS/Asobo Updates do now affect this map as this i completely independent)
Mhmmmm...I know it sounds like a dumb excuse, but: I didn't change anything on the networked boxes where lnm with ofm is running - but OFM just doesn't work anymore. Well, ATM I'm flying without them. No big problem.
Ok, sometimes i noticed that something could be wrong in the LNM config/profile that leads to strange behaviour. So i suggest to make a backup and then delete the folder C:\Users\andre\AppData\Roaming\ABarthel (yours will be "%appdata%\ABarthel"), and then try again with a fresh config.
@AndreGeddert: Didn't help. My boxes are backupped on a daily basis - and 8 days ago (the last time I fired up MSFS) LNM with OFM was working fine. So I restored that Macrium-BU, but...black maps.
It must be something other.
But ATM I won't track the issue (again...) further down, because I don't have the time due to RL workload - and LNM is principally working fine both on the MSFS rig aswell as on networked machines.
It's just OFM which won't work - and given the circumstances I can live with that. In 2 years I'm flightsimming for 40 years: In this time I learned that something is always broken, and most likely that "something" will work again...sometimes, somewhere 😎😉.
Anyway, thanks for your kind try to help!
Anyway, thanks for your kind try to help!
Problem solution: I edited openflightmaps.dgml to reflect the current airac cycle. Now all is fine again. See https://forums.flightsimulator.com/t/vfr-map-for-little-navmap/317879/91?u=mager1965
This is fixed in #19 and the upstream. Maybe you should include a link to https://github.com/AmbitiousPilots/LittleNavmapOFMTheme/archive/refs/heads/main.zip instead of individual releases. I ran into the same issue and downloaded an old release.
Same here, but with editing the AIRAC cycle, I coud it get back to work.
Two times change the query to:
query=“path=2208/base/latest”
Seems like there is a problem with OpenFlightMaps with all AIRAC cycles right now.
I found out when I tried updating to cycle 2209 and found out, that even after clearing the cache in LNMP the tiles remained black. The live map on their website shows black too. Is anyone else experiencing this too?
(https://www.openflightmaps.org/eh-netherlands/)
Seems like there is a problem with OpenFlightMaps with all AIRAC cycles right now. I found out when I tried updating to cycle 2209 and found out, that even after clearing the cache in LNMP the tiles remained black. The live map on their website shows black too. Is anyone else experiencing this too? (https://www.openflightmaps.org/eh-netherlands/)
Well, if you AIRAC matches, you don't have problems.
> > Seems like there is a problem with OpenFlightMaps with all AIRAC cycles right now. I found out when I tried updating to cycle 2209 and found out, that even after clearing the cache in LNMP the tiles remained black. The live map on their website shows black too. Is anyone else experiencing this too? (https://www.openflightmaps.org/eh-netherlands/)
Well, if you AIRAC matches, you don't have problems.
Nope. As I have mentioned, even the website itself doesn’t show the map tiles for me anymore, regardless of the selected AIRAC in the top right. I don’t think this is user error with littlenavmap, the file or the cache.
see attached screenshot of the website (pc/cellphone wifi/4G doesn’t make a difference)
I am using #20 (.../latest/) and that works fine for me.
You might have to clear caches (Options -> Cache) to be able to test properly.
@AmbitiousPilots does anything speaks again merging #20 ?
Hello all. I'm having the issue as well. I tried passing the whole URL path on a browser and it gives black tiles (only the JPG for the base), so I guess the issue is server-sided and really needs to be troubleshot. Hope someone would find a fix ASAP :-(
@doitagainstudio Have you applied https://github.com/AmbitiousPilots/LittleNavmapOFMTheme/pull/20/files? That works well for me since months now.
Hello all. I'm having the issue as well. I tried passing the whole URL path on a browser and it gives black tiles (only the JPG for the base), so I guess the issue is server-sided and really needs to be troubleshot. Hope someone would find a fix ASAP :-(
Yeah, It has been mentioned. Applying the changes in merge #20 did the trick for me.
@Samamax this is not related to the nav data from Navigraph.
If you have applied the changes from #18 (comment) and have still issues, please attach a screenshot.
Here is an example of how it should look like:
The black area is Great Britain where no openflightmaps data is available.