I believe I might have resolved this...

Interesting enough, while dabbling in mission building in a military simulation game called ArmA 3, I was consistently getting CTDs when I went live to test, due to a paging file error. So I blew away my pagefile.sys and generated a new one. That immediately resolved my problems in ArmA 3. And now with some flying around the PacNW this afternoon with PlanG v4.01 b262 always connected, I didn't receive a single CTD. I was certainly flying around areas with extensive 3rd party scenery, because I just bought FSimStudios' CYVR and CanadianFSimStudios' CYAZ and those were the airports I was departing and arriving at.

So it looks like both simulators CTDs were caused by a corrupted paging file. I can't remember the last time I hade a corrupted pagefile.sys - maybe as far back as Win2000. I'm not sure why the CTDs only happened in MSFS 2020 when PlanG was connected, but maybe in that set of circumstances MSFS or Win10 uses, or causes the paging file to be utilized.

Quote from: tim arnot on August 25, 2022, 10:49:57 AMIt could be worth clicking in an area of blank desktop before you click in the Plan-G window - that will "deactivate" MSFS (ie make it not the "active" window) If it still crashes, that eliminates clicking in the Plan-G window as the cause of the problem. Similarly, if when you're not running Plan-G you don't click outside the FS window, maybe  the reason it didn't crash is simply that you never clicked outside MSFS. Trying these will help narrow down the problem.

OK, when I'm next flying I'll try that approach when I've connected Plan-G to MSFS.

QuoteAlso, if you look at your computer's error logs, that should show some extra information about the crash, at least identifying the faulting module. That can help us tell if it's a known problem, or has a known fix etc.

I've wondered about this. Is there a error/crash log that's specific to MSFS? There was a log for FSX, but I haven't read anything about MSFS having an equivalent.

I should probably mention it'll be some days before I'm flying again. I broke my wrist on Tuesday and with my occupation requiring me to wordprocess all day, it's about as much fatigue and discomfort I can manage right now.

Quote from: tim arnot on August 24, 2022, 04:29:36 PMI'm not totally clear here: is it MSFS that's crashing? or Plan-G? Also, do you have any other external utilities running, such as JoinFS or FSUIPC? (you've already mentioned TrackIR)

MSFS is crashing and almost always without any error message. The next time I start MSFS, it prompts me if I want to start in standard mode or safe mode. The client software for TrackIR 5 is the only other external utility I have running.

QuoteAlso how are you connecting Plan-G to MSFS? Is it through SimConnect, or through FSUIPC?

Via SimConnect. I'm new to MFSF and don't own that edition of FSUIPC yet.

QuoteWhen you click out of MSFS to use Plan-G, do you directly click Plan-G or do you click the desktop first?

I run MSFS in windowed mode and have a 3 display setup. So with Plan-G running in one of my other displays, I just move my mouse to it and click it directly.

My Plan-G 4.1.0 install was indeed into a new folder.

[Edit] This might provide better clarity to your 2nd question; when accessing File > Options > FS Connection the selected setting is "SimConnect 2 (FSX/MSFS)." I'm not sure why it's set to SimConnect 2 as opposed to SimConnect  1 - Plan-G did that by default. Should it be set to SimConnect 1?

I'm getting a Crash To Desktop error with MSFS on every flight I fly when Plan G 4.01 build 262 is connected to MSFS. Plan-G runs fine on its own and it appears to have created a flawless database. The database is no small achievement, because I have all of the fan-made addon scenery from the Return To Misty Moorings website with 100's of new seaplane base and cabin locations, all of which are accessible on the Plan-G map. I've also been able to successfully create flight plans and export them to MSFS, which has worked well with the exception that the elevation chart doesn't show me any graphics for terrain.

The crashes come when I connect Plan-G and fly the flight specified by my flight plan. Plan-G has a rule in my Windows firewall settings. I have a multi monitor setup, but don't span my desktop. So I run Plan-G from my left monitor. The CTD's are random, but I did note that 2 of them occurred when I turned to access Plan-G to zoom the map. I run MSFS in windowed mode, so it's easy to do that. Almost all of my departures and destination points have involved the scenery airstrips or seaplane bases from RTMM. I also use the TrackIR 5 head tracking accessory and software. If I fly the same flight plan without Plan-G connected, MSFS runs without any errors.

I haven't given up on the Plan-G yet and I have hundreds of memorable hours bush piloting with version 3.2.2 and FSX-SE. So having become very familiar with the earlier app, I feel committed to continue to use it. I'm wondering what I need to provide to better help with the beta testing process?

[Edit] I forgot to mention that on 1 flight I got a cryptic break point error. It was displayed in an old school dialog box that looked like it could have been generated by a 1990s edition of Visual C.  And nevermind about the elevation graphics - I recreated folders for 262 for zero state install and I forgot to copy the DEM files from my 3.2.2 installation.

I see a problem on the 3rd line of that portion of your log you posted. The Registry CFG path is pointing to a subfolder under the ProgramData folder on your C: drive. I've heard of this before for FSX:SE and there's some reason why it's that way. I believer it's either when installing FSX:SE on a PC in which FSX9/2004 is also installed, or when uninstalling FSX:SE and installing it to another location; could even be for yet another reason.

Anyhow, I'd recommend opening the SCENERY.CFG files in your C:\ProgramData\Microsoft\FSX folder and your C:\Users\BigDog\AppData\Roaming\Microsoft\FSX folder and then comparing the entries toward the end of them. If you see an entry for your KCGX scenery in the Scenery.cfg file that's located under the ProgramData folder, change PlanG to use that location for the "FSX Scenery" setting instead. You could just copy that Registry cfg path entry from your log and paste it in.

Are you sure you're using the new updated KCGX within FSX:SE? The reason I ask is because some addon scenery needs to be manually added to your library - usually not the case for Steam DLC, but I've heard of where an automated install fails. It's a simple procedure to test whether it's been successfully added to your scenery library; just access [Settings] > [Scenery Library...]  and make sure you KCGX airport scenery is present in the list of scenery areas.

Otherwise, PlanG need to know where the correct location of your user SCENERY.CFG file is to successfully build the database.  Note; this is different than the SCENERY.CFG that's located in you FSX folder and is typically in a folder with the path \Users\username\AppData\Roaming\Microsoft\FSX folder. The path for the folder may different, depending upon your version of Windows.

Glad to be of help Col.

I haven't run PlanG in such a configuration, but it's going to have to know how to communicate with FSX via Simconnect and where to read the Scenery.cfg file. First start would be to ensure PlanG knows where to find those, so what have you entered in the FSX Program and FSX Scenery.cfg text boxes under File > Options > Locations?

[edit] As well, did you read this forums Connecting Plan G over network (simconnect) TIP stickied thread. I haven't read through that myself, but there's no doubt helpful info in it.

Quote from: Col1948 on September 28, 2019, 11:47:06 AM
I saw one topic where it said replace the . with a / in the long code, I tried that but still got the error.
I have version 3.2.1.151 in Plan-G
The code from MB is a new one because I recently logged in after a spell away, there is a public code as well, I tried using that but still no joy.

Any help appreciated.

For mapbox maps, you don't use your account name in the PlanG ID textbox, but instead must enter a portion of what's called a mapbox style ULR. I got a mapbox map to display correctly last week and these are the steps to do it:

• Create an account at mapbox.com
• Once your account is activated, login and click the drop-down menu at the very right of the home webpage and choose 'Account' to access your account page.
• Click the 'Design in Mapbox Studio' item on the Tools & resources menu; right side of the page.
• When the "Mapbox | Studio" web page is displayed, click the [New style] button to access the 'Choose a template' page
• Click the template you'd like ('Basic template' and 'Satellite' both worked for me). A checkmark will appear on that map type.
• A [Customize specific template you selected] button will also appear at the middle of the page bottom; Click it. It may take some seconds, but eventually an editable map with a title of "Styles > your selected map type", will be displayed.
• Don't bother making any edits to the map, instead click the 'Share...' option on the upper right of the menu bar.
• On the 'Share' form, locate the "Your style URL" textbox and click the clipboard icon to the right of it to copy the URL to your clipboard.

NOTE: The next step is a bit tricky, but crucial to making the map display correctly in PlanG.

• Copy the style URL into any text editor. Then select that portion of that URL text beginning at your account name to the end and copy it to the clipboard. This is a simplified, abstract example of what an edited style URL should look like:  acountname/aa9aaaaa9a9a9aa9aaaaaaaa
• In PlanG, access 'File' > 'Options' > 'General' and paste that edited style URL into the Mapbox 1  'ID:' textbox.
• Go back to that mapbox 'Share' form and locate the 'Your access token' textbox. Click the clipboard icon to the right of it to copy the token to your clipboard.
• Close the mapbox 'Share' form and then click "Styles >" in the upper left of the map. You'll be returned to the Mapbox | Studio Styles page and you will see your new style listed there.
• In PlanG, again access 'File' > 'Options' > 'General' and paste that access token into the Mapbox 1  'key:' textbox.
• Enable the Mapbox 1 radio button and then close PlanG. The next time you open PlanG, your mapbox map should display correctly.

It might seem like an awful lot of effort, but I found that there's some advantages with mapbox maps. The Satellite map in particular is very good for viewing the actual layout of an airport or airfield, since it provides a photographic depiction of them.