Ah ok, makes sense then. Thanks Tim.

Test: rename your data folder.....  x:\documents\Plan Gv4 Files  to Plan Gv4 FilesOFF   

Then try to do a fresh 242 from the zip. The run the executable and see if it creates the documents folder "Plan Gv4 Files" and has db default files or goes CTD.  If no data created then it will CTD. Suspect something broken in the zip to create a default set of db folder/files to start. 
If yours does create the default "Plan Gv4 Files" folder and db files upon startup then I have an issue somewhere!!

(Just tried this again with build 240 and confirmed that it works fine in 240 to create the documents\Plan Gv4 Files  folder and files, whereas build 242 doesn't not).

Norm

Ok Tim... figured it out..  (Logbook db had nothing to do it cause none of the db files can be found). My existing data folder was not named Plan-Gv4 Files. (I had mine set and cfg as Plan-G v4 Files.  (space between Plan-G and v4 Files. (on purpose).   But 242 is not creating a default Plan-Gv4 Files data folder/files hence will not start.

So the beta v4 build 242 is trying to start, but can't find the data (and since it is not creating a default set) it has no source or parameters hence CTD. (This version (build 242) does not create it's own db Plan-Gv4 Files folder or data files for some reason).   

I renamed my previous "Plan-G v4 Files" data folder back to your default named "Plan-Gv4 Files" and tried it again: Build 242 upon startup now found my old previous 240 db data files and therefore started up.   (but 242 itself does not create a data folder hence to use 242 a previous version a data folder must already be in place and the folder named Plan-Gv4 Files) or CTD.

So for a new user, build 242 as is will not work as upon startup as it does not create the required data folder Plan-Gv4 Files or db files required to startup. Also for anyone who requires/wants a separate or different named db data folder name (for whatever reason), can no longer do this in 242.   

So right now I have build 242 using the build 240 data files (which I don't want to do) and 242 is not creating default data in which to be able to startup.

Hope this now explains the issue. The  data folder "Plan-Gv4 Files" appears to be hard coded somewhere but a default is not being created upon when Plan G exe is run.

Now after getting into 242, do see Options/Locations that can be configured/change.. but that would only work  if data folder/files are already in place prior to 242 Plan G initialization/startup. (242 does not create a default data folder/files that are required.)

(When the exe is run, if Plan Gv4 files Folder is not present a default needs to be created to enable the app to startup).

Hope this helps and explains.

Norm

Hmmm, for some reason 242 won't start up. Executable run  (Run regular as well as admin- same result:
splash screen displays then Closes/CTD).  (Faulting Module- KERNELBASE.dll) and .NET Runtime error:

Faulting application name: Plan-G.exe, version: 4.0.0.242, time stamp: 0x60776c81
Faulting module name: KERNELBASE.dll, version: 10.0.19041.964, time stamp: 0x11253621
Exception code: 0xe0434352
Fault offset: 0x0012a6e2
Faulting process id: 0x213c
Faulting application start time: 0x01d753bbd83e2459
Faulting application path: C:\Flightsim Programs\Plan-G_v4 Beta Build 242\Plan-G.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 1b66d2e6-b3a9-4b8a-b9be-87c11ed648ed
Faulting package full name:
Faulting package-relative application ID:
----------------------------------------------

Application: Plan-G.exe
CoreCLR Version: 4.700.21.21202
.NET Core Version: 3.1.15
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Windows.Markup.XamlParseException: The invocation of the constructor on type 'Plan_G.ViewModel.ViewModelLocator' that matches the specified binding constraints threw an exception.
---> System.TypeInitializationException: The type initializer for 'Plan_G.Data.Logbook' threw an exception.
---> Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 14: 'unable to open database file'.
   at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db)
   at Microsoft.Data.Sqlite.SqliteConnection.Open()
   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenDbConnection(Boolean errorsExpected)
   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternal(Boolean errorsExpected)
   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected)
   at Microsoft.EntityFrameworkCore.Sqlite.Storage.Internal.SqliteDatabaseCreator.Create()
   at Microsoft.EntityFrameworkCore.Storage.RelationalDatabaseCreator.EnsureCreated()
   at Microsoft.EntityFrameworkCore.Infrastructure.DatabaseFacade.EnsureCreated()
   at Plan_G.Data.EF_LogbookDataContext..ctor() in C:\Users\Tim\source\repos\Plan-G\Data\EF_Logbook.cs:line 209
   at Plan_G.Data.Logbook..cctor() in C:\Users\Tim\source\repos\Plan-G\Data\Logbook.cs:line 35
   --- End of inner exception stack trace ---
   at Plan_G.Data.Logbook.QueryAircraftList() in C:\Users\Tim\source\repos\Plan-G\Data\Logbook.cs:line 1454
   at Plan_G.ViewModel.LogbookAirframeDetailViewModel..ctor() in C:\Users\Tim\source\repos\Plan-G\ViewModel\LogbookAirframeDetailViewModel.cs:line 239
   at Plan_G.ViewModel.ViewModelLocator.CreateLogbookAirframeDetailViewModel() in C:\Users\Tim\source\repos\Plan-G\ViewModel\ViewModelLocator.cs:line 2565
   at Plan_G.ViewModel.ViewModelLocator..ctor() in C:\Users\Tim\source\repos\Plan-G\ViewModel\ViewModelLocator.cs:line 3907
   --- End of inner exception stack trace ---
   at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri)
   at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
   at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
   at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
   at System.Windows.Application.LoadBamlStreamWithSyncInfo(Stream stream, ParserContext pc)
   at System.Windows.Application.LoadComponent(Uri resourceLocator, Boolean bSkipJournaledProperties)
   at System.Windows.Application.DoStartup()
   at System.Windows.Application.<.ctor>b__1_0(Object unused)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
   at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
   at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
   at System.Windows.Threading.Dispatcher.Run()
   at System.Windows.Application.RunDispatcher(Object ignore)
   at System.Windows.Application.RunInternal(Window window)
   at System.Windows.Application.Run()
   at Plan_G.App.Main()

(I have Plan-G_3.2.2.167 and Plan-G_v4 Alpha Build 240 are both working perfect.. 
but Plan-G_v4 Beta Build 242 won't fire up.    (dotnet-runtime-3.1.12-win-x86.exe) is installed.

Any ideas Tim? > NET runtime version correct?  (Or maybe I don't have c:\user\Tim on my pc so have no sources?).


Norm

Yup add-ons (Custom add-on scenery) RTMM (Return to Misty Moorings - Alaska scenery)  (https://return.mistymoorings.com/)
(Looks like the scenery is the custom pipeline airports (BWEP) - https://return.mistymoorings.com/bwep/index.php).

Yes worked before, and they do work in v4 and v5. (There is no issue or errors in Plan G v4 (237) but is in Plan G 3.2.2).

No worries Tim. Will keep playing with it at this end big no biggie. Plan G v4 (237 +) seems to be working fine so would be best to continue developing that app as the previous versions will slowly die off as more and more switch to v5 and/or MSFS2020. 

Thanks again for your help.
Norm (Canada)

Getting errors writing custom airport entries.

09:14:28.5 Error writing airport: 0AK0 Scotts
09:14:28.5 WriteAirportsData-SetValue: : System.NullReferenceException: Object reference not set to an instance of an object.
   at Plan_G3.Data.FSData.WriteAirportsData(SortedDictionary`2 apts)

09:14:29.0 Error writing airport: WSM Wiseman
09:14:29.0 WriteAirportsData-SetValue: : System.NullReferenceException: Object reference not set to an instance of an object.
   at Plan_G3.Data.FSData.WriteAirportsData(SortedDictionary`2 apts)

As a result of the errors as shown above (and many similar), the writing of the airports/diagrams is not completing. v3.2.2
(If I remove these bgl files and build navigation db with stock, then there is no errors and "show airport diagrams" works fine. 


Now a funny thing, if I run the build nav database with these files in Plan-G_v4 Alpha Build 237, there is no issue or problem. Go figure.


Any ideas?

The airport diagram windows opens/works fine it's just empty! Will redo the navigation database.

Plan-G v3.2.2... (Put this version back on, updated the db (P3Dv4)... but can't get any airport diagrams to show up.. 
Is there a switch to be able to show them or do I have a missing file? 


PS: Have Plan G V4-(237) installed and all the airport "show airport diagrams" are working. 

(Is there a file that I copy from v4 to the v3 DB (I have separate DB).. for the airport diagrams to show up in v3.2.2?

Hmmm ok Tim.. will try do some more checking to find the version that found all the stuff from the parent folder below when the parent path was entered in the Additional Scenery location field. (I know it already does a complete scan when scanning the root sim or the main Orbx folder if it is inside the root sim).   

In the mean time, if it is not too difficult to do, making the additional scenery location work that way -being all inclusive (parent through to also capture all the child scenery folders) is the way to go especially for those FSX or P3D users that have layers of scenery folders in various locations or maybe using complex add-ons (xml). So to select a parent folder in the additional scenery location form and all items below that folder can be additionally picked up and scenery contents added to the database would be very beneficial and would avoid much work in selecting a path for each scenery entry if the user wants those pieces as part of the Plan G database.

Thanks for all your work on this Tim.

Could enter all the paths direct into the AdditionalSceneryLocations.txt (much faster using a text editor). I have tested and know this works when each path is added and the apps finds as directed builds the correct database.

But if the parent folder only is selected app can't seem to find anything that is a level below that parent level.
I'll keep playing with it in an effort to try to establish why those are not being picked up but they used to be picked up in previous versions. Maybe my sub-directories scenery levels are too deep but don't think so.

End user won't want to enter multiple individual paths to be able to generate all the addon scenery/airports on the map.

Will keep trying to play with it Tim but what it seems like is: IF it is not in the scenery.cfg it's not being picked up unless that path is directly entered into the Additional Scenery Location form.

Here is one specific example:   Scenery is > NA-USA-Alaska RTMM Add-on which has 5 sections of scenery pieces with 1-2-3-4 being object libraries - and the last section has all the add-on scenery locations - 243 individual scenery locations to be exact..

So start by adding the D:\Add-ons\  which is the parent or main add-on scenery folder.
(All scenery folders under this main folder are in their own sub-directories:)

Building Navigation Database: 

1. Path entered for additional scenery location: (Main add-ons folder).

D:\Add-ons\  << but no sub levels being picked up when the build navigation database is executed
----------------------------------------------------------------------- 

2. Then tried next level down: path set up in the Additional Scenery Locations prompt:

D:\Add-ons\NA-USA-Alaska RTMM Add-on << no sub levels being picked up when the build navigation database is executed
-----------------------------------------------------------------------

3. Then tried next level down: path set up in the Additional Scenery Locations prompt:

D:\Add-ons\NA-USA-Alaska RTMM Add-on\05-RTMM Addon Scenery << no sub levels being picked up when the build navigation database is executed
-----------------------------------------------------------------------

4. Then tried next level down: direct paths set up in the Additional Scenery Locations prompt:

D:\Add-ons\NA-USA-Alaska RTMM Add-on\05-RTMM Addon Scenery\Misty's Place\  << Picked up ok and database  built (and map displays correct airport location and correct ICAO). (Misty's Place has the scenery folder)

D:\Add-ons\NA-USA-Alaska RTMM Add-on\05-RTMM Addon Scenery\NAC Bases\   << Picked up ok and database built
(and map displays correct airport locations and correct ICAOs)  (NAC Bases has the scenery folder)

D:\Add-ons\NA-USA-Alaska RTMM Add-on\05-RTMM Addon Scenery\CIRP Ice Stations\ << Picked up ok and database built (and map displays correct airfield locations and correct ICAOs)  (CIRP Ice Stations has the scenery folder)

So only on the last case was the scenery found and included in the database.


Hope this specific example better illustrates to what I am trying to explain. 

Norm 

Referring to creating the airport database (using Additional Scenery Location paths:)

Appears that the Additional Scenery Locations path doesn't pickup any sub-levels.

Now I am using multiple scenery pieces that are built as add-ons.. and they have sub-levels of scenery. Is there a way to scan an entire scenery root folder (IE: Add-ons folder" that will pickup all the scenery folders underneath the root that may be in sub-folders?  Or does each folder path now have to be individually selected/chosen to be included in building the airport data base?

(I am referring to many sub-sub-scenery folders that are under addon scenery folder in sub-folders.. It used to work (like a wildcard) *.* in previous versions but seems that it is not picking up my add-ons folder scenery pieces in that folder. 

Now I did test a few of the specific paths - and selected a few direct in the form entry of the additional scenery locations option then the loading of those scenery is picked up when the database is being built - but if the root folder only is selected then any sub-subfolders below appear not to be included in the database build.
Anyway around this? or anyway to include a *.* wildcard for a root scenery folder that when selected that all scenery pieces in sub-folders would also be picked up in the airport database build?

Ie: My RTMM addon is inside the main add-ons folder, (not contained in the scenery.cfg). (P3D). The root folder contains a scenery that contains 241 sub-scenery pieces which make up the entire package- and each of those sub-folders contains it's own scenery folder but none of it is being picked up when building the database.
But if I include the exact path to each or any of those sub-folder scenery pieces then that scenery is read and included in the Database.

Is there a way to revert a chosen additional scenery location as a parent to apply or scan all the sub-locations or is there a way to be able to apply a wildcard on a main addon or scenery folder so that the system, when creating the airport database, could be able to pickup all the scenery pieces that are in sub-folders underneath that main folder?

Make sense?  I hope I explained the issue that I am having. I have too many add-on scenery pieces built as addons and in sub-folders in a main scenery folder that are not being picked up during the database creation.

Norm

Ok Tim. will give it a go.. (also updating to 235),

Thanks Tim.

Ok Tim. Will do some more playing.. Now today's case was a multi-flight with only 5 others (JoinFS 1.5.10)
(FS AI Traffic off/ (Air & GA AI traffic OFF). 


Key Parameters:

FS Connection: Simconnect (P3D)  (Sim P3Dv5)

User Aircraft:
> Refresh Rate (seconds (2) <<<<<<<<<<<<<<<<<<<<<<<<<<  Maybe too short? 
Map Sync >Lock,
Update TAS from FS (unchecked/Off),
Show Waypoint Alerts (Checked)
Show Lat/Lon in Toolbar  (Checked)

Breadcrumbs Show trail (Checked)
Log trail (Unchecked/OFF)

Traffic
Show Moving (Checked)
Show Parked (Checked)

Range km 100   <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Maybe too large a radius?
Refresh rate (seconds) 5 <<<<<<<<<<<<<<<<<<<<<<<<<<  Maybe too short?
Breadcrumbs Show trail selected (short)  (Log OFF)

Everything else as default.

Will change "range" parameters as follows: then retest.
> User Refresh Rate (seconds) >> decrease refresh rate from 2 secs to 5 secs,
> Traffic > Reduce Traffic range from 100 km to 50 km,
> Traffic > Reduce Traffic Refresh Rate >> decrease refresh rate from 5 secs to 10 secs,

Build 234 has an intermittent issue of bogging down or being so sluggish after running/connected for @ 10mins or so.. with either MSFS2020 using either Simconnect 1 or 2 and also the same drain with P3Dv5 Simconnect (P3D). (After @10mins or so the app is bogged down and there is @ a 3 sec lag to access any function in plan G). .  Not sure Tim but It's almost like a memory leak or something that drains the Plan G application and it then runs at a snails pace thereafter.  Now if I close out 234 and start it up again, it's fine again for 10mins or so - then may (or may not) bog down again. Didn't see this problem mentioned before (unless I missed it).

Today, ran plan G twice with bogging down (Simmconnect (P3D), then the third start up and run today, it was fine with no bogging down. (Not really understanding why this occurs while at other times it is fine but you may have some insight?) 

----------------------------------

The only other issue I note is that the end user must manually select: 1. The correct connection method for the sim used
and 2. manually select the correct airport database for the respective sim.

Now item 2. the airport database manual switch is not a big deal.  But is there any way to have an universal connection that can seamlessly connect to the various sims without user invention. 


Norm 
(Long time Plan G user).

Ah ok Tim-got it.  Thanks for the info. Working on it now.

Norm