Re: [Flightgear-devel] Braking chutes

2008-10-08 Thread gerard robin
On mercredi 08 octobre 2008, AJ MacLeod wrote: > On Wednesday 08 October 2008 10:16:28 gerard robin wrote: > > Hello AJ > > Thanks > > What about SpeedBrake, which could be used instead of it with some > > particular Aircraft (BlackBird) won't it be better to have a wrapper too > > ? > > Hi Gerard

Re: [Flightgear-devel] Braking chutes

2008-10-08 Thread AJ MacLeod
On Wednesday 08 October 2008 10:16:28 gerard robin wrote: > Hello AJ > Thanks > What about SpeedBrake, which could be used instead of it with some > particular Aircraft (BlackBird) won't it be better to have a wrapper too ? Hi Gerard, Yes, definitely; actually I had a simple one in my own contr

Re: [Flightgear-devel] Braking chutes

2008-10-08 Thread AJ MacLeod
On Wednesday 08 October 2008 10:06:38 James Turner wrote: > What about multiplayer (claim one of the network shared properties?), > and re-setting the chute for the next take off? Does chuteDeploy(0) > specify a reset? I deliberately didn't include a reset in the spec, because AFAIK that's not som

Re: [Flightgear-devel] Braking chutes

2008-10-08 Thread gerard robin
On mercredi 08 octobre 2008, gerard robin wrote: > On mercredi 08 octobre 2008, AJ MacLeod wrote: > > Hi all (aircraft developers in particular), > > > > As you might have noticed from the commits list, there was a "wrapper > > function" added to controls.nas last night for braking chutes. > > > >

Re: [Flightgear-devel] Braking chutes

2008-10-08 Thread gerard robin
On mercredi 08 octobre 2008, AJ MacLeod wrote: > Hi all (aircraft developers in particular), > > As you might have noticed from the commits list, there was a "wrapper > function" added to controls.nas last night for braking chutes. > > As things stand, it is practically impossible to asssign brakin

Re: [Flightgear-devel] Braking chutes

2008-10-08 Thread James Turner
On 8 Oct 2008, at 09:50, AJ MacLeod wrote: > PLEASE modify your aircraft to use the controls.chuteDeploy function - > override it to your heart's content in your own model. All you need > to > ensure is that controls.chuteDeploy(1) deploys the chute and > controls.chuteDeploy(-1) jettisons the