|
From: Jon S. <li...@st...> - 2006-04-18 16:12:06
|
Ralf Gerlich wrote: > Hi, > > Chris Metzler schrieb: >> Well, I did mention this over there earlier, in the second paragraph of: >> >> http://mail.flightgear.org/pipermail/terragear-devel/2006-March/001355.html >> >> >> but however you saw it, I'm very glad, because . . . > > I saw it in both lists, but the memory about me seeing the same problem > in my first scenery building attempts sunk in after I read it in > flightgear-devel. > >>> If anything else doesn't work, I suspect that it doesn't have >>> anything to do with this. >> >> >> Bingo! This not only stopped the odd non-Latin-1 characters to the >> screen, but it solved the problem with hgtchop. I am able to proceed >> to the end of the tool chain and build tiles! > > Huh?! I don't know how this small issue (char printing) could break the > whole building process...but nevertheless: if it works, it works ;-) > >> The next problem (which I'll post over there): the cutouts for the >> airports place the airports at sea level. >> >> http://www.speakeasy.org/~cmetzler/KSDF_pit.jpg >> >> But while I want to get this fixed at some point, right now I'm able >> to do what I most need to do, which is review airports I've worked on >> in TaxiDraw. > > This looks as if you ran hgtchop after genapts. Maybe it's even > necessary to run terrafit before genapts (hgtchop, terrafit, genapts, > fgfs-construct). *always* fully process your DEM before you start basing other stuff on it. there's no need to run arrayfit - but it will get rid of a lot of "redundant" data. It's worth the time spent processing it. Then *back up the result* you won't need to go back to that step until newer DEM data is released. Once you're at that stage you can happily run genapts, build some scenery, then throw it away and build a newer version. -- Jon Stockill li...@st... |