Victhor wrote
> I use CVS data and source. It could be a simple conflict in the
> nimitz_demo.xml file.
> > Victhor wrote
> >
> > >
> > > The nimitz_demo one just said(even with --log-level=debug) that
> > > nimitz_demo failed to load. The traffic manager one happened after it
> > > displayed a m
I use CVS data and source. It could be a simple conflict in the
nimitz_demo.xml file.
> Victhor wrote
>
> >
> > The nimitz_demo one just said(even with --log-level=debug) that
> > nimitz_demo failed to load. The traffic manager one happened after it
> > displayed a message that it had found a par
Victhor wrote
>
> The nimitz_demo one just said(even with --log-level=debug) that
> nimitz_demo failed to load. The traffic manager one happened after it
> displayed a message that it had found a parking position for an AI
> plane, but it wasn't an error.
> > Hi Vithor,
> >
> > On Sunday 26 April
The nimitz_demo one just said(even with --log-level=debug) that
nimitz_demo failed to load. The traffic manager one happened after it
displayed a message that it had found a parking position for an AI
plane, but it wasn't an error.
> Hi Vithor,
>
> On Sunday 26 April 2009 00:27:02 Victhor wrote:
>
Hi Vithor,
On Sunday 26 April 2009 00:27:02 Victhor wrote:
> I updated my copy of FlightGear CVS today, and noticed two bugs. I
> started FG, but it would crash with a segmentation fault error. I set
> the log level to debug and found out that it was having trouble with
> nimitz_demo.xml, so I rem
I updated my copy of FlightGear CVS today, and noticed two bugs. I
started FG, but it would crash with a segmentation fault error. I set
the log level to debug and found out that it was having trouble with
nimitz_demo.xml, so I removed it. Soon FG worked normally, but would
crash soon after. As I s
6 matches
Mail list logo
