v4 Alpha Build 237

[ju28]

Hi Tim,
after updating v4 to build 234 I could connect Plan-G to the MSFS successfully. But I couldn't manage to create a Nav Data File. This worked out finally after updating to build 237. It shows for minutes that the file was created.

But for what ever reason Plan-G still don't have any airport or any VOR, nothing. Not visible on the map and nothing if you use the search window.

The only source I did set while creating the nav data file was the MSFS Content Path as "C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator".

Have no idea how to fix it.

Appreciate your help.

Happy new Year,
Juergen

[tim arnot]

Firstly, did you select the database after you built it?
Secondly, if you did, please attach the log showing the build.

[ju28]

Hi Tim,

thanks for your reply, according to your input I found in the Data folder a "Plan-G_NavDataMSFS_BAK.db" with 745.856 KB and a "Plan-G_NavDataMSFS.db" with 216 KB. So I deleted the ...db and renamed the BAK.db as "Plan-G_NavDataMSFS.db" and it worked.
Seems to me that after a second start of building a data base the new file was created with no data in it.

[ju28]

Hi Tim,

what I just have realized is after I added two freeware airports via the Generate Nav Database-Button / Settings it generates the new database file only with the added airports and Plan-G shows only this two airport. And then I tried it again just to recall what I did and than the actual fiel was copied as BAK-file and my data file with all content was deleted.

I deleted both .db files and created a new data base and I got only a file with the two added freeware airports.

Just for you as information- don´t know if this is a bug but it seems to me that this is not what it should be

[tim arnot]

It only maintains one generation of backups. If you build a database and then immediately rebuild it again, obviously your second backup is going to overwrite the first backup.

If the database only has two airports in it, please attach a log file covering the database build. (I strongly suggest you delete the existing log file then build the database again, as this will provide the clearest log, and be of manageable size)