Quote from: tim arnot on December 03, 2009, 09:04:15 AM
Did you see what error was reported in the log file? It cold be one of three) This is the first I've heard of it not working on a non-system drive, but it's certainly worth a followup.

Hi Tim

Typically I do not have that log file so what I did was this to try to repeat the original situation.

Deleted HKCU\Software\TAS

Unzipped to D:\FS9Online\PLAN-G

Run the app

Acknowledge the Build Database dialog

App starts up with no error connecting to Google Maps

Build the FS9 database

All worked as expected.

So I don't know what happened first time, sorry.

I have attached the logfile for this reinstall but I guess it will only tell you that everything in the garden is lovely.

Thanks
Graham

Quote from: TangoEcho on December 03, 2009, 03:56:46 PM
I'm confused here. Why make a plan in one prog and import it into another when it can be easily produced in the latter?

Hi Tom

Unless I have missed it, and I have read the manual  :) there is no automatic flight plan generation from departure to destination. When flying offline I use FSNAV to do this so I thought I would see what happens when FSNAV exports to a .PLN file and PLAN-G opens it.

Like I said, no biggie, I can correct any funnies by hand.

Even though I have only been using it for a day, I like the app  ;D

I created an FP using FSNAV and exported it to FS9 PLN format and got the following

Plan exported by FSNAV

waypoint.24=LUB, V, N53* 56.45', E10* 40.07', +000000.00,
waypoint.46=LAM, V, N51* 38.77', E0* 9.10', +000000.00,


After loading into PLAN-G and saved under a new name

waypoint.24=, LUB, , LUB, V, S11* 35.07', E27* 32.8', +004294.00,
waypoint.46=, LAM, , LAM, V, N38* 54.44', E16* 13.55', +000036.00,


After deleting these two waypoint and adding them by hand, and saving the plan under another name

waypoint.24=ED, LUB, , LUB, V, N53* 56.45', E10* 40.07', +000262.00,
waypoint.46=EG, LAM, , LAM, V, N51* 38.77', E0* 9.1', +000196.00,


You will see that FSNAV is exporting in the ?old? FS9 FP format. The route I generated had 48 waypoints and it was just these two that were not right.

For example:
FSNAV

waypoint.0=UUDD, A, N55* 24.50', E37* 54.50', +000587.27,
waypoint.1=UM, N, N55* 52.00', E36* 55.00', +000000.00,
waypoint.2=AR, N, N55* 59.00', E36* 48.00', +000000.00,
waypoint.3=BG, N, N55* 50.00', E34* 52.00', +000000.00,
waypoint.4=TU, N, N55* 51.00', E32* 56.00', +000000.00,
waypoint.5=RATIN, I, N55* 16.80', E30* 51.80', +000000.00,
...


PLAN-G

waypoint.0=, UUDD, , UUDD, A, N55* 24.5', E37* 54.5', +000583.00,
waypoint.1=, UM, , UM, I, N55* 52', E36* 55', +000000.00,
waypoint.2=, AR, , AR, I, N55* 59', E36* 48', +000000.00,
waypoint.3=, BG, , BG, I, N55* 50', E34* 52', +000000.00,
waypoint.4=, TU, , TU, I, N55* 51', E32* 56', +000000.00,
waypoint.5=, RATIN, , RATIN, I, N55* 16.8', E30* 51.8', +000000.00,
...


No big issue but I thought you might like to know about it  :)

Quote from: hbarkhof on December 02, 2009, 05:01:03 PM
And finaly I found the solution but it's a crazy one. The plan-g software appearantly must be installed on the drive were the operating system boots , in my case C:\     C:\Plan-G\  works but D:\Plan-G does not  >:D >:D

As a follow-up, I too installed on the non-system drive D:\FS9Online\Plan-G and got the same error. After moving to C:\Plan-G everything built ok and the the db was built.

I am using WinXP SP3, .NET3.5 SP1, FS9.1

Incidentally, on the initial failure, after the messagebox was okayed, the UI disappeared but the app was still running (presumably still trying to build the database).