Open Ruikio opened 3 years ago
I'm sorry to hear you're having issues, but those problems are unfortunately in parts other than Neos, so there's not too much that we can do about those directly. All the USB and wireless communication is handled by SteamVR and your system drivers, Neos doesn't touch that at all.
What's likely is that Neos is triggering some underlying system issue in the drivers or your system with its pattern of usage, but you'd still need to address that.
One thing that comes to mind is your BIOS - have you updated it to the latest version? Which motherboard you have? Some AMD motherboards had issue where the USB would randomly disconnect due to high chatter on the PCI-E bus, with was fixed with AGESA 1.2.0.2 BIOS (or later), trying that might be worth a try.
Isn't there a way to go back to older versions to test things? Like I said this just happened out of the blue with a random Neos patch. I just thought it was the usb cord or something so I picked up a new one. My PC normally sits at high CPU usage when I use Neos. Which is has for years. This issue just recently popped up.
I have not updated my Bios but I can look into that. I've listed my Motherboard below
You could use Steam depot downloader to get an older version of Neos from Steam: https://github.com/SteamRE/DepotDownloader
However even if there's a difference I'm not sure it's something we could fix on our end, since this is a system issue - nothing Neos does should be able to break USB and wireless communication like this, that's handled completely outside of Neos.
You could use Steam depot downloader to get an older version of Neos from Steam: https://github.com/SteamRE/DepotDownloader
However even if there's a difference I'm not sure it's something we could fix on our end, since this is a system issue - nothing Neos does should be able to break USB and wireless communication like this, that's handled completely outside of Neos.
Gonna restart everything, try sitting in VRC for an hour and see if anything happens. If not, I'm gonna try a few things:
Something to also consider is Neos doesn't let the Vive Pro Eye HMD start Neos unless you allow the eye tracking software to be on. I mean iirc anyway. I remember hitting no on letting it start and my Neos refused to do anything. So it could be how Neos interacts with the eye tracking software aswell?
Like I said. As soon as I sacrifice the eye tracking and mouth tracking, everything becomes fine again. I just unplug and replug the USB that connects the 3-in-1 connector box and everything returns to normal.
Disabling eye and mouth tracking essentially disconnects two (three?) web cameras from your USB network. As your USB is now under lighter load, it behaves more stable.
Neos tries to initialize SRAnipal if it is detected, so if SRAnipal has problems, Neos would indeed have trouble loading. As far as I remember there's an option to force SRAnipal usage (if you have no eye tracking, but want to use mouth tracking), but there's no way to disable SRAnipal usage.
Small update: I tried Neos without the mouth tracker. Still does the disconnecting of my hands. Unplugging the USB and replugging brought it back. Which means only thing that's left is eye tracking and maybe too much draw somewhere.
Can someone else drop their eye tracker SRanipal (Eye tracker stuff) versions?
Runtime Version: 1.3.1.1
Runtime Type: Public
Eye Camera Version: 2.41.0-942e3e4
Lip Camera Version: 50100
I'm curious if I'm using out dated software. If so I need to see if I can find an updater or something. The one in the folder doesn't run or open or do anything.
You seem to be actually on an older version of SRAnipal. Mine is 1.3.2.0
, everything else is the same.
You seem to be actually on an older version of SRAnipal. Mine is
1.3.2.0
, everything else is the same.
Do you happen to know how to update to the newer version?
Enverex provided the site to update. Which you should also update, Froox. 1.3.3.0 seems like it's only an SDK
Will check here to see if this solves my problem.
https://developer.vive.com/resources/vive-sense/sdk/vive-eye-and-facial-tracking-sdk/
Updated bios. Updated eye tracker software.
Did not help at all. What else is there to try?
Different combinations of USB ports may be able to resolve this, I feel the issue is likely the USB controller can't keep up, if you have multiple 3.0 USB ports (normally they are blue or sometimes red) shifting your plugs around may help.
Devices like keyboards and mice don't need those data rates, but the headsets do and trackers may need them depending on how your USB network is laid out.
Different combinations of USB ports may be able to resolve this, I feel the issue is likely the USB controller can't keep up, if you have multiple 3.0 USB ports (normally they are blue or sometimes red) shifting your plugs around may help.
Devices like keyboards and mice don't need those data rates, but the headsets do and trackers may need them depending on how your USB network is laid out.
I tried shuffling it around to the two USB 3.0s on the back of my PC. The only thing I can try now is the single one on the front of my PC. I'll try it today here and report back.
Is there anything else you could look into? Like I don't know, Neos logs since it only happens in Neos, I have the SteamVR System Report. It's just up in the air at the moment and it's taxing mentally ~__~ @Frooxius
Information that could be helpful: When I use my Vive Pro Eye mic. It's very high pitched for some reason. Almost as if I am talking on helium. That's what people tell me and I don't know if that info will help at all.
Vive support let me know:
NVIDIA has reported an issue with graphics driver versions 471.11, 471.41, and 471.68, but don't worry, we've found that using the NVIDIA graphics driver version 466.77 seems to prevent symptoms from occurring.
So I'll try this and also report back.
The only problem with this is, I haven't updated my GPU in awhile. Everything was working fine and then the next day it wasn't. I actually updated the drivers BECAUSE I thought it was a potential problem.
More info now that I've thought of it. Yesterday during the stream I actually noticed my eye tracking would work and stop working randomly on and off until eventually my hands loss tracking, even with a green light.
Also more info that may help: When I did plug in my fullbody using the vive trackers, my headset would start randomly grey screening where as it didn't before. Even when losing tracking of my hands.
If I start up my VR right now. I can play the game that requires eye tracking and have control of my hands and eye tracking. Eventually my eye tracking turns off and back on a few times and eventually my controllers lose their tracking (Green lights, but pulsing blue showing they aren't tracking on SteamVR)
I'm using the Vive Pro Eye HMD and Index Knuckles controllers.
Information that could be helpful: When I use my Vive Pro Eye mic. It's very high pitched for some reason. Almost as if I am talking on helium. That's what people tell me and I don't know if that info will help at all.
I think that’s a known issue, you can fix it with the steps here: https://forum.vive.com/topic/8972-sudden-high-pitch-mic-issues-on-vive-pro-hmd/?do=findComment&comment=38431
As a note, I was experiencing a similar issue with my Vive Pro Eye, with the addition of hearing USB connect / disconnect sounds. I replaced my headset cable, but I’m sunrise if that would work in your situation.
There's actually another thing that might help. With my laptop, I had similar issues whenever the camera on the front of the headset was in the system, even if it wasn't actively used.
Go to Device Manager in Windows and under Cameras disable the "VIVE Pro Multimedia Camera" using "Disable Device". On my laptop that has fixed those kinds of symptoms.
I think anything that reduces the amount of data going through your motherboards USB controller may help then, an additional pci based set of USB ports may help offload the speed into another controller. If your motherboard is having trouble with all the add-ons.
Describe the bug?
After playing VrChat for hours and not having any problems. Seems it's not just my VR acting up. Everything has been fine for the last year-ish with this headset until a week or two ago.
It seems a Neos update is making my VR act up. One hand will lose tracking (Blue pulsing on SteamVR, lights on controllers still green) and then the other will lose tracking 5 - 6 minutes after. When in Full Body my headset will go grey sometimes (Doesn't happen when FBT is off) When playing without Full Body, I make sure the dongles and USB hub are not plugged in.
Changing USBs fixes it and brings my hands back. At the cost of my eye tracking & mouth tracker which means I need to restart my VR to get them back.
Things I've tried:
Runtime Version: 1.3.1.1
Runtime Type: Public
Eye Camera Version: 2.41.0-942e3e4
Lip Camera Version: 50100
Relevant issues
Nope
To Reproduce
Be inside Neos for an hour or so.
Expected behavior
My controllers actually working.
Log Files
No response
Screenshots
No response
How often does it happen?
Always
Does the bug persist after restarting Neos?
No
Neos Version Number
2021.8.27.914
What Platforms does this occur on?
Windows
Link to Reproduction Item/World
No response
Did this work before?
Yes
If it worked before, on which build?
About two to three weeks ago
Additional context
When I unplug my USB and replug it back in, it kills my mouth and eye tracking. But it also gives my hands back.
When I put full body on, my headset starts to grey screen. Without full body, it's perfectly fine.
Reporters
Rukio#0001