Strange problem - help?

Ford Friendly · Post by **Ford Friendly** » 26 Nov 2008, 16:39

I am running into a problem that I have never seen before in either FSX or FS9.

I installed a new scenery, Bitburg v3, creating and activating a new scenry folder for it in the Scenery Library. The accompanying afcad doesn't seem to deactivate the default FSX afcad regardless of whether I have the "new" afcad in the Bitburg folder, temporarily set as the highest priority folder, or in ..\Addon SCenery\scenery.

I've spent about 2 hours on it so far and I have literally stumped myself on this one. I've redownloaded it, reinstalled it, even made a change to the afcad in AFX - which loads, accepts changes, and saves it just fine(including showing any changes I made to it).

I'm at a complete loss.

Any ideas why this would happen and/or how to fix it?

Ford

davidbernard · Post by **davidbernard** » 26 Nov 2008, 17:42

Maybe the airport reference point in the new afcad is different from the airport reference point in the default FSX one. If this is the case there will be two airports with different reference points sharing the same airport ID, which leads to a possible conflict.

Try changing the coordinates of the airport reference point to the ones in the default FSX one.

David

Ford Friendly · Post by **Ford Friendly** » 26 Nov 2008, 18:04

Hadn't thought of that. I'll give it a look and try.

Ford Friendly · Post by **Ford Friendly** » 26 Nov 2008, 18:52

That did it. Copied the default Lat/Lon coords to the new afcad reference point and all's well now.

There must be some sort of "tolerance" for such new/default coordinate variance in the FSn system as this has never happened to me before and I know I haven't ever worried about it when creating new afcads.

Learn something new every day as they say.

Thanks.

davidbernard · Post by **davidbernard** » 27 Nov 2008, 07:43

I had the same problem in FS9 once, so it looked kinda familiar to me. Glad to help.