He is trying to be a horse's rear end with his attempt to blame you for this situation.The bottom line is that AS needs to read a FS formatted plan. If you are going to use a 3rd party planner then you need to either make sure the exported plan is in FS format or open the plan in FS and re-save it. Then you have a FS formatted plan to use in any version of AS.

Jim,who are you of all people calling a horses arse? I have FSCommander and the plan is saved to FSX as a pln file. This plan is then imported into AS 2012 as per the previous edition ASE. If thats doesn't work it's operater error.

If the plan has points not in the FS database then AS will not process the plan. Re-saving the plan in FS eliminates this. With my suggestion Nixon fixed his issue, so I guess I was more helpful in this situation. It was not operator error.

I had this issue as well before. Look into your scenery.cfg (C:ProgramDataMicrosoftFSXScenery.cfg) if there are no weird spaces and numbering of layers and areas. Once I " cleaned" my scenery file, I ree-run the database manager of FS Commander and EHAM was recognized again. Of course all other scenery databases as wel (for example RC4, FS Captain, EFB etc.)Perhaps this helps you.Succes.

DickoIf you read the whole of this thread you would see that the problem only occurs with EHAM. Luckly am thick skinned so am not bothered that you inferred that it was operator error. If you are going to make such comments you too should develop a thicker skin, so until then just read before you post.

DickoIf you read the whole of this thread you would see that the problem only occurs with EHAM. Luckly am thick skinned so am not bothered that you inferred that it was operator error.If you are going to make such comments you too should develop a thicker skin, so until then just read before you post.

Ok fare enough, don't worry there have been plenty of times when operator error applies to me.

Ok fare enough

Should read fair enough :(