Re: [Flightgear-devel] terragear-cs unknown runway surface/ segfault

2011-04-17 Thread Martin Spott
Christian Schmitt wrote: > Martin Spott wrote: >> http://mapserver.flightgear.org/Heliport.pl >> > > Well, I'd rather get it right in genapts [...] Sure, would be preferred. The above is just a quick hack (but functional) and was meant as a hint to which places might be worth looking at. > [

Re: [Flightgear-devel] terragear-cs unknown runway surface/ segfault

2011-04-17 Thread Christian Schmitt
Martin Spott wrote: > > http://mapserver.flightgear.org/Heliport.pl > Well, I'd rather get it right in genapts and I'm sure it's not too difficult to accomplish. Chris -- Benefiting from Server Virtualization: Beyo

Re: [Flightgear-devel] terragear-cs unknown runway surface/ segfault

2011-04-17 Thread Christian Schmitt
Martin Spott wrote: >> After that genapts segfaulted during EGKK processing [...] > > Did you use the 'public' apt.dat file from MapServer ? Yes, indeed. I hope i'll be able to really get down to the problem today. I still have no exact clue what caused it, although I recompiled with several

Re: [Flightgear-devel] terragear-cs unknown runway surface/ segfault

2011-04-17 Thread Martin Spott
Martin Spott wrote: > I don't remember all the details from the top of my head, but I'm > pretty certain that processing heliports requires a few more changes. I > usually pre-process the 'apt.dat' files, making simple tarmac from the > helipad squares (thus loosing the "helipad"-tag, but better t

Re: [Flightgear-devel] terragear-cs unknown runway surface/ segfault

2011-04-17 Thread Martin Spott
Hi Christian, Christian Schmitt wrote: > I encountered "unknown runway surface" errors, caused by some strange > heliport runways (see EGTG). I created a patch to circumvent this for now: > https://gitorious.org/papillon81/terragear- > cs/commit/263a1cdd537bd07e2d5a503b38043f8faee29e38 I don't