#Bindings
80 messages · Page 1 of 1 (latest)
Here's what I've bound so far (removed axis, I don't have Nitro to have a long message)
//Control Stick
-Autopilot disengage trigger- HOLD and hit PA on left of dash (green is good)
-Autopilot disengage lever - to disengage AP [I'm setting to NWS for now]
-Bombs, rockets, missiles and sight recorder button [this is wep release]
-Gun button (see cover) [I haven't had to flip a cover, just master arm]
-(C + M or SW) R deselection switch [CMS depress to simulate return to search]
//Throttle
-Cannon 300-600m and missile lock/unlock button [needed?? see Radar Stick separate "Lock-On" for BVR use -- what is this for? I haven't seemed to need it]
//High-lift devices
-Slat/Flap lever - DOWN/UP (see combat flap, device selector)
//Undercarriage (gear)
-U/C control lever - Extend/Retract (see U/C safety lever)
//Engine/Fuel controls
-Start button (see cover - CLOSE/OPEN)
-Throttle cut/idle switch
//On keyboard (these aren't literal from controls menu yet)
-Master arm cover and master arm On/Off
-"Master failure warning light"
-Emerg jettison
-Ldg/taxi light/off
//Front structure, Chaff and Flares
-"Chaff/flares selector switch -BOTH" and "Chaff/flares selectro switch - CHAFF" and "- FLARE", I set this on my throttle
-"Chaff/flares release button" - [I used aft on the warthog throttle brake and fwd to set to "BOTH"]
//Other bindings - I still need to note what it's called in controls
-"Airbrake" [I need to find a new spot for this or other throttle bindings I have now]
-BZ and TL close combat air modes ("Telemeter/zone scanning switch - BPZ" and "- TEL" and "- CENTER" in controls) for radar close combat modes, I haven't figured out BZ "sector" search lcoks
-"Radar control stick APS/APC lever - Lock-On" (for BVR locks, separate from the other lock, hold until acquired]
-Form and nav lights (where's beacon/anti-collision I think is "formation")
-Wheel Brake On [I changed from default to match my own standard]
//still need to bind:
-Chute
I bound trim and possibly some other obvious things that I didn't include in my notes because... I always bind trim and it's obvious
@narrow slate FYI
Updated. The radar lock on for "BVR" is "Radar control stick APS/APC lever - Lock-On}
There is, but you need a moderator to do it
and you need to open the "full" view to see pins
Thanks. I was trying to figure out how to pin earlier and failed
Ah, I see
I also edited my initial reply to be more clear
New message for axes (I don't have Nitro and hit the character max):
-Thrust - Set to Slider, using curvature -10 - this allows me to hit AB physical detent on my Warthog throttle
-"Radar control stick bearing control" && "Radar control stick range/velocity control" [inverted] - this is for "TDC slew" see "Alidade (strobe" in documentation)
Updated AP buttons in notes on control stick
For binding radar controls, just use mouse for now:
Awacs? I'm trying to get there Bailey
Get where? ah, on different channel
in other news, I have a solution for the radar stick. not the best, but its something:
{down = devCmds.Cmd101, cockpit_device_id = devices.MAIN, value_down = 0.33, name = _('Radar control stick scale selection - 15'), category = {_('Left console'), _('Radar control stick')}},
``` Goes in `C:\...\DCS World\Mods\aircraft\Mirage-F1\Input\Common\keyboar\defaults.lua` around line 243. I may maek a formal writeup later. Don't be afraid to take it into your own hands. The other value_downs will be 0.0, 0.67, and 1.0 for the other ranges.
This should works. I dont have the time to restart dcs to check
{down = devCmds.Cmd101, cockpit_device_id = devices.MAIN, value_down = 0.00, name = _('Radar control stick scale selection - 7'), category = {_('Left console'), _('Radar control stick')}},
{down = devCmds.Cmd101, cockpit_device_id = devices.MAIN, value_down = 0.33, name = _('Radar control stick scale selection - 15'), category = {_('Left console'), _('Radar control stick')}},
{down = devCmds.Cmd101, cockpit_device_id = devices.MAIN, value_down = 0.67, name = _('Radar control stick scale selection - 35'), category = {_('Left console'), _('Radar control stick')}},
{down = devCmds.Cmd101, cockpit_device_id = devices.MAIN, value_down = 1.0, name = _('Radar control stick scale selection - 60'), category = {_('Left console'), _('Radar control stick')}},
Scan Selection: working
{down = devCmds.Cmd102, cockpit_device_id = devices.MAIN, value_down = 0.5, name = _('Radar control stick scan selection - 30'), category = {_('Left console'), _('Radar control stick')}},
{down = devCmds.Cmd102, cockpit_device_id = devices.MAIN, value_down = 1.0, name = _('Radar control stick scan selection - 60'), category = {_('Left console'), _('Radar control stick')}},
Worked like a charm. To test, I just used keys 1 through 4 on the keyboard:
awesome. The same exact format will work for the \joystick\defaults.lua file too
HSI Modes, works
{down = devCmds.Cmd555, cockpit_device_id = devices.MAIN, value_down = 0.00, name = _('Mode selector switch - TT'), category = {_('Central front panel'), _('Navigation indicator')}},
{down = devCmds.Cmd555, cockpit_device_id = devices.MAIN, value_down = 0.33, name = _('Mode selector switch - TE'), category = {_('Central front panel'), _('Navigation indicator')}},
{down = devCmds.Cmd555, cockpit_device_id = devices.MAIN, value_down = 0.67, name = _('Mode selector switch - VT'), category = {_('Central front panel'), _('Navigation indicator')}},
{down = devCmds.Cmd555, cockpit_device_id = devices.MAIN, value_down = 1.00, name = _('Mode selector switch - AR'), category = {_('Central front panel'), _('Navigation indicator')}}, -- use Mode selector switch - RIGHT
This works perfectly too. Took me longer to test because I forgot to check for a pre-existing default bind which was conflicting.
awesome. ty
works
TMWH or Virpil CM3 Flap Controls
Put the following in C:\...\DCS World\Mods\aircraft\Mirage-F1\Input\Common\joystick\default.lua, around line 43, just below the other flap binds:
{down = iCommandPlaneFlapsOff, up = iCommandPlaneFlaps, name = _('Flaps Up/Down Special'), category = _('Systems')},
{down = iCommandPlaneFlapsOn, up = iCommandPlaneFlapsOff, name = _('Flaps Landing Position Special'), category = _('Systems')},
For the TMWH, bind the flaps up to Flaps Up/Down Special and your flaps down to Flaps Landing Position Special. Due to the animation speed, the controls can possibly get out of sync. If that happens, slowly (at a rate of once per second) select flaps up on the TMWH, then middle, then up. They should now be in sync. If not, I have not discovered your case. You will likely be able to resync by pressing the ingame flaps once or twice. Enjoy.
Is this for thrustmaster warthog flap control so you can have three position match up/half/full ?
yes
I've just been using it as a up/down control but that's cool
I use VA and SD. Saw the request on the forums, so I found a temp solution.
Does anyone have a Warthog hotas profile for mirage F1
As usual, I recommend binding it oneself, but I suppose I could try to export mine. Mine is a "work in progress" as I discover what I need. I've posted the text version of what I've considered important to bind so far
But I haven't done any attack work yet, just figuring out how to fly and do basic air to air
Yeah I followed that for the most part
But then, what I think makes sense for me might not make sense for you
I just want to have it binded lol
I'm not even sure I'm happy with my current version yet anyway
What did you do for axis curvature and deadzones ?
Only what I posted for the throttle to use the physical detent for afterburner
I normally don't see a need for any curves or deadzones on my thrustmaster stick
I'm happy to share my work in progress bindings, I just don't know how to do that in dcs. I'm also bound on the TM virtual device as I use target (rotate the stick about 15 degrees for ergonomics)
My throttle currently
I think
I'm assuming guid on the virtual target device would just need to be changed but I've never swapped profiles with people before or used others
Only reason I need curves is my hotas will pull back farther than the ingame stick
so you use saturation to adjust for full travel?
Dont know what you mean by that
what do you adjust on other aircraft so that your real world pull back matches the stick in the game?
Why curvature instead of saturation?
Great for the Virpil CM3 5way Knob
Add this to the end of C:\...\DCS World\Mods\aircraft\Mirage-F1\Comm\comm.lua to enable JTAC. IC safe:
utils.verifyChunk(utils.loadfileIn('Scripts/UI/RadioCommandDialogPanel/Config/Common/JTAC.lua', getfenv()))(9)
Is there any documentation i can find that can provide me with some pointers for what i need bound?
Yes, Chucks' guide, is the easy and short answer
There is no chucks guide for the F1 yet homie
Ah, yes. Sorry, didn't know we were on f1 specific.
I'm still waiting for Chuck to do his Apache guide too.
(I came to whatever this Discord feature is trying to find F1 hype/opinions/discussion/hate but found people only discussing the weird Discord feature)
Did you ask in #questions ?
No in here, where it should be?
I don't know. Again, I was hoping to find F1 discussion but only found Discord feature discussion so far
I know people are discussing F1 stuff in questions though
possible to rename this to "F1 bindings?" I don' tknow
Did you look in the manual? I haven't bought it yet, probably will today
"RTFM" lmao ill, take a look
[shrug] sorry, it's all I got. Other than the standard bindings for any module
And no one else is responding here...
Have you looked at the RedKite videos?
I know that's not documentation... but if you don't like "manual" as the answer to the "where's the documentation" question
My guess is the radar and a/a weapons bindings are first to look at