Sounds like you have problems other than the VFR map.
I think the concensus still is that if you don’t open the map, or open it at the start and never close it (only minimise it), this fault will not occur. This is certainly my experience.
Sounds like you have problems other than the VFR map.
I think the concensus still is that if you don’t open the map, or open it at the start and never close it (only minimise it), this fault will not occur. This is certainly my experience.
Yea… I’d have to agree with you on that. So far, when I read the posts about the software being “unusable” I’ve been thankful my experience has been (mostly) very positive.
Last night was the first time the program has ever simply vanished as though it had never been running. It was quite odd.
I’ll keep plugging away, changing just one thing at a time to see what happens.
i’ve never had the VFR map issue, but then again, i don’t do multiplayer…
tonight, i had my first CTD not caused by impatience and using Alt-F4 while working on modding something that needs to reload the sim…
so, the CTD was caused by having multiplayer aircraft. For fun, I decided to set my multiplayer aircraft option on the flight settings page from offline to all players. When I loaded up the game and once out of 3-4hrs of sitting at KMCO tarmac testing things with people flying all about me, I had the inclination to open the VFR map to see exactly where people were distance wise to me. BOOM CTD!!!
just for fun, I reloaded, used offline mode, loaded VFR map and no issue. Back to main menu, all players again, loaded flight, opened vfr map, boom CTD…
Wow… that’s great info!
FWIW I have set the VFR map to not open at startup, and never open it. I use Little Navmap, which is so far superior that - once you use it - you could never be satisfied with the built in VFR map again.
I have it set to open on flight start, and I don’t think any of my CTD’s have been related to the VFR map. I just had another crash after passing Mt. Fuji in the Japan tour like a lot of other people but it was unrelated as far as I can tell.
Interestingly after three CTD’s yeaterday - I noticed that FS was taking way more memory that it should’ve. I upped my RAM from 16 to 48 Gb and re-tested - with the map open FS was taking 39Gb of RAM - ouch. With it closed that dropped to 6Gb. Looks like a major memory leak with the map functionality - which would certainly be enough to cause CTD.
That is odd.
I’ve had 48GB all the way through alpha, til now, and never had beyond 22GB being used.
I have replaced mine with this:
https://forums.flightsimulator.com/t/release-littlenavmap-toolbar-window/296952?u=azredneck33
Nice to be able to adjust what is displayed and different kinds of map representation via LNM settings.