[Flightgear-devel] cvs broken now and log-level doc issue

2004-07-22 Thread Jim Wilson
Just tried CVS and we're aborting right after the log entry for Traffic Manager.

BTW I noticed in the command line help we're showing 0=verbose, 5=alerts
only,  but I think the numbers do not apply.  I'd change it,  but I'm not
100% sure what all the log-level options are.

Best,

Jim


___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel


Re: [Flightgear-devel] cvs broken now and log-level doc issue

2004-07-22 Thread Durk Talsma
I just saw this overhere as well, although I didn't check the log files so 
carefully. This is probably caused by a the missing aircraft, because I don't 
see this in my CVS version. 

The short term solution is going to be that we're removing MD-11 traffic.

Cheers,
Durk

On Thursday 22 July 2004 21:53, Jim Wilson wrote:
 Just tried CVS and we're aborting right after the log entry for Traffic
 Manager.

 BTW I noticed in the command line help we're showing 0=verbose, 5=alerts
 only,  but I think the numbers do not apply.  I'd change it,  but I'm not
 100% sure what all the log-level options are.

 Best,

 Jim


 ___
 Flightgear-devel mailing list
 [EMAIL PROTECTED]
 http://mail.flightgear.org/mailman/listinfo/flightgear-devel


___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel


RE: [Flightgear-devel] cvs broken now and log-level doc issue

2004-07-22 Thread Vivian Meazza

Jim Wilson wrote

 Sent: 22 July 2004 20:54
 To: [EMAIL PROTECTED]
 Subject: [Flightgear-devel] cvs broken now and log-level doc issue
 
 Just tried CVS and we're aborting right after the log entry for Traffic
 Manager.
 
 BTW I noticed in the command line help we're showing 0=verbose, 5=alerts
 only,  but I think the numbers do not apply.  I'd change it,  but I'm not
 100% sure what all the log-level options are.
 

cvs seems to be broken when compiling and running under Cygwin. Using Norman
Vine's OpenAL files SimGear and FlightGear compile without error. On running
I get:

Initializing OpenAL sound manager
Unknown exception in the main loop. Aborting...
Segmentation fault (core dumped)

WAG - we need an update to Norman' files.

I'm investigating some more.

Regards,

Vivian



___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel


Re: [Flightgear-devel] cvs broken now and log-level doc issue

2004-07-22 Thread Jim Wilson
Durk Talsma said:

 I just saw this overhere as well, although I didn't check the log files so 
 carefully. This is probably caused by a the missing aircraft, because I don't 
 see this in my CVS version. 
 
 The short term solution is going to be that we're removing MD-11 traffic.
 

I don't see any traffic files at all so maybe that is the problem.  It looks
like it all got removed on the last update.

Best,

Jim


___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel


Re: [Flightgear-devel] cvs broken now and log-level doc issue

2004-07-22 Thread Durk Talsma

 I don't see any traffic files at all so maybe that is the problem.  It
 looks like it all got removed on the last update.


I do see them in fgfs-base-0.9.5-pre2. In data/Traffic. Are you referring to 
CVS or to the pre-release. Erik has commited a few changes just about a few 
hours ago (thanks BTW, Erik). And I haven't had a chance to update CVS. 

I'll it's getting late here, so I'll check tomorrow.

Cheers,
Durk


___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel


Re: [Flightgear-devel] cvs broken now and log-level doc issue

2004-07-22 Thread Durk Talsma
On Thursday 22 July 2004 22:37, Vivian Meazza wrote:

 Initializing OpenAL sound manager
 Unknown exception in the main loop. Aborting...
 Segmentation fault (core dumped)

That's actually a message indicating that the AIModel subsystem can't find a 
model. I'm not yet sure how to handle this best. Probably it should revert to 
loading the default glider model. 

Cheers,
Durk


___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel


Re: [Flightgear-devel] cvs broken now and log-level doc issue

2004-07-22 Thread Frederic Bouvier
Durk Talsma wrote:


  I don't see any traffic files at all so maybe that is the problem.  It
  looks like it all got removed on the last update.
 

 I do see them in fgfs-base-0.9.5-pre2. In data/Traffic. Are you referring
to
 CVS or to the pre-release. Erik has commited a few changes just about a
few
 hours ago (thanks BTW, Erik). And I haven't had a chance to update CVS.

 I'll it's getting late here, so I'll check tomorrow.

Apparently, TrafficManager is complaining because Traffic/KLM/KLM.xml
is missing

-Fred



___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel


RE: [Flightgear-devel] cvs broken now and log-level doc issue

2004-07-22 Thread Vivian Meazza


Durk Talsma wrote

 Sent: 22 July 2004 22:09
 To: FlightGear developers discussions
 Subject: Re: [Flightgear-devel] cvs broken now and log-level doc issue
 
 On Thursday 22 July 2004 22:37, Vivian Meazza wrote:
 
  Initializing OpenAL sound manager
  Unknown exception in the main loop. Aborting...
  Segmentation fault (core dumped)
 
 That's actually a message indicating that the AIModel subsystem can't find
 a
 model. I'm not yet sure how to handle this best. Probably it should revert
 to
 loading the default glider model.
 

That's good news, I think. Glider model would be fine, at least in the short
term.
 
Regards,

Vivian



___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel


Re: [Flightgear-devel] cvs broken now and log-level doc issue

2004-07-22 Thread Frederic Bouvier
Frederic Bouvier wrote:

 Durk Talsma wrote:

 
   I don't see any traffic files at all so maybe that is the problem.  It
   looks like it all got removed on the last update.
  
 
  I do see them in fgfs-base-0.9.5-pre2. In data/Traffic. Are you
referring
 to
  CVS or to the pre-release. Erik has commited a few changes just about a
 few
  hours ago (thanks BTW, Erik). And I haven't had a chance to update CVS.
 
  I'll it's getting late here, so I'll check tomorrow.

 Apparently, TrafficManager is complaining because Traffic/KLM/KLM.xml
 is missing

There is an exception thrown by the property system when a file is not
present. The exception is of type 'sg_io_exception' and it would be nice
is there was a try {} catch {} around the functions that try to read a
XML file.

-Fred



___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel


Re: [Flightgear-devel] cvs broken now and log-level doc issue

2004-07-22 Thread Frederic Bouvier
 Apparently, TrafficManager is complaining because Traffic/KLM/KLM.xml
 is missing

Traffic/UAL/UAL.xml is also not there.

-Fred



___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel


Re: [Flightgear-devel] cvs broken now and log-level doc issue

2004-07-22 Thread Ampere K. Hardraade
I think it will be a good idea to identify what file(s) are missing before 
aborting.  Loading the glider is just a waste of time.

Regards,
Ampere

On July 22, 2004 05:08 pm, Durk Talsma wrote:
 That's actually a message indicating that the AIModel subsystem can't find
 a model. I'm not yet sure how to handle this best. Probably it should
 revert to loading the default glider model.

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel