Rotating knobs with VR Controllers produces large jumps in values: unable to dial heading etc

,

Are you on Steam or Microsoft Store version?

Steam

Are you using Developer Mode or made changes in it?

No

Brief description of the issue:

Rotating knobs with VR controller is too rough: no matter how slowly you try to turn your controller, heading (for example) jumps by 20-30 degrees at a time, and all rotational controls jump by a huge margins. It’s impossible to tune anything to any degree of accuracy at all.

Provide Screenshot(s)/video(s) of the issue encountered:

Easy to reproduce, no need for video.

Detail steps to reproduce the issue encountered:

  1. Grab any rotating knob with a VR controller. Heading bug is a good example.
  2. Try adjusting headin 1 degree or even 5 degrees left or right from current by rotating the controller. The dial jumps by large numbers. Same happend with VS, altiture and any knob or encoder that can be rotated.

PC specs and/or peripheral set up of relevant:

Reverb G2, WMR, Ryzen 5900X, RTX 3080, 64Gb RAM, 2Tb SSD.

Build Version # when you first started experiencing this issue:

Sum Update 7

Same issue also for me. Please fix this.

1 Like

Apparently it’s even worse with trim wheel - try to adjust it and it jumps so much you’re likely going to crash. VR controllers as they are implemented now are absolutely useless for any fine adjustment: trim wheel, heading, course, radio frequency etc. Simply unusable, period.

ALT setting goes ‘2400’ → ‘3900’ → etc…toggle switches can be flipped up OK-ish but it’s extremely hard to flip them back down again but I’m sure they know all these things. I guess they just didn’t have the time to bring it to some basic level of usefulness before the deadline came and so they pushed it out because saying “sorry guys, maybe next SU” would’ve made no difference in the level of uproar in the community. So what we have is an early preview into planned functionality, not the actual controller support.

Except we were told that VR controller support is coming, not as a preview. We were told DX12 will come as a previoew and not to expect performance gains. We really didn’t expect DX12 to be a huge performance loss it is, but nobody really complains about that becase our expectations were managed. It is a preview, and a placeholder, and we treat it as such. No problem, it’s fair game. But they had a year to implement the controllers, and this shouldn’t have been released in this state, or they should have told that it’s just a preview, and we should expect full support at a such and such date. There would have been much less disappointment and negative reactions…