• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.

    Post 16 Update

    Post 17 Warning

Scenery Quandry!

falcon409

falcon409

SOH-CM-2025
I have a dilemma that I seem to be unable to figure out and I need some expert advice from someone more familiar with this stuff. I am doing an update from the default for KGYI North Texas Regional (formerly Grayson County). The terrain sits at an elevation of 228m (all elevation measurements are done using TCalcX_2). However the AFCAD sits at an elevation of 220m. I went into AFX to change the AFCAD elevation only to find that under "properties" it shows that the airport does in fact sit at an elevation of 228m. Oh and I forgot to mention that this is the "stock" airport, not one that I modded already. So why would a stock airport show one altitude but sit at another?:kilroy:
 
Use 228 Ft. T-Calc sometimes differs slightly with what the Rreference altitude of the airport is, but if you model the new one just a little off, strange things start happening. Unless you're willing to deal with stub files and the like, both the old and new reference altitudes need to match.
 
There is a TCalc003 from 2010, replacing TCalc002. Both the airport tools show 749' for me.

What I use more than anything is the updated for FSX Finney Crosshairs tool. It sits flat and gives accurate reading via the Shift-Z key combo.

Both TCalc003 and the F C tool are at FS Developer.
 
Thanks guys.I think I have that one under control now and moving on to another one I'm running into more and more. . . . .airports that are situated on uneven ground. So uneven that any "even" altitude flatten will leave a rising cliff in one area and a steep drop off in another. North Texas Regional sits at the bottom of what probably figures to be about a 100'+ slope on the east side and then tapers off to the west and north and rises again to the south. An ordinary flatten looks ridiculous so I'm going to try stepping several flattens of varying elevations in those areas either up or down to see if I can get a reasonable taper to the terrain rather than just abrupt cliffs.
 
falcon409 said:
An ordinary flatten looks ridiculous so I'm going to try stepping several flattens of varying elevations in those areas either up or down to see if I can get a reasonable taper to the terrain rather than just abrupt cliffs.
Click to expand...

SBuilderX is way more versatile than AFX for creating flattens IMHO... You can even make slopes to blend in to the local terrain - takes a bit of time and patience though! :salute:
 
Dave Torkington said:
SBuilderX is way more versatile than AFX for creating flattens IMHO... You can even make slopes to blend in to the local terrain - takes a bit of time and patience though! :salute:
Click to expand...
Dave I am using SBuilderX for the flattens. I only use AFX to handle the AFCAD work.:salute:
 
You must log in or register to reply here.
Back
Top