No Nvidia filters or overlays are being used on my system.
Will try this.
Probably related, but ever since the Japan update, i’ve tried to do the Japan tour and have CTD 3 outta 3 times. Last one I was about 20 mins to Mt Fuji 
best solution - DO NOT use the VFR map at all for long flights
2 Likes
Work like a charm, thank you.
1 Like
I agree, WinterStewart.
I would also consider detaching “V” from your keyboard so that “we” do not accidentally press it. Ka-boom.
I purposely went into a clean session and tried every option I could think of to display the VFR, and after setting the options/assistant setting, mine does not blow up now. But, I will just minimize it when not in use and leave it active.
Was the CTD’s related to the VFR map usage?
it seems worked for 1st day testing. i will try for several days for sure,TKS anyway.
i’ve been using the one in the cockpit for now, not ideal, but it works.
what really is bothering me since the last patch more than the VFR bug is my log book no longer logs anything after the patch. 
stopped right as i was about to reach 200 flight hours, so been stuck on 197 since the patch.
I remapped it to X, like “eXit to Desktop”
It’s handy if you don t want to go through the Main Menu 
2 Likes
Better yet, use Little Navmap, which is free, open source, stable, and a million times better than the VFR. Instead of V, presse alt-tab, and you have a highly detailed map with all the infos you need.
Also, about random cashes, someone suggested cleaning the cache after the latest patch. That makes sense because if Asobo modified the format of some of the data, then the cache still stores ancient data that is incompatible and the game may crash.
So a good idea is to clean the cache after each patch.
No, I had a CTD 25 mn into the Japan tour and I don’t use the VFR map at all. I also have CTDs over Manhattan.
I’ll try again after cleaning the cache.
Im not going to spend 1 $ on any add ons, untill the basic game functinalities get up to a certain standard, which is sad since I really want to support our community developers.
2 Likes
Happened to me now, searched the forums for a fix only to find out that it is INCLUDED in the patch… lol what?
this update is an update with a little bit of bugs and glitches. A patch is supposed to FIX things, this is NOT a patch tell you that much.
Hey man I cant find this option anywhere, I’m in the options main menu.
Yep. Don’t use it until we get a hot fix - hopefully soon!
IMO they ought not have released this patch with such a known issue with the VFR map. I’ve sent several crash reports with a request for an urgent hot fix. Probably falling in deaf ears though
2 Likes
Since they didn’t bother releasing a hotfix for this critical known issue, we basically can stop expecting hotfixes ever. We’ll have to stick to their 2-week development sprints as it seems.
Based on the experience of test quality of previous patches, I’m not even sure if hotfixes are something we should want 
not that it breaks even more stuff…
maybe developer mode activated?
the logbook doesn’t count with that.
no developer mode when this happens.
what i found is i have to get that final ending screen in order for the flight to be logged, otherwise it doesn’t log. this was not the case prior to the last patch. even non-flights, where i started at an airport parking space and just used the drone to check things out used to log in the logbook and instances where i immediately exited the current setup flight due to forgetting to change flight number or wanting to start in a different parking space or accidentally forgetting to change runway start. so i guess it’s good those instances no longer get logged.