* Vivian Meazza -- Saturday 25 June 2005 19:27:
> Melchior
> > the bo105 doesn't have brakes, so I'm simply polling the brake
> > property and don't have to mess with bindings:
> >
> > m.triggerN = props.globals.getNode("controls/gear/brake-left");
> Wot no rotor brake :-). Cheating - no quick fix there. Another todo - bind
> trigger to key ... sigh.
Setting /ai/submodels/trigger wouldn't work for me, anyway. The bo105 has
8 weapons (6 anti tank rockets, and two M134 miniguns). So I have to have
a dispatcher that polls the brake state and sets the trigger of the currently
selected weapon.
The js trigger is a special key, and one could think about adding one of
the controls wrappers here, too. Driver creators could then use
controls.trigger() on this key and let the aircraft decide what to do
with it. This would still be the user decision and IMHO OK (unlike
redefining a js button directly, which is an absolute no-no).
m.
PS: for those who haven't seen the bo105 shoot: in the CVS version
you can switch through a few civilian and military helicopter versions
with c/C. Those with guns shoot on js trigger/,-key.
_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d
