Piling on here....TX0T is coming up Clipperton Island in both V1 and V2 in the cluster spotting when it is French Polynesia in cty.dat
Doesn't V2 use cty.dat for cluster spot exceptions? In V2 I have "Use Clublog database" and "Use CTY database" enabled.
Also where does clublog.xml come from? Doesn't appear to get updated at all.
In V1 we see this error on a new installation of LogOM V1 -- could this error prevent the lookup of TX0T in the cty.dat file?
2020-11-02 16:27:58.9242 INFO: Log4OMMainWindow: *********************************************************
2020-11-02 16:27:58.9327 INFO: Log4OMMainWindow: *********** LOGGING LEVEL: TRACE MODE + SQL MODE ********
2020-11-02 16:27:58.9336 INFO: Log4OMMainWindow: *********************************************************
2020-11-02 16:28:13.3547 INFO: Log4OMMainWindow: *Open IMPORT CLUBLOG FROM WEB*
2020-11-02 16:28:13.4184 INFO: FileManagement: Clublog begin download
2020-11-02 16:28:13.4193 DEBUG: FileManagement: URL
https://clublog.org/cty.php?api=6e41673 ... ce4c6bbe0e
2020-11-02 16:28:13.4368 INFO: Log4OMMainWindow: *Open IMPORT RANKING FROM WEB*
2020-11-02 16:28:13.8625 INFO: FileManagement: RANKING begin save
2020-11-02 16:28:13.8664 INFO: FileManagement: RANKING save completed
2020-11-02 16:28:13.8674 INFO: Log4OMMainWindow: *CLUBLOG Database updated*
2020-11-02 16:28:14.6826 ERROR: *** FileManagement: Error downloading ClubLog Database ******* [Function: #=qVfFY8UX3NIm9FZJNZkLa3CL8XpFKQYcgMs7U$XeUp5E=] System.NullReferenceException: Object reference not set to an instance of an object.
at LogOM.BL.FileManagement.#=qVfFY8UX3NIm9FZJNZkLa3CL8XpFKQYcgMs7U$XeUp5E=(Object #=qDs4haVqs9PbDqTR4OfKoPg==, AsyncCompletedEventArgs #=qegipl4uvOXoZkLMfRNCdmA==)