You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using version 2.7.8 develop I've run into a problem that I do not know how to solve or really explain.
I was turning on and off features displayed on the map, things like airports, VOR stations, ndb stations, and finally waypoints. I do not know what order or how this happened but waypoints show up on about the bottom 1/3 of my map regardless of whether I have Show waypoints turned on or off. I can move the map around and the bottom 1/3 waypoints will redraw themselves on the map.
I have quit out of Little Navmap and restarted it and the problem returned immediately.
Here are two screenshots of the situation.
.
I am not sure if this is a bug in 2.7.8 develop or a user error. Let me know if there is any other information you'd like from me or for me to try to clear this up.
The text was updated successfully, but these errors were encountered:
What's happening here: LNM limits the number of shown objects to avoid freezing. This happens too early here. Normally an indication of this overflow is shown too in the status bar but is missing.
Using version
2.7.8 develop
I've run into a problem that I do not know how to solve or really explain.I was turning on and off features displayed on the map, things like airports, VOR stations, ndb stations, and finally waypoints. I do not know what order or how this happened but waypoints show up on about the bottom 1/3 of my map regardless of whether I have Show waypoints turned on or off. I can move the map around and the bottom 1/3 waypoints will redraw themselves on the map.
I have quit out of Little Navmap and restarted it and the problem returned immediately.
Here are two screenshots of the situation.
.
I am not sure if this is a bug in 2.7.8 develop or a user error. Let me know if there is any other information you'd like from me or for me to try to clear this up.
The text was updated successfully, but these errors were encountered: