Jump to content
Sign in to follow this  
Hans_Petter

Keyboard commands

Recommended Posts

My father's PC got a copy of FU3 some time ago. A few days ago he even got the refined mesh with Jon's flattened airports. However, he never got my rudder pedals so I/he will have to fly the planes without pedals. I checked/ticked auto-coordination to make them turn on the ground by means of a joystick. Well, they mostly don't. You may laugh now but where are the keyboard commands for turning / rudder? It's been so long since I tried to fly without pedals that I've forgotten.Hans Petter

Share this post


Link to post
Share on other sites

Hello Hans,This is straight from my Flt3 install cd:Joystick/Keyboard Command Binding SystemIn the following section, a "joykey" refers to a joystick button or keyboard key. The following section also refers to the command console. The console is invoked from fly mode by hitting the ":" key.You can change the mapping of joystick buttons or keyboard keys from their defaults by creating a file named joykeys.cfg in your flight directory. That file contains lines with one of these formats: bind joykey to function, pass default data to function bind joykey to function, pass specified data to function off remove all bindings to this joykey console bind joykey to console command stringThe best way to find out the syntax for joykey_codes, as well as the list of available functions, is with the dump_hotkeys console command described below.There is a brief description of the joykey code syntax at the end of this document.Examples: joy_1 left_brake_on when joystick button 1 is pressed, turn on the left brake joy_1_up left_brake_off when joystick button 1 is released, turn off the left brake alt_x off disable alt-x (program exit) shift_alt_f do_the_hokey_pokey 10 invoke the do_the_hokey_pokey routine with data value 10 ctrl_u console wakeup the dog pass the string "wakeup the dog" to the consoleDynamic Joykey Function MappingYou can change a single binding on the fly with the console "bind" command. The bindcommand is followed by a string with the same format as lines in joykeys.cfg.Example: bind joy_1_down toggle_landing_gear this would bind your joystick button 1 to toggling the landing gear.NOTE: bindings added with the "bind" command are not recorded and go away when you exit this program.Getting a List of Existing Joykey BindingsYou can get a list of all the existing joykey bindings written to a file with the console command dump_hotkeys .Making Joybuttons RepeatJoybuttons can made be to repeatedly invoke their bound function as long as a joybutton is held down by adding the _rep modifier to the end of the joykey code name. This is good for things like trim or prop pitch which have a large number of increments.You can set the overall global repeat rate with the config variable joykey_repeat_interval, which is repeat time in seconds. Default value is 0.1.You can set the overall global delay before repeating begins with the config variable joykey_repeat_delay, which is also in seconds. Default value is 0.25.The repeat rate for individual buttons may be scaled by adding _XX after _rep, where XX is between "1" (fastest repeat) and "15" (slowest repeat). "10" is the default repeat rate. For example, with the default values, you could make joybuttons repeat with an interval of of .001 seconds to .15 seconds.Joykey Code String PartsLook at the default joykey bindings section below for good examples of Joykey codes.Prefixes:joy_ joystick buttonkey_ keyboard key (optional)Modifiers:altshift NOTE: shift_f is not the same as F, shift_; is not the same as :ctrlkp numeric keypad key (IE kp_5 instead of regular 5)Suffixes:_down do the key or button press (optional)_up do the key or button release_rep_XX make the command repeat at rate XX, XX="1" is fastest, XX="10" is default rate, and XX="15" is slowest. This is only for joybutton presses. The _rep_XX must be the last token in the keycode string (after _down/_up).special key names: ins del home end pageup pagedown up down left right print pause bs esc tab enter space f1 through f12Default Joykey Bindingsx_up Zoom_Out_Donez_up Zoom_In_Donebs Toggle_Auto_Trimtab Activate_Radioenter Repeat_Messageesc Exit_Screenspace Communicate" Toggle_Navigation_Lights' Toggle_Beacon, Left_Rudder. Right_Rudder/ Center_Rudder; Toggle_Anti_Collision_Lights< Rudder_Trim_Left> Rudder_Trim_Right? Rudder_Trim_CenterB Prop_BrakeC Source_Next_CommE Select_EngineF Flaps_UpI Source_SelfL Toggle_Pulse_LightsO Source_Next_Ground_ObjectP Source_Next_PlaneX Increase_Field_Of_ViewZ Decrease_Field_Of_View[ Elevator_Trim_Up Elevator_Trim_Center] Elevator_Trim` Toggle_AntiIcea Autopilot_OnOffb Toggle_Parking_Brakesc Target_Next_Commd Increment_Time_Of_Daye Start_Enginef Flapsg Toggle_Landing_Gearh Toggle_Carb_Heati Target_Selfj Panel_Main_Backlightingk Toggle_Taxi_Lightsl Toggle_Landing_Lightsm Inflight_Mapo Target_Next_Ground_Objectp Target_Next_Planeq PCLr Toggle_Comm_Radios Increment_Time_Of_Yearu Toggle_Right_Landing_Lightw Wax_Moonx Zoom_Outy Toggle_Left_Landing_Lightctrl_D Dump_Crashboxctrl_M Toggle_Modelsctrl_R Toggle_Blackbox_Recordctrl_d Decrement_Time_Of_Dayctrl_e Shutdown_Enginectrl_f Toggle_Frame_Ratectrl_l Toggle_Labelsctrl_p Toggle_Blackbox_Pausectrl_p Pausectrl_s Blackbox_Save_Editctrl_s Decrement_Time_Of_Yearctrl_v Debug_Voice_Logctrl_w Wane_Moonctrl_z Toggle_Zoar_Modealt_enter Full_Screenalt_M Add_Auto_Markeralt_a Autopilot_HoldAltitudealt_d Toggle_PropDomealt_f Auto_Tune_Radioalt_g Maydayalt_h Autopilot_HoldHeadingalt_m Autopilot_ToggleApralt_n Autopilot_ToggleNavalt_o Optionsalt_r Change_Resolutionalt_s Autopilot_HoldAirspeedalt_t Reload_Voice_Timingsalt_v Autopilot_HoldVerticalSpeedalt_w Autopilot_LevelWingsalt_x Quit_Gamealt_y Toggle_YawDamperctrl_alt_A Add_Hoopctrl_alt_G Toggle_Grid_Texturesctrl_alt_H Toggle_Hoop_Statsctrl_alt_T Cycle_Forced_Grid_Texturesctrl_alt_g Start_Grid_Testctrl_alt_p Print_Screenctrl_alt_q QA_Print_Screenkp_8_up Look_Up_Donekp_4_up Look_Left_Donekp_6_up Look_Right_Donekp_2_up Look_Donekp_0_up Left_Brake_Offkp_del_up Right_Brake_Offf1 Camera_Forwardf2 Camera_VFR_Cockpitf3 Camera_IFR_Cockpitf4 Camera_Virtual_Cockpitf5 Camera_Externalf6 Camera_Chasef7 Camera_Spinningf8 Camera_Taxif9 Camera_MTVf10 Camera_RCkp_7 Look_Left_45kp_8 Look_Upkp_9 Look_Right_45kp_4 Look_Leftkp_5 Look_Aheadkp_6 Look_Rightkp_1 Look_Left_135kp_2 Look_Downkp_3 Look_Right_135kp_0 Blackbox_Toggle_User_Controls_Camerakp_0 Left_Brake_Onkp_del Right_Brake_Onf11 Camera_Stillf12 Toggle_Tape_Stripctrl_kp_5 Center_Controlsctrl_f12 Cycle_Active_Tapestripalt_f5 Camera_Inverse_Externalalt_f7 Camera_Abovealt_f12 Show_Taxi_Pathkp_enter Target_Next_Internalkp_* Reverse_Thrustkp_+ Throttle_Increasekp_- Throttle_Decreasekp_/ SpeedBrakesctrl_kp_+ Mixture_Increasectrl_kp_- Mixture_Decreasealt_kp_+ Prop_Deployalt_kp_- Prop_Retractup_up Pitch_Offleft_up Left_Roll_Offright_up Right_Roll_Offdown_up Pitch_Up_Offhome Target_Next_Internal2up Blackbox_Play_Forwardup Pitch_Onpageup Miracle_Upleft Blackbox_Frame_Backwardleft Left_Roll_Onright Blackbox_Frame_Forwardright Right_Roll_Ondown Blackbox_Play_Backwarddown Pitch_Up_Onpagedown Miracleshift_kp_+ Prop_Increaseshift_kp_- Prop_Decreaseshift_up Blackbox_Play_Fastershift_down Blackbox_Play_Slower


dual boot: win8.1pro64bit (primary) | win10pro64bit  | mobo: MSI Prestige x570 Creation | cpu and cooler:  AMD 5950X; Noctua NH-U12A | ram: 4each 8gb sticks of ddr4-3200 CORSAIR Vengeance LPX CMK16GX4M2Z3200C16 | gpu:  nvidia RTX2070Super Founders Edition| lcd: LG 24" 4k, LG 24UD58-B

Share this post


Link to post
Share on other sites

Thanks to you both :-)So, the standard keyboard set-up and the possible joykeys commands are available from my installation CDs.There's a complicating issue for us "foreigners" with "regionalized" keyboards -- FU3 keys refer to the placement of keys on a standard US keyboard rather than to the key command. Thus, the key for ":" gives no meaning unless you know where the US keyboard has placed the ":". Conversely, Jon's image will give the correct keys for rudder, no matter which characters your particular keyboard has placed on those particular keys. When in doubt, the layout for various keyboards can be found at Wikipedia.I'm thinking, wouldn't it be better to define the important key commands to parts of the keyboard that are common to all of us? The arrow keys are the same and so is the numpad section. I think I'll use the arrow keys for rudder. "F" for flaps and "G" for gear are fine since these are out of the "regionalized" area too. The area that varies is the one to the right of the main letter section. Norwegian and Danish have the characters

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...