On Thursday 04 January 2007 05:31, Hal V. Engel wrote: > > > The first issue is how the boost control is set up. I notice that in > > > the P51, Corsair and the Beaufighter that these are setup differently > > > but not much differently. Just enough that it looks like anything I > > > setup in my joystick configuration will be correct for only one > > > aircraft. This is what nasal control wrappers solve, when aircraft modellers and joystick config writers remember to use them... The default function works in most cases, and for aircraft with unusual requirements can be overridden with a custom function of the same name. For example, the Lightning provides its own controls.applyBrakes() and controls.flapsDown() functions amongst others.
> > There is also some difference in Boost handling. Some Aircraft switch > > the blower by hand, so the switch works like on/off. Other engines (like > > the two staged supercharged merlin) switch the gears automatic and the > > "user" button just disables this Automatism. > > These are key bindings which are easy to unify. I see a problem with > > nasal scrips... There should probably be a nasal wrapper for boost control too - even if the default was only suitable for one aircraft, it would at least provide a unifying function name for JS config purposes. > The joystick config for this look like this: > <button n="8"> <snip huge button definition> > </button> Oh, and the nasal wrappers are so much compact than that sort of XML config :-) > > > But the > > > rockets use a custom nasal script: <snipped lots about the Beaufighter and A-10 weapons> I believe that Alexis is working on revising the A-10 weapons systems, but there are already weapons selection and triggering functions in controls.nas. I think aircraft modellers should wherever at all feasible stick to the existing function names for controls functions that are likely to be bound to JS buttons. That way, this whole discussion is pretty much completely solved. > > I believe (haven'tried for a while) you can also add nasal scripts in > > your Joystick config. The Beaufighter needed Nasal to display the > > remaining rockets on the rails. You can add nasal scripts to joystick configs if necessary, the Saitek Cyborg-Gold-3d-USB.xml is an example of what's possible (including modifier keys with JS buttons) > > As stated above key bindings are easy to adapt, but the nasal scripts > > names vary with every aircraft and function triggered. > > The first I can think of, is to attach listeners to generic properties > > which can be triggered by key/joystick bindings. The listener then calls > > the nasal script. > > But is this an acceptable solution? As far as I can see, it's not necessary if we have sufficient "standard" functions in controls.nas for overriding. If a nasal wrapper for a function exists, joystick configs should use it rather than messing about with properties which may be used in all sorts of different ways by aircraft modellers. This is one of Melchior's pet topics and he knows a lot more about it than me - I'm sure he'll have something to say when he shows up again. Cheers, AJ ------------------------------------------------------------------------- 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-users mailing list Flightgear-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-users
