Re: [Flightgear-devel] Hidden vs public files

[James T. <zak...@ma...>]

> On 6 Jan 2017, at 09:20, Thorsten Renk <tho...@sc...> wrote:
> 
> I suppose most commonly people deal with FG_HOME when their FG  
> installation crashes after an update due to the dreaded nav database  
> problem (SQLite access error or something like that).
> 
> This happens ~ once per week in the forum (for the last instance see e.g.  
> here)
> 
> https://forum.flightgear.org/viewtopic.php?f=17&t=31388#p302744
> 
> and since this is a SERIOUS issue, of course we try to spread the  
> information how to deal with it as widely as possible. Same is true for  
> the log files - of course we want to see them in case of problems, so we  
> need to tell people where to look for them.
> 
> I don't think there's any recommendation to actually edit files in FG_HOME  
> (I might be wrong there...) - but as matters stand, things are set up in a  
> way that makes it fairly crucial to have people locate it and read or  
> delete parts of it.

Hmm, this is unfortunate - I am basically unaware of any issues with the nav-db getting problems, because I don’t experience them locally, nor see any reports here. Are they confined to Windows?

There is existing code to detect when the nav-db seems to be corrupt, delete the current one, and rebuilt it - we ask SQlite to perform an integrity check + validation as the first step after we open an existing DB. If it fails we delete the DB and start from fresh.

I would prefer to fix this issue, and remove the need for users to touch things inside FG_HOME, but I would need some people to work with me on understanding why they see the issues and I don’t.

Kind regards,
James