![]() ![]() It also depends on what type of aircraft you want to fly since some aircraft should use a yoke rather than a stick (most GA aircraft and Airliners). Joystick recommendation? It depends on a number of factors. Philosopher Posts: 1593 Joined: Sun 7:29 pm Oh, and agree on what is speedbrake and what is spoiler. I wish we could come to an agreement on a standard way to do things, but my only idea is to have a toggle(Control) and step(Control) for every control to provide flexibility and overload those per-aircraft. my real opinion is that the controls.*() wrappers should be overwritten for special uses, but I end up reaching around those wrappers and using setprops/getprops and manually coding support for different aircraft. I also give the user my own sense about what things are spoilers and what are speedbrakes (tip appendages like on the A-10 and things that dump lift are spoilers, everything else is a speedbrake, especially if pointing down). And I did the f16, harrier, helis, and V-22, but it really takes a while to fill in information for all the aircraft (I think I have >90% of the 2.6 release, and I haven't gotten a chance to update to 2.10 ). I do all of those things every day! One big problem though: I only got through the 'B' section of the launcher. (I'll also check that I've got the prop/mixture/throttle adjustments available as button bindings) Is there are a particular reason for not using the repeatable flag, or is it purely for people who have mode-switches and might have another (non-repeatable) function assigned to the button? On a different note, I'm interested to see what bindings people are using on joysticks, to check that the set of button bindings that are supported in the configuration dialog are sufficient.Īt present the dialog supports trim settings, but sets the button to be repeatable. IMO anyone who knows enough to write Nasal joystick bindings will have enough knowledge to edit the joystick XML files directly and use the Nasal Console. The joystick configuration dialog is really targeted at new users who don't have any XML or Nasal experience. Partly this was due to time constraints, but it was also because I didn't think there was a use-case for it. Adding the ability to write Nasal for a given button was something I considered, but didn't implement.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |