FYI All: ZenDesk has replied to a support ticket and acknowledged the issue with SimConnect (causing CTDs when connecting while in a Bush Trip from the Activities menu).  [What a strange problem...]. They also said that it will be fixed in the next MSFS update.

FYI Tim:  The original CTD issue that I reported does seem to be a MSFS issue as you suggested and I've verified that it happens with Little NavMap also. 

To clarify a bit - the CTD consistently occurs (for me and others, maybe not all), when you are either in a Bush Trip from the Activities menu and you connect your flight planner (via SimConnect), or let's say you already have connected the flight planner and then go Main Menu > Activities > Bush Trips > [I believe any of them I've tried 3 so far].  The Sim immediately stops responding then crashes to the desktop.  The Event log contains an Event 1000 indicating FlightSimulator.exe as the "Faulting Module."

I realize this may not help with development here and now, but it may be handy to be aware.

It was happening immediately after connecting, but... I think we can hold off on this one.  Another problem cropped up at about the same time, having to do with a faulty BIOS update for my laptop.  It was coincidental to my using Plan-G build 237.  That BIOS issue is resolved now and in the process of troubleshooting that, I reinstalled Plan-G 237, which seems to be working better now too.

I still get a Crash To Desktop sometimes in MSFS, but not immediately after connecting, so I think it is strictly a MSFS issue at this point.

I'm sorry if I've wasted any of your time.  It seemed like a strong correlation and I wanted to check and see if it was "just me" or something with Plan-G.  Glad it doesn't seem to be a Plan-G issue at all.  Thank you!

I don't know about the version of MSFS affected.  Started happening about 2 days before I reported it, when I first tried the 237 build.  I jumped from 233 to 237 and just copied everything in the 237 ZIP file into the existing 233 (Plan-G build) folder.  Maybe that won't work?

When I copied a clean 233 over the same folder again (replacing all duplicate files), it worked fine again.  I have not tried any intermediate builds.

Seems to be crashing MSFS every time I connect.  Is this unique to my system?

You are awesome sir!  And, this is a truly great product/tool.  Thank you very much.   :)

Think I misconfigured something.  I'm using the 233 build of the v4 beta but my gut tells me it is not related to the beta.

Suddenly, the map is covered with large numerals with degree symbols next to them (kind of tan or light brown/orange colored).  Once they appeared (triggered accidentally I think), I can't turn them off.

Does anyone know what the cause is and/or how to fix it?

Thanks for any help. :0)

Hi.  Looking for a sanity check...   :)

I've used Plan-G for flight following (and lots more) for 2-3 years.  While most of what is discussed here is about creating a flight plan in Plan-G and exporting it to the flight simulator, I have always created my flight plans in FSX and then I "Open" the flight plan in Plan-G (just point Plan-G to the User folder where plans are saved from the sim.  That has worked great for me; and it has been very simple to do.  Am I the only one doing it this way?  Does it make a lot more sense to create from Plan-G then "Load" the plan into the Simulator?  It seems a little more complicated, and I don't see yet what the advantage(s) are.

It seems like I got started this way based upon info in Plan-G documentation, but maybe I got from somewhere else.

Anyway, I appreciate any thoughts you may share.