Oculus Rift S: Two-Handed Gun Issue

[Beaudozer]

Hey All, Playing on a Rift S, and for some reason, I was unable to move any gun that required the use of two hands while firing.

The gun would either, stay put, or skip around while I was firing, as well as on some occasions, the gun would continue to fire, even though i had stopped. This made them completely ineffective in any situation, and i ended up using only Melee and Handguns during my playthrough.

If anyone knows a fix it'd be very appreciative.

Thanks!

[GamePil]

Just wanna make sure you know, that two handed guns require both your real life hands to be in the proper position to accurately aim. Also you are using a Rift S. If i remember correctly the Rift S uses Inside-Out tracking like the WMR (No outside sensors) in which case you need to make sure that the cameras in your Headset can see the rings on your controllers at all time or you might lose tracking. Skipping Around usually happens to me when i either have too many Bluetooth devices connected at once, the controllers are running out of battery power or if the Sensors in the Headset can't see the controllers properly. No idea about the shooting issue though. Maybe this isn't on you at all and is just a general problem with the game on the Rift S but i never heard of this issue.
Have you ever played any other VR games with your Rift S where you had to use both hands to aim a gun? (H3VR, Pavlov...)

[Beaudozer]

The issue only arises when firing. I can wave the gun around perfectly fine, its only when firing.

I Also thought it was the tracking, but even when I hold the gun by my hip where my cameras on the headset can see both hands clearly, i still get the skipping issue.

Hope that clears some things up.

[GamePil]

So your gun is skipping around while firing? Never happened to me except for the obvious recoil

[ShutUpAndGoogleIt]

Test all of your USB ports. The first port I used caused the same issues you're describing but when I used another one, it worked. I fixed the issue before I played Boneworks so I'm not 100% sure it will work but give it a try.

[AK0]

its possible that something changed about how the controllers are taking haptic calls? I'm not sure how or why that would change but I will dig into it at some point to see if I can recreate the issue.

[Senvixe]

You might have defective controllers. The vibration is effecting the tracking lights. My Quest controllers have slight shaking when vibrating but its not that bad. Get your controllers looked at by oculus.

[Ktulhu]

Mine does this as well, but only when reprojection kicks in. Not sure if its due to the infamous USB power issue or what but it's so rare it doesn't really matter (at least for me)

[radioteque]

Hope it isn't too much hassle, but could you make a video of the issue?

[AK0]

Originally posted by radioteque:

Hope it isn't too much hassle, but could you make a video of the issue?

Someone else made a video of it on discord so I've seen it. It definitely seems like either a power drop or something wrong with the controller firmware (something going weird with oversaturating the haptics) I don't think its when the haptics are actually vibrating because it happened to that person even when the haptics were set to 0, it might literally just be the messages?

[radioteque]

Originally posted by Cfish:

Originally posted by radioteque:

Hope it isn't too much hassle, but could you make a video of the issue?

Someone else made a video of it on discord so I've seen it. It definitely seems like either a power drop or something wrong with the controller firmware (something going weird with oversaturating the haptics) I don't think its when the haptics are actually vibrating because it happened to that person even when the haptics were set to 0, it might literally just be the messages?

Damn I gotta see this. I'll pop in now to find it. I wonder if there's a clue in the output log somewhere.

@colemanchu, can you post the output log in your boneworks folder? It'll be in

C:\Users\(your username here)\AppData\LocalLow\Stress Level Zero\BONEWORKS

It might be too long so you may have to fileshare.

[Beaudozer]

Originally posted by radioteque:

Originally posted by Cfish:

Someone else made a video of it on discord so I've seen it. It definitely seems like either a power drop or something wrong with the controller firmware (something going weird with oversaturating the haptics) I don't think its when the haptics are actually vibrating because it happened to that person even when the haptics were set to 0, it might literally just be the messages?

Damn I gotta see this. I'll pop in now to find it. I wonder if there's a clue in the output log somewhere.

@colemanchu, can you post the output log in your boneworks folder? It'll be in

C:\Users\(your username here)\AppData\LocalLow\Stress Level Zero\BONEWORKS

It might be too long so you may have to fileshare.

Heres a Link to the Output.txt https://drive.google.com/open?id=16dn17dNV-BHbsUH54SSk-voWiHLx709a

[Banana Bitch]

me and my sister hare having the same issue on her Rift S. Only with two handed gun and only when firing. moves around weird and even stop responding to movement entirely for seconds at a time. Sometimes the triggers also act as if theyre being held down even tho we've only tapped the button once.

[GamePil]

Originally posted by ShutUpAndGoogleIt:

Test all of your USB ports. The first port I used caused the same issues you're describing but when I used another one, it worked. I fixed the issue before I played Boneworks so I'm not 100% sure it will work but give it a try.

This was my issue the first time i got my Headset. The Headset itself needed 3.0 (didn't even work with my 3.1 slots) and the Bluetooth dongle needed USB 2.0 and glitched when in a 3.0 slot

[Nomad]

You have to use a different USB Port. I noticed the same issues while - and only - firing two handed guns. Same things happened in Pavlov VR.

Rift and Rift S are very picky with USB Ports. I am using a USB Motherboard Port. Only 2 out of 6 Ports are working fine.