The Choctaw Navy Outlying Field - KNFJ - is now the highest mountain in the state of Florida - with an elevation of 359 ft (109.1M) - higher than the real highest elevation in the state of Britton Hill which is 345 ft / 105MLooks like the elevation in feet - 109 - got entered as meters in FSX.I never did learn how to fix such issues in FS2004.KNFJ is NFJ in FS2004 and is located across the bay due east of Pensacola and south of Milton FL.

Do you mean an airport elevation? If so, then the error is due to the data source - Jepp in FS 9 and perhaps the F.A.A. in FS X.It needs a simple flatten, Reggie, easy to make with any number of scenery or flatten tools.Best regards.Luis

I would hope the FAA data is not off by that much. A lot of us use it over Jepp.

The data source - Jeppesen current and Spring 2005 which I also have is 109 feet - FSX is 109 METERS.Flattens never resolved the X34 "fake airport" issue just north of KMLB - thankfully that airport is no longer duplicated FSX and is in it's correct location. Of course I was trying to remove the airport and the 118 ft ASL hill completely.

R, you might want to email that to [email protected] or whatever the email address is... (can't remember)Hopefully they know about these types of errors in the database but I'm not sure. There are also a lot of mesh spikes in the beta, I hope they go through those as well, but I know that takes time and I am not sure if that will be done.RhettAMD 3700+, eVGA 7800GT 256, ASUS A8N-E, PC Power 510 SLI, 2 GB Corsair XMS 3-3-3-8, etc. etc.

Oh well, Reggie, I was certainly not very complete in my answer.The problem has to do most certainly with the airport elevation, whether somewhere near Melbourne or anywhere else.There are 2 distinct files that determine the elevation - the airport flatten that is in a FL file, and the airport file that contains the reference altitude and that can be found in the AP files.To modify the altitude of an airport, you must necessarily change the elevation in both files.To change a flatten elevation, you can just make a new flatten. No problem.But, Microsoft did not provide any method for changing the airport reference altitude in the AP. There is no "DeleteAirportElevation" key in BGLComp.You can create a new AP in AFCAD with a different altitude, but FS will always use the elevation from the first AP file it finds, and this is always the default.There are ways to make this work. Jackie Brouze provides his JABBgl (available in the Avsim library), a tool that changes the elevation value directly in the AP file. Contrary to what some people think, JABBgl does not decompile the AP file at all. No information (approaches) is lost in this way. All that it does is to write the new value to the file.But, there are also other ways to do the same thing.We have extensively discussed this matter and you can find the gist of it here:http://forums.avsim.net/dcboard.php?az=sho...ing_type=searchUnfortunately, FS X will not have a "DeleteAirportElevation" key either (I think), so everyone who wishes to change an airport elevation should familiarize themselves with these methods.Best regards.Luis

I was being a little facitious.I've been making airport elevation change files with XML successfully for almost 2 1/2 years now - about six months before thread in your reference.Changing the airport elevation - all three different values which FS2004 uses - is relatively simple.Though I still don't understand why so many people want to ignore Microsoft's recommendations on where to place files.JABBGL does a good job and is very clean, but (1) how many modifications have to be made to a single APnnnnn.bgl file, and (2) I think it an extremely poor practice to distribute a modified default file.If you modify ONE airport, you certainly do not want 100 other airports in the file.I've used flattens to bring airports scenery up or down to match the airport elevation.X34 defeated my efforts. Don't know why.One misperception I noted in the thread - that FS uses the first elevation it reads for an airport.There are three different times that FS reads the airport elevation if you have AI, and all three can return different values if the files have different elevations.That is why parked AI, just landed AI and the User aircraft can all have different elevations.

Gee, Considering that Florida is the epitome of flatness I always thought the highest mountain in Florida was in a well known theme park and called "Space Mountain". Ha! Ha! Ha!Regards, Carlos

Thank you for the correction, Reggie, very kind of you.I had not realized that elevation values for airports were stored in 3 distinct places. It would be highly appreciated by scenery designers if you could give more details, as we had not known this.Normally, I do not take a look at other people's scenery problems, since I have enough in my own projects. But, you have raised a doubt in my mind; after all, anyone can make a mistake.So, I took a look at your problematic X34 - Sheets airfield. Here is a picture of the default, looking South towards Melbourne:http://forums.avsim.net/user_files/155855.jpgYou can distinguish the fuel trigger for Melbourne in the distance.As far as we had known in scenery design, elevation values for airports are only found in the FL (flatten) file and AP (the airport file). So, I went ahead and removed the default FL and AP for this airport. Since the very Northern tip of this airfield extends into a different file, I removed 2 of each, that is, AP926210, AP926220, FL926210, and FL926220 and this is the result:http://forums.avsim.net/user_files/155856.jpgThe problem plateau is gone, totally wiped out. You can still see the AB (airport background) because, of course, I did not remove that file.So, it seems clear that the only places with airport elevation are AP and FL. Simply modify those files and the problem is solved. You will find a full discussion of this that we had 2 years ago in the link mentioned above.Personally, I favor Jacky's JABBgl since it is a straightforward and simple solution. But, it is also possible to use Dick Ludowise's solution of creating a small file with only the basic facilities information and placing that below the default. Be warned, however, that this has created unexplainable problems for numerous users.There is nothing particularly complicated about Flight Simulator, in the sense that there are no hidden tricks waiting to create problems. Everything is pretty straightforward once all the elements are understood. This does not mean that FS is not complex; on the contrary, there is a lot going on in there, but it is all perfectly understandable.Forgive me for not providing you with a fix for this problem, but with this information, you should be able to do it yourself. If you do have any questions or problems, please do not hesitate to ask in the scenery forum, where there is always somebody willing to help.As for distributing these modified files that replace the default, I have the same reservations as you, and am probably one of the few, if not the only, scenery designer who has them. Nonetheless, all the great scenery packages of the last 3 years do precisely that, from Holger's astonishing stuff to the FreeFlow scenery - they all either replace parts of default (AB, FL, HL, HP, RD, ST, UT) or the entire thing with a corrected version.Since the AP files have exactly the same coverage as those other terrain scenery files, there does not seem to be any particular reason why they should be somehow any different as to distribution of modifications.In this particular case of an airfield, X34, that should not even be there, it seems evident that there is even less reason to hesitate, as the default is just wrong and a replacement would simply be correcting it.I may be mistaken, but it seems to me that Scott has even provided precisely this fix for some duplicate airports in the FreeFlow Florida coverage, perhaps even this particular airfield. But, my memory of this is hazy as I did not install that fix.In any case, it is all just code, and no matter what problem is created by distributing them is extremely easy to fix.Best regards.Luis

Okay - I see that was my main problem - two FL files covering the airport.Re: Elevations:FS reads the "floor" as Jim Vile describes in the lowest default scenery file level. This is the elevation where AI aircraft are placed if they are initialized in parking spots at the airport.Later FS reads the addon AFCAD / addon Scenery elevation and the highest level - and that is the elevaiton used to place the user aircraft.When AI aircraft land - their elevation and parking elevation is the runway elevation of any addon AFCAD or other scenery file used to create the runway.You can see how an addon scenery set to one airport base elevation - with the runways, ILS, start locations created at 100 ft, an AFCAD where a user changes the elevation to 95 feet, and a base elevation in APnnnnn.bgl file of 90 ft can create varying aircraft at different levels.The SceneryWorld folder is lowest level in FS9 and must remain so. The SceneryBase must remain second, then the individual regions, then the SceneryGeneric folder.This will be more important in FSX if it carries forward with the FSX beta structure of dozens more scenery folders.No one should ever alter the order of the default scenery setting in the scenery.cfg - everything else we place in the system should be above/ after the default. Moving them around messes with additional program in FS and leads to problems.Of course we also know no one should ever edit a scenery.cfg - that changes needs to be saved in a NewScenery.cfg file, which FS will integrate the next time it boots.Editing the scenery.cfg causes the scenery.dat cache files to get messed up and out of sequence, which leads to all sorts of strange behaviors until the scenery caches are completely rebuilt.One major problem I have with distributing APnnnnn.bgl files is that they frequently erase modifications people have made to other airports with JABBGL.This was a significant issue with some addon sceneries in the northeast US a couple years ago.Also, I'm very wary of some sceneries which distribute those files which have decompiled and recompiled the file. Which usually destroys the airspace information and the approach system.