Jump to content

Babbo

Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Babbo

  • Rank
    Newbie
  1. Right, if you mean Prop coarse/fine a bit, this is already mapped by default to F3/4 - and it works nicely. However, it appears that detent-functionality then is ignored.
  2. Thanks a lot for your update! ... and a question: condition levers now can be mapped to keys?
  3. ... anyway, I tried it. So we may discuss the following script - for me it's running fine: local CL_time CL_DRef = "LES/saab/CL/manip_common" create_command("FlyWithLua/LES/Saab/CL_increase", "Move condtion lever towards Max", "CL_time = os.clock() + .1\nset(CL_DRef, get(CL_DRef) + .01)\nset(CL_DRef, math.min(get(CL_DRef),1))", "if os.clock() > CL_time then\nset(CL_DRef, (get(CL_DRef) + (os.clock() - CL_time) * .05))\nend\nset(CL_DRef, math.min(get(CL_DRef),1))", "") create_command("FlyWithLua/LES/Saab/CL_decrease",
  4. Hello all! Please accept excuses for bumping a frequently stressed theme. I've searched up and down the net, but was not able to find an answer to the following question: how to map a keyboard key to jointly move both condition levers? (I.e. not a quadrant, not a joystick, not the mouse - just the keyboard, precisely, two keys for both directions.) Thanks a lot for any input!
  5. Thank you, I would never have had that idea. - Is there a way to disengage this licensing window (since it isn't needed)?
  6. Firstly, have my greatest thanks for your gift, but secondly, I can't license your product: correct entries (email and pwd) always fail! Could you please offer some help?
×
×
  • Create New...