Am Samstag, den 16.12.2006, 15:54 +0100 schrieb Melchior FRANZ: > * alexis bory -- Saturday 16 December 2006 15:13: > > controls.trigger() is not used in aircrafts, but overwritten by MiG15 [...] > > Which is perfectly fine. See below. > > > > > - some use ',' as a gun/missile trigger depending of the variant choosed > > (bo105). > > Yes, but that's only the half truth. > > It's true that there are no standard *bindings* to trigger weapons, > but triggering itself *is* standardized and was respected by all > aircraft in CVS last time I checked. There's only an "obligation" > for bindings(!) to use controls.trigger(). This sets property > /controls/armament/trigger by default. It is up to the aircraft > to *either* listen to this property *or* to redefine controls.trigger() > to do whatever they want. Both is 'legal'. > > The bo follows this standard, too. If anyone has a <binding> that > calls controls.trigger() (which the Saitek/Cyborg does; see > "Menu->Help->Joystick Info"), then the weapons fire. But as the bo105 > doesn't have wheels/brakes, the default js fire button would otherwise > be unused, and so it's used to trigger, *too*. And there's no reason > to change that, even *if* we have a standardized key binding. > > Joysticks can hardly be standardized. There are some around with only > one button, and it's up to the joystick driver's author to assign > sensible functions. All that we can do is offer useful controls.*() > wrapper functions. For now there's controls.trigger() and > controls.weaponSelect(). Suggestions for more are welcome. > > So the only question remains: should there be a standard *key* for > weapon trigger (I'd say yes), and if so, where. > agreed, I took the e key for the bf109, only because it was the first key ever used for weapon fire. Maybe s or d are better suited because the distance to the modifier keys is shorter (the bf109 had 3 fire buttons on the stick, one for the guns on top of the engine, one for the cannon firing throught the propeller shaft and one for releasing external load, so I used e, E and ctrl-e). By the way, I chose m/M for Master arm on/off.
> > > 'Space' would be a good choice for a simple standard weapon trigger > > (every one try 'Space' first when trying to shoot in a new Sim, [...] > > True, but the majority of fgfs aircraft doesn't shoot. Wouldn't that > be a waste of that 'prominent' key? Although some sims use "e" for > "engines" or "s" for "starter"(?), which would make sense, too. And one > doesn't start engines *that* often. > > BTW: one can do a lot more with joysticks than only assign one binding > per button. There can be combinations with keyboard keys (Ctrl, Shift, Alt), > there can be bindings that switch the complete js to another operation > mode, etc. It would just be very hard to standardize that. > > m. > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
