2.9 - Object Camera with Position Inheritance [RSHFT+RCTRL+F2]

[Mistermann]

Not sure where to post this.  Mods, please move accordingly.

The update to 2.9 introduced 2 new "go pro" cameras called

Object Local Camera [RCTRL+F2] and Object Camera with Position Inheritance [RSHFT+RCTRL+F2]

How do I bind these cameras to my HOTAS?  I fly in VR and don't use the keyboard at all.  When I try and use the controller setup, the system doesn't allow me to bind anything but the keyboard to these cameras.

Can someone please point me to the proper way (lua files?) to enable binding of these cameras to something other than the keyboard.

Thanks!

Edited October 26, 2023 by Mistermann
Added image

[Mistermann]

@Flappie and/or @BIGNEWY, I suspect I posted this in a bad place.  Maybe it gets more traction in the videos and screenshots sub forum?  I don't want to cross post.  Can you move or recommend a better home for this topic?

[Revs]

I have not used it in a while but I was able to use key combinations using Voice Attack

[davewhite]

A bit off from Mistermann original question, but did anyone else notice that these camera options are not available for the Mig-21?

[Mistermann]

7 hours ago, Revs said:

I have not used it in a while but I was able to use key combinations using Voice Attack

Thanks.  I haven't used VA in quite some time, but I suspect you bound the keyboard combinations to your VA command. 

I am asking how I can assign new HOTAS bindings to this command.  For some reason the DCS configuration isn't allowing that.  Its difficult to see in the image I posted above, but the cells underneath my HOTAS peripheral devices is a different color indicating those cells are locked from being edited.

Taking a shot in the dark here - hey, @Rudel_chw, any ideas?  

[Rudel_chw]

1 hour ago, Mistermann said:

I am asking how I can assign new HOTAS bindings to this command.  For some reason the DCS configuration isn't allowing that.  Its difficult to see in the image I posted above, but the cells underneath my HOTAS peripheral devices is a different color indicating those cells are locked from being edited.

Taking a shot in the dark here - hey, @Rudel_chw, any ideas?  

 

Hi,

I'm not really versed on this, but look at this folder:

C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Config\Input\Aircrafts

(it may be different if you have a custom DCS install path)

 

There is a common_keyboard_binding.lua file, which contains the sentence that defines the binding for the keyboard, for example:

{combos = {{key = 'F2', reformers = {'RCtrl', 'RShift'}}}, down = iCommandViewObjectWithPosition, name = _('Object camera with position inheritance'), category = _('View')},

 

Now, if you check the file used by the Hotas, common_joystick_binding.lua, you will see that it does not have a definition for this iCommandViewObjectWithPosition function, but you can add it like this:

{combos = {down = iCommandViewObjectWithPosition, name = _('Object camera with position inheritance'), category = _('View')},

 

Of course, before editing make backups of the affected files, just in case.

 

Editing files within the DCS program folder may break the IC multiplayer integrity, so you probably would like to use the Quaggles utility:

 

 

[Mistermann]

Thanks @Rudel_chw, I'll give it a shot when I'm back at the DCS computer.  

EDIT:  Worked exactly like you predicted.  I can now bind that command to a HOTAS.  You, sir, are awesome!  Thanks for helping out a fellow DCS fanatic.  

Edited October 31, 2023 by Mistermann
Rudel's suggestion worked