Remove NUM5 as recenter view

I have just added a numberpad to a bracket on my left arm rest to use whilst flying in the rift. I have all those keys at my fingertips. However I want to assign options in the UI layer like having number 4 as right mouse button or assign a zoom key etc. Anyway round the fact that you can presently only assign joystick buttons ?

It appears DCS doesn't allow assigning the VR or mouse functions to keyboard characters. My workaround is using an ancient Belkin Nostromo N52 keypad on my left like you are attempting. I have programmed keys for VR functions, mouse functions, general functions (i.e. quit, pause, active pause, frame rate display, control input indicator and cockpit camera position). I setup a N52 profile that maps the keys to DirectInputs (DI's), which the DCS recognizes as joystick buttons and will accept for the VR and mouse commands. I doubled the numbers of commands on the keypad from 24 to 48 by using one of the joystick buttons on the stick as a modifier.

I am happy with the way it works.

Up.

Come on ED, respond to this, we need NUM5 for the Hornet more then ever now....

Up.

 

Come on ED, respond to this, we need NUM5 for the Hornet more then ever now....

This has been an option long before the hornet released. Go to the UI settings for VR in the controllers section, and reassign the KP5 to what ever you want it to be. For example I reassign mine to Warthog Paddle + CMS Z.

This has been an option long before the hornet released. Go to the UI settings for VR in the controllers section, and reassign the KP5 to what ever you want it to be. For example I reassign mine to Warthog Paddle + CMS Z.

I know very well that I can assign it to anything we want, but this does not unmap the num5. I need to unmap num5 from recenter view to use it for the UFC numbers, but it is not possible even if removed from the controls setup it still re-centers the screen. It was already discussed in the thread.

I know very well that I can assign it to anything we want, but this does not unmap the num5. I need to unmap num5 from recenter view to use it for the UFC numbers, but it is not possible even if removed from the controls setup it still re-centers the screen. It was already discussed in the thread.

I works just fine here and as has been said, it is implemented for a long time now. I use Num5 for my UFCs all the time in VR without it re-centering my view.

If it does not work the error is on your end.

Strange has been corrected long ago and wasnt doing it any longer. Using Oculus now so cant test but it was corrected 100% sure.

Strange has been corrected long ago and wasnt doing it any longer. Using Oculus now so cant test but it was corrected 100% sure.

I also use oculus, and num5 re-centers the screen even tho it is not mapped in the UI cintrols. Checked also in the default.lua in config/input/keyboard folder and there is nothing for re-center view line. I don't think this was ever corrected.

Both open beta and "stable"

I know very well that I can assign it to anything we want, but this does not unmap the num5. I need to unmap num5 from recenter view to use it for the UFC numbers, but it is not possible even if removed from the controls setup it still re-centers the screen. It was already discussed in the thread.

Well that's funny because I have un-mapped the NUM5 from the controls and mapped to something else as mentioned. I also use the keypad for UFC, and fly with a VR headset. I have had this configuration for nearly a year now. When I press the NUM5 my view doesn't recenter, my UFC 5 presses both in BETA and STABLE. Maybe a reinstall is in order.

Well that's funny because I have un-mapped the NUM5 from the controls and mapped to something else as mentioned. I also use the keypad for UFC, and fly with a VR headset. I have had this configuration for nearly a year now. When I press the NUM5 my view doesn't recenter, my UFC 5 presses both in BETA and STABLE. Maybe a reinstall is in order.

This is weird, my open beta is relatively fresh installation, since 2.5 release. Will give it a few more shots, map/unmap to see if it can make any difference.

This is weird, my open beta is relatively fresh installation, since 2.5 release. Will give it a few more shots, map/unmap to see if it can make any difference.

I would start with your saved games folder, that is where the keybind stuff is, not the game installation folder.

I would start with your saved games folder, that is where the keybind stuff is, not the game installation folder.

Yes, thanks. I will test today to wipe out some stuff from there and see what happens. Should be something on my side if it works for you.

Using numpad for UFC in A10C and FA18. Also for input in Viggen and Mirage, no longer centering the view in VR.

Yes! Worked for me after mapping something else for re-center. It is fixed. Thanks :)

Sent from my Redmi 4 using Tapatalk

only took 2 years to figure it out... :megalol: j/k

only took 2 years to figure it out... :megalol: j/k

Sent from my Redmi 4 using Tapatalk

Solved....

Old thread, but i still found it searching for  solution to this issue. There seems to be a lot of "it doesn't work for me" and "well you are wrong because it does work for me" type comments on here so I thought I would add a definitive answer now I seem to have fixed it. 

Basically Num 5 defaults to VR Centre View even if Num 5 is bound to something else. BUT, if you bind another key to VR Centre View and not leave it blank then Num 5 is ok for other things. 

Hope this helps someone.

Just in case you got here as I did after all these years.

Rebind "recenter VR view" into something else!!!

It seems DCS use default hardcoded bind in case of lack of binding for specific command.

Shish. 

And here I was in 2023. 

Same. 

I'd have a lot less to be annoyed about if they'd just documented it somewhere that users will see.  I spent a couple of hours of my time trying to chase down a non-existent binding, thinking I'd made a mistake.

I guess we should add a counter for wasted life hours xD
Just to give some ED developers a number for considerations about design decision consequences.
In example of how many hours of frustration they caused.

Would be nice that you can edit the keybinding in each module. Two or three updates ago, start to interferes (for example) with the Num Pad in the Apache.