Jump to content

Recommended Posts

Posted (edited)

There was a similar thread about this:

Deleting the Num5 binding from General - View Center didn't seem to work for me. However, binding something on the keyboard for UI Layer - recenter VR Headset fixed the issue for me.

Edited by Maverick806
  • Like 2

9800X3D, 64GB DDR5, RTX 3080

Valve Index, RS FSSB R3 Ultra, TM Viper TQS, TM TPR Pedals

Posted
28 minutes ago, Maverick806 said:

There was a similar thread about this:

Deleting the Num5 binding from General - View Center didn't seem to work for me. However, binding something on the keyboard for UI Layer - recenter VR Headset fixed the issue for me.

 

Thank you so much. Adding a keybind for the keyboard in UI layer - recenter VR Headset (I did RCTL +RSHFT + RALT + Scroll lock) fixed the issue for me too.

Removing the keyboard keybind for UI layer - recenter VR Headset causes the bug to reappear. As of patch 2.8.2.35632 Open Beta there must be a conflicting command not shown to the user for the UI layer - recenter VR Headset keyboard that takes over whenever the user leaves the command empty.

  • Like 1
Posted (edited)
20 hours ago, Flappie said:

Have you checked your aircraft bindings?

num5.png

Yes, I have. The [numpad 5] key is only bound as UFC 5, and has been unbound from any camera view keys. It has also been unbound from any relevant bindings under UI Layer and General tab.

 

15 hours ago, Flappie said:

Can you please check if the issue is also present when you're not using VR?

This issue is only present when using VR, and does not lead to any camera changes in 2D.

Interestingly, it recenters VR head position even when the controls menu is active (normally all inputs are captured when the control menu is active preventing transmission to in game).

 

Edit:

Additional info added to title post + workaround. It seems this is now triggered if "recenter VR" does NOT have any keyboard binding, in which case it defaults to [numpad 5]. This has been newly introduced with this hotfix.

 

Edited by Aarnoman
Edited for clarity
  • Like 2
  • Thanks 2
Posted


Duplicate bug report with temporary solution

- if a keyboard binding is created for UI Layer -> "recenter VR headset", it will no longer default to using [numpad 5].

Posted (edited)

Setting a keybind in the UI layer fixes the problem. Only a problem in VR this it seems like...So the fix is to keep a keybind in the recenter VR tab in the UI layer.🙂

@Flappie

Im only running the Steam version of DCS open beta latest and only playing in VR. no mods, only OpenXR and a reverb G2

Edited by Sjanten
  • Like 1
  • Thanks 1
Posted

@Flappie, can you confirm the bug (and the solution around it) is now tracked? The issue has arisen due to [numpad5] becoming the default VR recenter key if the "recenter VR headset" command under UI layer does not have any keybind assigned. This has been newly introduced in the recent OpenBeta.

Thanks, Yoyo

Posted
20 hours ago, Aarnoman said:

@Flappie, can you confirm the bug (and the solution around it) is now tracked? The issue has arisen due to [numpad5] becoming the default VR recenter key if the "recenter VR headset" command under UI layer does not have any keybind assigned. This has been newly introduced in the recent OpenBeta.

Thanks, Yoyo

Hi, I was about to get to it since this issue was occupying the thrid place of my long todo-list.

Since I'm not equipped with VR, I tried to reproduce this issue using my Track IR, to no avail. I've just reported the issue and I'll ask a fellow tester to help me on this one.

---

Posted

So it wasn't working as intended until the recent updates? In the rearm menu when I change my aircraft number to anything with a 5 my VR view gets reset, when typing 5 in the rearm menu should take priority and not recenter the view.

  • Like 2
Posted

I think the correct answer is: the game requires that something is mapped to "recenter VR headset" command. If the mapping is empty, it will revert to "Num5".

Want to free Numpad5 key for other functions? Map "recenter VR headset" to a different key combo. 

Hardware: VPForce Rhino, FSSB R3 Ultra, Virpil WarBRD, Hotas Warthog, Winwing F15EX, Slaw Rudder, GVL224 Trio Throttle, Thrustmaster MFDs, Saitek Trim wheel, Trackir 5, Quest Pro

Posted
7 minutes ago, some1 said:

I think the correct answer is: the game requires that something is mapped to "recenter VR headset" command. If the mapping is empty, it will revert to "Num5".

For the keyboard specifically? I've had the recenter command mapped to my HOTAS for about 3 years now, with Num5 doing nothing in VR for those 3 years until this recent update. 

  • Like 2
Posted

I could be that it now requires other keyboard key mapped. Haven't noticed any issues recently, but I've had it mapped to a different key combo for years. 

Hardware: VPForce Rhino, FSSB R3 Ultra, Virpil WarBRD, Hotas Warthog, Winwing F15EX, Slaw Rudder, GVL224 Trio Throttle, Thrustmaster MFDs, Saitek Trim wheel, Trackir 5, Quest Pro

Posted (edited)
On 1/27/2023 at 3:42 PM, Taz1004 said:

I did find a workaround however.  Go into UI Layer and assign keyboard strokes you don't use to "recenter VR Headset".  I assigned LCtrl+Num5.  Leaving it empty causes it to revert to Num5.

This is the solution to the problem - giving it a key like LCtrl+Num5 will release Num5 from the command to be used for any other functions. Thank you!

Edited by cpt_milkeye
Posted
On 2/7/2023 at 9:19 PM, BIGNEWY said:

Threads merged. 

This is working as intended, numpad 5 is hardcoded as the view reset in DCS

thank you

This is a very bizarre working as intended, as it only became an issue with this update. Please consider reverting to how it worked pre 2.8.2.35632, as it goes against all standards you have set for keybindings by specifically not having functions hardcoded.

  • Like 4
Posted
On 2/7/2023 at 5:19 AM, BIGNEWY said:

Threads merged. 

This is working as intended, numpad 5 is hardcoded as the view reset in DCS

thank you

Rather not have it hardcoded if possible. Hardcoding it makes it very unclear as to why it's happening.

You could make the default binding for view reset to be Numpad 5, but on the control bindings screen, like every other key.

  • Like 2
Posted

Might be worth creating some sort of note within the binding screen that there needs to be a keyboard key bound rather than just leaving that binding blank and having users experience what is from their point of view a bug.  Even if devs consider this correct behavior, from a user perspective it's poor design.

  • Like 2
Posted (edited)
On 2/13/2023 at 4:30 AM, cpt_milkeye said:

This is the solution to the problem - giving it a key like LCtrl+Num5 will release Num5 from the command to be used for any other functions. Thank you!

 

It is certainly a workable solution, but it totally conflicts with "Works as intended, num5 hardcoded to bla". Apparently it is NOT hardcoded. Getting fed up with reporting issues and just being dismissed. I'm glad there is a workaround. Especially in VR having a working numpad is essential.

Edited by MarcT-NL
  • Like 3
  • 1 month later...
Posted
2 hours ago, Vector1 said:

Can we get the hangar menu screen fixed to the right position, instead of having to press num5 every time I start sim up? Thanks

This is normal tha you have to center of the picture if You will see the main screen if you havent headset on your head when you click exe file. If you have it set up, it will center right away, if you have somewhere on the side, then no, you need to press the centering button. Set your joystick to center VR view.

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  5090 32Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

Posted
9 hours ago, Vector1 said:

Why in previous beta versions did not have this problem with hangar menu screen being low, didn't have to Centre it at all.

Were you using OpenXR before?

AMD 5800X3D · MSI 4080 · Asus ROG Strix B550 Gaming  · HP Reverb Pro · 1Tb M.2 NVMe, 32Gb Corsair Vengence 3600MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · VIRPIL T-50CM3 Base, Alpha Prime R. VIRPIL VPC Rotor TCS Base. JetSeat

  • 4 weeks later...
Posted (edited)
On 1/30/2023 at 4:06 AM, Maverick806 said:

There was a similar thread about this:

Deleting the Num5 binding from General - View Center didn't seem to work for me. However, binding something on the keyboard for UI Layer - recenter VR Headset fixed the issue for me.

 

I also have this problem since MT. It was _very_ frustrating until i found your answer.

 

This workaround fixed it for me, thank you so much. Getting my headset recentered every single time i tried to enter some numbers to waypoints in editor or ufc in the plane was infuriating to say the least 😄

Edited by Grodin

Fighting for peace is like screwing for virginity.

  • 8 months later...
Posted

Hi,

 

I'm not using VR mode, just mouse view and keyboard (and controller of course).

But since I've moved to latest version of DCS, I can't use numpad keys for pan camera on external views ...

RCTRL+RShift+ Numpas 2, 4, 6, 8 should pan the camera. It works fine INSIDE the cockpit, but not on external views.
I have tried some things but nothing works.

Any idea ?

 

Thanks

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...