Is there setting for me to be able to use my honeycomb yoke and throttle in vr with the quest 2? Im new to using vr here but seems like experience is a ton better. The game wants me to use my occuclus controllers by default. Ive looked for a setting and tried finding some info on youtube but nothing. Thanks for any help. If this works I would love to upgrade to a better vr headset!
Just plug them in and use as normal…?
the occulus controllers show up on my screen. I moved the one out of the area and then have no controls. I was wondering if theres a setup option to default to the honeycomb or what. I have no idea. If anyone is using a quest 2 and honeycomb please let me know. I have a very high end pc and stream to my occulus via steam vr and virtual desktop.
The first thing to check is if the Honeycomb shows up in the Options::Control Options, and that the controls are assigned to the appropriate function. (You may need to scroll sideways to see it.)
If it’s not there in VR, check in 2D with the VR headset disconnected.
I have a honeycomb setup in combination with virtual desktop and a Quest 2 running. Never had any problems though. I think you will have to look into your virtual desktop settings, you probably have some input emulation active. In the input section of virtual desktop (in VR) I have enabled all input options except for “thumbstick horizontal scrolling” and “hand tracking”. The “gamepad” and “emulate d-pad” options are all turned off. Please check if these settings match on your end first.
You solved it. It was a setting in virtual desktop, Hand tracking and thumbstick hoizontal scrolling were on. I had disabled hand tracking in my occulus but never thought to look in virtual desktop. Thanks so much! It was causing crashes too.
I still get a jittery screen though when loading from a main menu. Any ideas on that?
Glad to hear so! That jittery screen is and has always been there for me too. I hope they will resolve it one day. It would be interesting to hear if other people with different headsets have the same issue.