I just did a test and it seems to be a problem with number of revisions and longitude shift. The longer an object was sitting there, the more it moved in longitude only. All other values were unchanged with each edit. If you edit a file a couple of times, you won't notice it. Work on it a few times a day for a week or so and it's a big problem.The only option I can see at this point is to disassemble the file each time and save the new text to the old stuff, then re-assemble it. In five edits of a file, my first object went from lon="W114 31.61600" to lon="W114 31.61627". More recently placed objects had less of a shift, but the longitude values were still changed.

Perhaps this is some sort of round error, occuring during conversion from decimal degrees to DMS format. I think the original AFCAD program had a similar problem, although I would think it would affect both latitude and longitude, unless it was near the equator or prime meridian.- Martin

Have you posted about these errors on the BEV site? Most of us thereare quite sure someone at Abacus reads the EZ Scenery forum.http://www.flightsim-bevs.com/smf_1-0-5/index.php?board=59.0Ken

Yes, I posted there yesterday morning when I first noticed some really significant creep on a project. I've got a few other posts in that thread about some things I was trying in an effort to document the shift.Here is the thread: http://www.flightsim-bevs.com/smf_1-0-5/in...hp?topic=1275.0An easy way to get a look at the shifting is to pick a nice N/S line at an airport and line up some objects right on the edge. Then edit the scenery a few times and go back to check the original objects. I tried one, adding objects over a few edits. The first object I placed was at least a foot back from the runway by the fifth edit. Other objects, placed in later revisions, were closer to the edge, but still not in their original spots.