Draken35 Posted October 20, 2021 Posted October 20, 2021 (edited) OB 2.7.7 - Oculus (QUEST 2) hand controllers Y & B buttons not responding while in cockpit (KA-50, A-10CII and AV8B at least, haven't tried in others yet) No hardware issue... they work fine outside the cockpits and in other apps. Edited October 20, 2021 by Draken35
Enduro14 Posted October 20, 2021 Posted October 20, 2021 so with this update our oculus controllers are now mappable in the control settings, So have to map the buttons to what you want now Intel 8700k @5ghz, 32gb ram, 1080ti, Rift S
Draken35 Posted October 21, 2021 Author Posted October 21, 2021 2 hours ago, Enduro14 said: so with this update our oculus controllers are now mappable in the control settings, So have to map the buttons to what you want now Thank you! This is actually quite cool! They show as controllers in the control tab when you are in VR. Also, there are a couple of new checkboxes in the VR tab to enable/disable the use of the stick and throttle with VR controllers. But is this in the change log? If so, I totally missed it !
Enduro14 Posted October 21, 2021 Posted October 21, 2021 1 minute ago, Draken35 said: Thank you! This is actually quite cool! They show as controllers in the control tab when you are in VR. Also, there are a couple of new checkboxes in the VR tab to enable/disable the use of the stick and throttle with VR controllers. But is this in the change log? If so, I totally missed it ! Nope not in Chang log Intel 8700k @5ghz, 32gb ram, 1080ti, Rift S
DMouse Posted October 21, 2021 Posted October 21, 2021 The problem now is that you can only use the hand controller buttons if you enable the hand controllers in the VR options menu. I used to use mine to re center my view point , but use the mouse for all the cockpit clickable items. Now the hand controllers don't allow that. I also cannot assign the hand controller buttons to a function, not sure why?
Mezsh Posted October 22, 2021 Posted October 22, 2021 I have exactly the same issue. For the last 2 years, I have used my hand controller to reset my cockpit view. Yes, yes, yes, I know you can do the same thing by pressing "5" on the Numpad, but then you have to lift up your visor to see the keyboard, whereas previously I could just reach for my controller to reset my view WITHOUT having to lift my headset up. PLEASE can we get this resolved, and the original functionality restored WITHOUT having to enable hand controllers in VR. 2
Auger Posted October 22, 2021 Posted October 22, 2021 This last patch really messed things up, for me at least. I kept wondering why my Harrier would start diving toward the ground even though I had autopilot set... kept wondering why the joystick in the cockpit was jumping around even though Windows game controller showed my HOTAS steady as a rock. Well, turns out that the last update set my thumb controllers as pitch and roll, not to mention a slew of other commands with the buttons.Clearing the Oculus control column hopefully cleared this up but I haven't tried it yet as I'm now looking for a solution as to why my FPS has dropped to the mid 20's. Everything was working great before the patch, now it's almost unplayable.
Draken35 Posted October 22, 2021 Author Posted October 22, 2021 1 hour ago, Auger said: This last patch really messed things up, for me at least. I kept wondering why my Harrier would start diving toward the ground even though I had autopilot set... kept wondering why the joystick in the cockpit was jumping around even though Windows game controller showed my HOTAS steady as a rock. Well, turns out that the last update set my thumb controllers as pitch and roll, not to mention a slew of other commands with the buttons.Clearing the Oculus control column hopefully cleared this up but I haven't tried it yet as I'm now looking for a solution as to why my FPS has dropped to the mid 20's. Everything was working great before the patch, now it's almost unplayable. I had the same issue with the Harrier, quickly realized what it was and cleared out the Oculus controllers axis and it, indeed, fixes it. I haven't experienced any drop of fps (knock on wood).
Wiggl Posted October 23, 2021 Posted October 23, 2021 Same Problem for me, used left Y to center view and left X to get to the menus. Now even if i can map Buttons it still will not accept and will recenter with left X and ignores Left Y. Im slightly at a loss here since it seems like the Left X is somwhat now Hardcoded to Center View.......
Auger Posted October 23, 2021 Posted October 23, 2021 5 minutes ago, Wiggl said: Same Problem for me, used left Y to center view and left X to get to the menus. Now even if i can map Buttons it still will not accept and will recenter with left X and ignores Left Y. Im slightly at a loss here since it seems like the Left X is somwhat now Hardcoded to Center View....... I thought that also, but in reality you have to go in and clear that column for every plane you have. I also cleared "General" and "UI". I was then able to assign the buttons I wanted to the command I wanted. Also, assigning the controller buttons is not like assigning the HOTAS buttons, where you open the box and then press the HOTAS button you want to assign.... instead when you open the box in the column (mine said Oculus) you have to use the pull down menu and select which button, A B X or Y, or thumb controller you want to assign to that particular command. For example, I assigned my A button to bring up the Communication menu, the B button to bring up the End Mission menu, the X button to bring up the Kneeboard and pushing in right and left sticks cycles the pages of the Kneeboard. I'm sure I'll make some changes in time, but it's actually working pretty well. I just wish that when we got the patch, there would not have been buttons already assigned. It was a bit time consuming to go in and clear each and every plane and helicopter. Still... the more I'm using the controller buttons for my selected commands, the more I'm liking it.
Hempstead Posted November 5, 2021 Posted November 5, 2021 On 10/22/2021 at 3:31 PM, Auger said: This last patch really messed things up, for me at least. I kept wondering why my Harrier would start diving toward the ground even though I had autopilot set... kept wondering why the joystick in the cockpit was jumping around even though Windows game controller showed my HOTAS steady as a rock. Well, turns out that the last update set my thumb controllers as pitch and roll, not to mention a slew of other commands with the buttons.Clearing the Oculus control column hopefully cleared this up but I haven't tried it yet as I'm now looking for a solution as to why my FPS has dropped to the mid 20's. Everything was working great before the patch, now it's almost unplayable. Talk about messed up control defaults. For YEARS, I thought DCS was just ridiculous with its flight model. My P51 and A10 would just bank left hard, invert, and dive whenever I pull the stick back a bit hard. Come on, prop procession isn’t that bad! Not on real Cessna, or Piper! Sure, P51 is a very powerful plane that I have never flown in real life, but this is some ridiculous banking that requires an uncle Chuck in order to just cruise, let alone fight. Not everyone flies the X-1, you know. Oh, and the A10 is a twin jet. There shouldn’t be any prop procession! So, I never really got into DCS, and wrote it off as a bad investment! Those are the two cheap modules I buy to try it out. Didn’t work out…. Move on. I even offered a cast bronze F16 TQS as the reward to a local fellow simmer friend to fix it for me. He didn’t take it, after I described the symptom to him. I finally figured it out myself. For some reason I could never understand, the damned thing would automatically assign all controllers it detects with X, Y, Rz to roll/pitch/yaw, including the damned mouse’s! Oh, and my Razer optical keyboard, and keypad also emulate joysticks. And vJoy joins the party too! All of them! So I would end up with multiple controllers all trying to control roll/pitch/yaw. And it would not manifest until I pull back on the stick a bit hard. So, I would take off ok…. And fly around, land fine…. But as soon as I tried any “maneuver”, it would bank left hard and dive! What? No split-S, you stupid plane! Haw, haw haw…. Old timers are probably laughing their rear ends off… everybody knows that, you rookie! Well, never in my wildest dream would I dream of programming it to assign all controllers’ X/Y/Rz to roll/pitch/yaw. There is the right way, the wrong way, the army way, and there is just the idiotic way. There is just no bloody reason to spend that extra effort to default it wrong! What are you trying to pull? Screw with new customers? And trying to discourage players changing/adding controllers? What for??? So, that was the last place I would have ever looked! Come on…. Nobody would…. Worse… every time I plug in a new controller, it detects and assigns the new X/Y/Rz to roll/pitch/yaw too! I plug in my Saitek yoke I use for flying 787 in MSFS 2020, my DCS F16 starts banking/rolling unintended! So, every time I add a new controller, I would have to go in and clear every single plane’s X/Y/Rz for the new controller. WTF? Even worse, I write my own USB firmware for controllers, so I often have “new” controllers to try out! This just drives me nuts! Come on, ED. Stop this auto-wrong!
atrcaptainjohn Posted December 16, 2021 Posted December 16, 2021 Has anyone figured out a solution to this? The only way I can map the VR Controller buttons is to enable the controllers in the UI Layer, but then I can't use the mouse to click on anything anymore. When I disable the hand controllers I can no longer use the buttons but I can once again use the mouse.
Recommended Posts