VR controller support in SU7

I use a motion seat. A 2D mouse hardly works. If you want to understand how motion controllers work, give X-Plane a try.

Laminar have implemented VR controllers in a way that the VR team at Asobo can only dream of!

I hear you. I have a motion platorm (i.e. not just seat, but all controls move). Moust is impossible. I use a trackball, but still it’s a crutch, compared to VR controllers, or what they should have been. Obviously in current incarnation they are hardly usable.

But there is a very interesting video about UltraLeap (LeapMotion) working in MSFS! I’m afraid only in SteamVR so far, but if they can make it work with WMR OpenXR, or for those who do use SteamVR OpenXR (Reverb G2 sucks in SteamVR mode) it can be a breakthrough. When VR controllers are implemented properly, a $100+ device can make full hand tracking and manipulating everything with your hands possible.

Hi. Has anyone been able to figure out how to switch between proximity and raycasting modes using Oculus Quest 2 and it’s Touch Controllers? B is assigned to a different function (Show Taskbar) and no button is assigned to the switching between proximity and raycasting modes and the like mentioned in the quoted comment, the mapping for this functionality is not present in the options :confused: :

I want to use the proximity mode, the raycasting mode is no better than using a mouse, it’s actually worse since it’s less precise.

Yes it is one of the two top buttons on the right controller , I cannot remember if it is a or b. If not working check you have got the default touch controller profile in controller settings.

In proximity mode be careful to not bp into things. Unfortunately you can’t ā€œhideā€ your hardware yoke :wink:

Sadly… I think you’re absolutely right about VR controller implementation. We’ve waited 12 months for this to happen and what they’ve done is simply appalling. Completely unusable. However, I think their lack of commitment to VR runs even deeper. Look for example at the toolbar interaction bug in VR receiving 100s of votes and replies here on the Forum. Not having access to the toolbar prevents any serious flying in VR. How Asobo have the nerve to dub this car crash Game of the Year beats me. I can’t understand why Asobo aren’t taken to task over stuff like this during their YouTube Q and As. Instead they’re interviewed by excruciating sycophants doing the users and customers of their product a huge disservice. However, I think we all realise that these Q and A sessions are setup, managed and orchestrated well in advance to ensure nothing contentious makes it through. As I say… a huge disservice to the flightsim community. Still… not to worry… at least Asobo have prioritised the Reno Races DLC for the gamers!

I have not been waiting for controller support because I fly in VR in my home cockpit. Have most buttons mapped to hardware and only use the mouse for menu and toolbar. Thats a pain right now because of the mouse bug. But another thing thats bugging me is that every time I start a flight a menu pops up that my oculus controller has been found and if I want to use the default bindings. Clicking ok seems not being saved. Is there a way to completely switch off controller support?

Thank you! After seeing your comment I went back in and just started clicking everything and testing if it has an effect and indeed, even though it’s not shown in the controls menu, the A button on the right controller does toggle between raycasting and proximity. When I initially tested every button I didn’t know what to look for (I thought it would change to a simulated hand like in Alyx :smiley: ) and was discouraged by the lack of the binding in the menu.

However either the implementation is still a bit wonky or I need to get used to it, because when controlling the yoke it’s very difficult to be precise and it’s practically impossible to set the correct values using dials (e.g. heading on the autopilot panel), it seems that the smallest increments it uses is ~10-15.

Anyway, thanks to you I can at least test it myself :slight_smile:

Do you have to turn on the controllers? I have a G2 and just don’t turn the controllers on, and there is then no pop up like you mention. Maybe you need the controllers to be on or they are automatically turned on though.

The controller needs batteries and Bluetooth. But I don’t use that because my hardware works better. I use a M-Panel from VRinsight to control my AP. This is able to use it nearly blind.

I also use H/W panels:

  • Honeycomb Yoke with plenty of buttons
  • Saitek throttle
  • DIY panel with encoders and buttons
  • 2 Behringer X-Touch minis (MIDI)
  • Novation LaunchPad Mini for FMS/CDU (MIDI)
    Enough buttons, switches, encoders for CRJ.

But this should not be an excuse for poor VT controller implementation for the folks who don’t like to be VR cockpit builders.

I totally agree and I also add another problem with VR controls:

With the controls in LOCKED mode, the G530’s knob cannot be pressed. The two knobs on each side can be turned, both wide and narrow, but nothing can be selected by pressing the tip of the narrow knob.

If I change the mouse to LEGACY mode, I can press the knob with the mouse, but with the VR control you cannot press in any way.

Can someone please confirm whether Quest 2 controllers can turn, flip or select knobs? They only work for menus for me.

Do you have ā€œlockā€ interaction mode enabled? Or ā€œlegacyā€? Legacy will not worjk with VR controllers. If you don’t know what I mean, search the forum.
I use G2, but the ā€œlockā€ interaction mode is applicable to all headsets/controllers I believe.

I can confirm my Quest 2 Touch Controllers work. I have the lock interaction mode set and you can use A on the right controller to switch between proximity and raycast modes. In my testing I was able to select all the switches and knobs etc and flip them and turn them in proximity mode. Also make sure you’re testing with a compatible aircraft as apparently not all are made controller ready yet (like the Cessna Longtitude, it’s not VR controller ready).

Same here. I can’t click anything in the cockpit with my quest 2 controller. Since the menus are not working anyway I’m grounded. Have to wait for the fix. One of the worst experiences right now as VR is not playable at all.

@stekusteku; @mrConkerNoob - Thanks for the hint, I’ll try that.

BTW I suggest you all vote here: this is how VR SHOULD be like. And there’s nothing preventing it from working that way, if Asobo wants to do it. Look at the second video. Even the first video, when VR Controllers will be properly supported, can be a game changer Not for G2 users though. For us there needs to be a native support. That will improve the SteamVR user experience (by showing hands instead of controllers etc.) and work with WMR HMDs.

You are welcome ! And I agree the implementation is strange. The yoke is often far too sensitive and not a 1/1 mapping to controller movement. It seemed better in the TBM than the cessnas but I only flew it once so need to double check. Then with joystick aircraft like A320, I really don’t like that I cannot tilt the controller to tilt the joystick.

Regarding the autopilot dials, somebody posted a good workaround which is to manually set the thumbsticks to increase/decrease the dial by one unit.

Controller is now working but still unusable in many aspects - one aspect is the delay when turning a knob, it works and then a delay and sometimes the vs selector jams, resulting in a continuous scroll which causes the plane to stall and any attempt to go the other way results to diving steeply. The sim is unusable. The mouse doesn’t work and the solution of Ctrl+0 changes the view. I’ll try unmapping that to see if it works without changing view - It is crazy, isn’t it?