#Bindings

80 messages · Page 1 of 1 (latest)

short cosmos
#

There's no way to pin a note in here, is there?

#

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

short cosmos
#

@narrow slate FYI

short cosmos
wild torrent
wild torrent
#

and you need to open the "full" view to see pins

short cosmos
#

Ah, I see

wild torrent
#

I also edited my initial reply to be more clear

short cosmos
#

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) 
short cosmos
#

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

flat silo
#

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')}},
short cosmos
flat silo
#

awesome. The same exact format will work for the \joystick\defaults.lua file too

flat silo
#

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
short cosmos
flat silo
#

awesome. ty

short cosmos
#

No, no. Thank you

#

You've made Gamera happy

flat silo
#

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.

short cosmos
#

Is this for thrustmaster warthog flap control so you can have three position match up/half/full ?

flat silo
#

yes

short cosmos
#

I've just been using it as a up/down control but that's cool

flat silo
#

I use VA and SD. Saw the request on the forums, so I found a temp solution.

slender hedge
#

Does anyone have a Warthog hotas profile for mirage F1

short cosmos
#

But I haven't done any attack work yet, just figuring out how to fly and do basic air to air

slender hedge
#

Yeah I followed that for the most part

short cosmos
#

But then, what I think makes sense for me might not make sense for you

slender hedge
#

I just want to have it binded lol

short cosmos
#

I'm not even sure I'm happy with my current version yet anyway

slender hedge
#

What did you do for axis curvature and deadzones ?

short cosmos
#

I normally don't see a need for any curves or deadzones on my thrustmaster stick

short cosmos
#

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

slender hedge
#

Only reason I need curves is my hotas will pull back farther than the ingame stick

short cosmos
slender hedge
#

Dont know what you mean by that

short cosmos
slender hedge
#

Dead zoner

#

zone*

#

and curvature

short cosmos
#

Why curvature instead of saturation?

flat silo
flat silo
#

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)

heavy rock
#

Is there any documentation i can find that can provide me with some pointers for what i need bound?

short cosmos
#

Yes, Chucks' guide, is the easy and short answer

heavy rock
#

There is no chucks guide for the F1 yet homie

short cosmos
#

Ah, yes. Sorry, didn't know we were on f1 specific.

#

I'm still waiting for Chuck to do his Apache guide too.

short cosmos
#

Did you ask in #questions ?

heavy rock
#

No in here, where it should be?

short cosmos
#

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

short cosmos
heavy rock
#

"RTFM" lmao ill, take a look

short cosmos
#

[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

flat silo
#

trim.
flaps.
dogfight switch and its off (something like C+S/M switch)
Radar Marker Move binds
Nose wheel Gain
Radar lock and unlock
Chute
Airbrakes
Gun fire
Bomb Drop

#

Thats the minimum imo

lime bloom
#

Bomb Drop/Missile Fire is the Bombs, Rockets, Missile, and Sight Recorder button

#

also the axis for the radar thing is Radar Control Stick Bearing (L/R) and Range/Velocity(Up/Down)