James Turner wrote:
>
> On 5 Sep 2008, at 17:21, James Turner wrote:
>
>> Yep, that's quite a likely source - thanks for the help, I'll work out
>> from this.
>
> Got it.
>
> If someone could kindly apply the attached patch, that'll keep this
> from crashing, I believe. The fix is easy since FGAir
On 5 Sep 2008, at 17:21, James Turner wrote:
Yep, that's quite a likely source - thanks for the help, I'll work out
from this.
Got it.
If someone could kindly apply the attached patch, that'll keep this
from crashing, I believe. The fix is easy since FGAirport can now
always provide an a
On 5 Sep 2008, at 15:24, Csaba Halász wrote:
> Well, I had that disabled so I couldn't reproduce the bug either. But
> enabling it indeed resulted in a crash.
> Problem seems to be in AILocalTraffic.cxx, marked as TODO:
>
> void FGAILocalTraffic::GetRwyDetails(const string& id) {
>//cout
On Fri, Sep 5, 2008 at 7:30 AM, Durk Talsma <[EMAIL PROTECTED]> wrote:
>
> Could you check whether you have the old AI traffic enabled? Check for
>
>
> false
> 1
>
>
> in preferences.xml. If this is set to true, please try changing it to false,
> and check whether that makes a difference.
On 5 Sep 2008, at 09:09, James Turner wrote:
> Just to be clear, what are the
> exact steps to reproduce the crash? If you're using fgrun, I really
> need to see the actual command line passed to fgfs.
Just tried locally with ./fgfs --airport=LFPN, and I don't crash, very
strange.
And checkin
On 5 Sep 2008, at 07:30, Durk Talsma wrote:
> Your bug report reminds me of a similar one that was reported a few
> weeks ago.
> We recently overhauled the runway search code, and in the process it
> is
> possible that either a new bug was introduced, or that the new code
> exposed
> existi
Hi Michael,
I am currrently working on a relatively limited internet connections, but let
me weight in and add a few comments below.
On Friday 05 September 2008 01:18:24 Michael Smith wrote:
> Anders Gidenstam wrote:
> > But the problem could also be triggered by some other piece of code that
>
Anders Gidenstam wrote:
> On Thu, 4 Sep 2008, Michael Smith wrote:
>
>
>> Hmm, did you specfiy the runway when you started?
>> And why does it take so long for it to load? it only takes 30 seconds to
>> load at any airport (iirc, fgrun slowed things down alot so that might
>> be it.).
>> Say aga
On Thu, 4 Sep 2008, Michael Smith wrote:
> Hmm, did you specfiy the runway when you started?
> And why does it take so long for it to load? it only takes 30 seconds to
> load at any airport (iirc, fgrun slowed things down alot so that might
> be it.).
> Say again how to turn the traffic manager of
On ven 5 septembre 2008, Michael Smith wrote:
> gerard robin wrote:
> > On jeu 4 septembre 2008, Martin Spott wrote:
> >> Anders Gidenstam wrote:
> >>> On Thu, 4 Sep 2008, Martin Spott wrote:
> Hmmm, I don't get a segfault here (Debian Etch/AMD64) but a 'hang on
> startup'.
> >>>
> >>> Ar
gerard robin wrote:
> On jeu 4 septembre 2008, Martin Spott wrote:
>
>> Anders Gidenstam wrote:
>>
>>> On Thu, 4 Sep 2008, Martin Spott wrote:
>>>
Hmmm, I don't get a segfault here (Debian Etch/AMD64) but a 'hang on
startup'.
>>> Are you sure it is a hang? On
On jeu 4 septembre 2008, Martin Spott wrote:
> Anders Gidenstam wrote:
> > On Thu, 4 Sep 2008, Martin Spott wrote:
> > > Hmmm, I don't get a segfault here (Debian Etch/AMD64) but a 'hang on
> > > startup'.
> >
> > Are you sure it is a hang? On my (admittedly less powerful system) FG
> > needed more
Anders Gidenstam wrote:
> On Thu, 4 Sep 2008, Martin Spott wrote:
> > Hmmm, I don't get a segfault here (Debian Etch/AMD64) but a 'hang on
> > startup'.
>
> Are you sure it is a hang? On my (admittedly less powerful system) FG
> needed more than 8 minutes to start. LFPN is close to Paris... :)
On Thu, 4 Sep 2008, Martin Spott wrote:
> Michael Smith wrote:
>
>> No good. Its not just starting there, if I start at LFPG then fly over
>> LFPN it seg faults with that message.
>
> Hmmm, I don't get a segfault here (Debian Etch/AMD64) but a 'hang on
> startup'.
Are you sure it is a hang? On my
Michael Smith wrote:
> No good. Its not just starting there, if I start at LFPG then fly over
> LFPN it seg faults with that message.
Hmmm, I don't get a segfault here (Debian Etch/AMD64) but a 'hang on
startup'.
When starting at any of these two for example with "--log-level=debug"
I get tons
Martin Spott wrote:
> Michael Smith wrote:
>
>
>> Fatal error: unknown runway 00 at airport:LFPN
>> (received from FGAirport::getRunwayByIdent)
>> Segmentation fault
>>
>
> Simple question (I don't claim that I'd be able to provide a fix), does
> the simulation start properly when you ente
Michael Smith wrote:
> Fatal error: unknown runway 00 at airport:LFPN
> (received from FGAirport::getRunwayByIdent)
> Segmentation fault
Simple question (I don't claim that I'd be able to provide a fix), does
the simulation start properly when you enter a valid runway, say 07L/R,
25R/L ?
Greetings, This is my first post to the FG-Devel mailing list.
I have a problem when I fly at or near LFPN. This is the output:
[EMAIL PROTECTED]:~/CVS/sources/flightgear$ src/Main/fgfs --airport=LFPN
Model Author: Unknown
Creation Date: 2002-01-01
Version: $Id: c172p.xml,v 1.19 2008/0
18 matches
Mail list logo
