Quote from: vbazillio on August 25, 2012, 05:19:28 PM
Update 1205 (august 2012) of the French VFR reporting points to download right here : http://20-100-video.blogspot.fr/2010/01/points-de-report-vfr-france-pour-plan-g.html

I've created a BGL file for FSX for these VRPs with markers similar to my UK VRPs. You can dowload it from:
HERE. See the included readme.txt file for details.

The first record in the file which fails to load looks like this:
"POI","Alcock & Brown landing site","Phew!",53.4671516418457,-10.03249168396,0,6.93,"EI","Landed upside down in a bog - but still heros"

That has eight commas = nine fields. All other records have eight commas. Maybe Plan-G doesn't like quotes round the text fields? though that's quite normal in a CSV file. I'll try it with no quotes.


Edit to add: Yes that solved the problem - quotes are not required, in fact they cause the error.

Thanks for your response. I think I've found out what the problem is - my scenery.cfg shows UK2000 Volume 1 with a complete path, with the disk letter different from that used on the laptop sharing the disk.

Bypass is to use the database created by running Plan-G on the desktop - copy this to the laptop, and all is well.  :)

EGDP is in UK2000 vol 1 installed on my FSX. It shows correctly in FSX, but is not shown in Plan-G after database load. Same in Version 8.1 and 9.0

Log shows:

QuoteError importing C:\ProgramFiles\Plan-G\Userwaypoints.csv: Insufficient data on line1. Only 9 columns (needs a minumum of 5)

???

Having exported from version 8.1, and edited out all those already included in version 9.0, this message comes when trying to import what's left.

I'm running FSX on desktop with Plan-g on Laptop connected via FSUIPC.

Quote from: Gray Brett on August 28, 2009, 08:46:50 PM
Captivating avatar Tony  ;D

It's one of those supplied for anyone to use. - I tried uploading my own picture but that didn't work. So I just picked that from the list instead.

It's Saturday.

Quote from: tim arnot on August 25, 2009, 07:04:46 PM
Yesterday's future is today's past....  ;)

Shouldn't that be tomorrow's past?  ;)