News:

Status: CAVOK

Main Menu

Plan G

Started by den68, November 26, 2010, 03:50:57 PM

Previous topic - Next topic

den68

Iam not able to open the home,map,view tabs.Could you help me with this?

Skynet

Did you manage to build the database? Those tabs won't work until the database has been built. If the database failed to build, there will be errors shown in the log file. There are two likely reasons:

One is that PlanG didn't interpret the path to your FS correctly (you will see "illegal characters in the filename" errors). For this, you need to set the FS path in Options--> Locations

The other is what's being called "the comma problem" (you will see lots and lots of SQL database error). For this you will need to temporarily change your region settings in Windows.

Most of the other threads here deal with these two issues.

den68

The data base appears to been build ok,still cannot open tabs

vgbaron

 Tim - Don 't know if this is relevant but in another forum someone reported that - if P-G was installed into the w7 default ProgramFiles(x86) folder, the database was NOT built but there was no error message. Could that cause this issue?

Vic
P3D#1 - 7700K 5.0g ROG X270F 3600 15-15-15 - 2-GTX1070 SLI 1000W PSU 1- 850G EVO SSD, 2-256G OCZ SSD, 1TB,HAF942-H100 Water W1064Pro
40" 4K Monitor 3840x2160 - AS16, ASCA, GEP3D, UTX, Toposim, ORBX Regions, TrackIR
P3D#2 - 3770K 4.7g Asus Z77 1600 7-8-7 GTX680 DH14 850W 2-1TB WD HDD,1tb VRap, Armor+

tim arnot

I don't believe the database can fail to be built and there be no errors at all recorded -- you'd need to show me a log file of that happening.

Plan-G requires there to be airports in the Airports table (either FSX or FS9) for it to consider the database to have been built. You will see "FSX database built" or "FS9 database built" in the logfile at startup if this is the case. And that is what determines if the menus are enabled or not.

Installing Plan-G outside the Program Files folders certainly may help, as will checking for the 'bad path' and 'comma' issues.

Tim. @TimArnot