I am becoming more convinced that the problems that have occurred since the 3.0.2 upgrade are linked to the introduction of the automatic database backup. I suspect that Luminar tries to access the last backup and if this is corrupt in some way it can't cope and that is where load time crashes occur.
I have just recovered from Luminar crashing on loading by going into the catalog folder, right clicking on the backups folder and selecting the rename option & changing name to "Backups old".
Luminar then loaded normally and in doing so created a new Backups folder. This process does nothing to the catalogue itself and so all my folder structure and edits are exactly as they were.
So may I suggest that if Luminar crashes on load for you that you try this before reinstalling Luminar and/or creating a new catalogue and losing edits.
The only draw back to this approach is losing the automatic backups so may be worth doing a manual full backup every now and again, though Time Machine backups also work.
I am not bothering to report this to Skylum support as I am not sure that their first-line support would understand that I am pointing out what might cause a problem and might be useful information for their developers rather than needing assistance to resolve the problem. At least that was my recent experience when reporting that my first experience of losing files from the catalogue came after using Lightroom plugin at same time as Luminar was already running standalone, and that perhaps the corruption came from an interaction. The responses from different people gave me no confidence that they had actually read and understood that I was trying to give a pointer that might help resolve the problems, if not already resolved ready for next update.
Please sign in to leave a comment.