RE: [Flightgear-devel] Re: Segfault from todays CVS

2005-02-20 Thread Vivian Meazza
Melchior FRANZ wrote

 
 * Vivian Meazza -- Saturday 19 February 2005 19:18:
  I'm not sure that the Nimitz version in cvs has cats.
 
 It has. Used them to launch the seafire after my second successful
 landing.
 Worked pretty well. Those didn't use cats in RL, did they? I mean, without
 single nose gear ...?
 

And here's how it looked:

http://myweb.tiscali.co.uk/vmeazza/FlightGear/Hellcat_cat.jpg 

The photo was taken aboard HMS Empress towards the end of the war in the
Pacific.

Regards,

Vivian





___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


RE: [Flightgear-devel] Re: Segfault from todays CVS

2005-02-19 Thread Vivian Meazza
Melchior FRANZ wrote

 
 * Vivian Meazza -- Saturday 19 February 2005 19:18:
  I'm not sure that the Nimitz version in cvs has cats.
 
 It has. Used them to launch the seafire after my second successful
 landing.
 Worked pretty well. Those didn't use cats in RL, did they? I mean, without
 single nose gear ...?
 

Yes they did - hydraulic! They used a wire strop which attached to catapult
'spools' (hooks) on the fuselage. Free takeoff was the norm, however.

You can read a detailed account:

http://www.fiddlersgreen.net/AC/aircraft/Supermarine-Seafire/sea-info/sea_in
fo.htm

Regards,

Vivian





___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] Re: segfault in SimGear code

2005-02-14 Thread Ron Lange
Hi Melchior,
I forgot to mention that the segfault occured with sdl disabled...after 
enabling sdl I can also start up (also not with the heli ;-)

I also think that the command line handling should be redesigned, but 
may be it is a hint to a consistence problem during threading.

Regards
Ron

Melchior FRANZ schrieb:
* Ron Lange -- Monday 14 February 2005 10:29:
 

Can anyone also cause this segfault by using with an .fgfsrc containing 
just one line

--airport=EDHI --aircraft=bo105 --enable-game-mode
   

It issues two warnings:
 Failed to find runway 28R at airport EDHI --aircraft=bo105 --enable-game-mode
 Failed to find a good runway for EDHI --aircraft=bo105 --enable-game-mode
but runs fine otherwise. Not with the bo105, though. But then it crashes on
exit.
If I had to fix this, I would start with making the config file scanner read
all parameters into an STL vector, allowing more than one parameter per line.
The file wouldn't have to be read more than once (as it's done now) and the
crash would probably not occur any more. Fixing the code that crashes now
is only curing symptoms and IMHO a waste of time. This code is innocent.
m.

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
 


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] RE: Segfault

2004-10-16 Thread Durk Talsma
Dave, 

Looks like you are right: I also got these segfaults. Works again now.

However, I discovered that the new version of the usb-pro-yoke.xml file undoes 
a few changes I submitted early summer. I changed the behavior of the flap 
switch to match it with how the keyboard handles it. Could we please add this 
part back in?

button n=6
  repeatablefalse/repeatable
  binding
   commandnasal/command
   scriptcontrols.stepFlaps(-1)/script
  /binding
/button
 
button n=7
  repeatablefalse/repeatable
  binding
   commandnasal/command
   scriptcontrols.stepFlaps(1)/script
  /binding
/button


I've attached the modified file for those who want to try it out. 

Cheers,
Durk

On Saturday 16 October 2004 05:32, Dave Perry wrote:
 The cause of the segfault was the replacement of pro-yoke-usb.xml in CVS
 with a windows edit (moving the hat axes up by one which breaks linux).
 So I edited the new file with

   number
  unix5/unix
  windows6/windows
   /number
 and a similar edit for axis 6/7.

 I tested the edit with today's cvs in linux and the recent windows 9.6
 binary.  One caution.  It seems that the propeller and mixture may have
 their axis interchanged between versions of the CH usb yokes.
 Would the person who changed this file in cvs please post the name that
 js_demo gives for his yoke.  If his is different than mine, then using
 name  ...  /name, we could have two different files that
 have the right propeller and mixture axis for both.

 Also, I am attaching the edited pro-yoke-usb.xml file.  It would be an
 improvement for both linux and windows users if this were added to cvs.
 Regards,
 Dave Perry
?xml version=1.0 encoding=UTF-8?
PropertyList

 nameCH PRODUCTS CH FLIGHT SIM YOKE USB /name
 nameCH FLIGHT SIM YOKE USB /name

 axis n=0
  descAileron/desc
  binding
   commandproperty-scale/command
   property/controls/flight/aileron/property
   power2.0/power
  /binding
 /axis

 axis n=1
  descElevator/desc
  binding
   commandproperty-scale/command
   property/controls/flight/elevator/property
   factor type=double-1.0/factor
   power2.0/power
  /binding
 /axis

 axis n=2
  descThrottle/desc
  binding
   commandproperty-scale/command
   property/controls/engines/engine[0]/throttle/property
   offset type=double-1.0/offset
   factor type=double-0.5/factor
  /binding
  binding
   commandproperty-scale/command
   property/controls/engines/engine[1]/throttle/property
   offset type=double-1.0/offset
   factor type=double-0.5/factor
  /binding
  binding
   commandproperty-scale/command
   property/controls/engines/engine[2]/throttle/property
   offset type=double-1.0/offset
   factor type=double-0.5/factor
  /binding
  binding
   commandproperty-scale/command
   property/controls/engines/engine[3]/throttle/property
   offset type=double-1.0/offset
   factor type=double-0.5/factor
  /binding
  binding
   commandproperty-scale/command
   property/controls/engines/engine[4]/throttle/property
   offset type=double-1.0/offset
   factor type=double-0.5/factor
  /binding
  binding
   commandproperty-scale/command
   property/controls/engines/engine[5]/throttle/property
   offset type=double-1.0/offset
   factor type=double-0.5/factor
  /binding
  binding
   commandproperty-scale/command
   property/controls/engines/engine[6]/throttle/property
   offset type=double-1.0/offset
   factor type=double-0.5/factor
  /binding
  binding
   commandproperty-scale/command
   property/controls/engines/engine[7]/throttle/property
   offset type=double-1.0/offset
   factor type=double-0.5/factor
  /binding
 /axis
axis n=4
  descMixture/desc
  binding
   commandproperty-scale/command
   property/controls/engines/engine[0]/mixture/property
   offset type=double-1.0/offset
   factor type=double-0.5/factor
  /binding
  binding
   commandproperty-scale/command
   property/controls/engines/engine[1]/mixture/property
   offset type=double-1.0/offset
   factor type=double-0.5/factor
  /binding
 /axis
axis n=3
  descPropeller/desc
  binding
   commandproperty-scale/command
   property/controls/engines/engine[0]/propeller-pitch/property
   offset type=double-1.0/offset
   factor type=double-0.5/factor
  /binding
  binding
   commandproperty-scale/command
   property/controls/engines/engine[1]/propeller-pitch/property
   offset type=double-1.0/offset
   factor type=double-0.5/factor
  /binding
 /axis

  axis
  descView Direction/desc
  number
unix5/unix
windows6/windows
  /number
  low
   repeatabletrue/repeatable
   binding
commandproperty-adjust/command
property/sim/current-view/goal-heading-offset-deg/property
step type=double2.0/step
   /binding
  /low
  high
   repeatabletrue/repeatable
   binding
commandproperty-adjust/command
property/sim/current-view/goal-heading-offset-deg/property
step type=double-2.0/step
   /binding
  /high
 /axis

 axis
  number
unix6/unix
windows7/windows
  /number
  descView Elevation/desc
  low
   repeatabletrue/repeatable
   binding

Re: [Flightgear-devel] RE: Segfault

2004-10-16 Thread Erik Hofman
Durk Talsma wrote:
Dave, 

Looks like you are right: I also got these segfaults. Works again now.
However, I discovered that the new version of the usb-pro-yoke.xml file undoes 
a few changes I submitted early summer. I changed the behavior of the flap 
switch to match it with how the keyboard handles it. Could we please add this 
part back in?

The cause of the segfault was the replacement of pro-yoke-usb.xml in CVS
with a windows edit (moving the hat axes up by one which breaks linux).
Joystick configuration files are becoming a nightmare.
I've added Dave Perry as the maintainer in the header of the file, so 
every proposed change to this file will be sent to him prior to inclusion.

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