[Hyacin]

Yours sounds like a bandwidth issue and not the same problem at all.

From – https://support.xbox.com/en-US/xbox-on-windows/accessories/kinect-for-windows-v2-known-issues

Only USB3 controllers from Intel and Renesas are supported
If you use a different brand of USB3 controller, the Kinect sensor may not function correctly. For example:

The sensor may fail to enumerate
Depth may not stream
Color may not stream
The sensor may stop functioning
Packet loss may increase

Via isn’t on that list, and they aren’t joking when they say what is supported. I bought a card with USB 3.1 and all this crap and thought “This is WAY more advanced than what they call for, it HAS to work” … it’s sitting in a drawer getting dusty now – I had to buy a Renesas card to make it work – despite even having an Intel controller on my board.

The different with my problem, is mine works fine, for 12 hours, or a day, or three days sometimes – but then it stops and nothing will make it work again except a reboot. It does not sound like yours is ever working at all.

[Hyacin]

I experienced this too. I tried lowering the leg height since there is no specific value for feet, but I couldn’t figure out after if it had made any difference.

[Hyacin]

So, does this imply that there is exposure control on Kinect One, and, that you modify it when driver4vr fires up? Because I just finished a driver4vr session and launched Kinect Configuration Verifier to get the camera lined up right (I think it was bumped since I last used it) and I noticed the picture was very, very, very dark. So much so I thought my Kinect was broken. driver4vr has already exited at this point. I’m in the middle of a few things, so I can’t reboot to verify – but if driver4vr is modifying the exposure, it should probably reset it to default or where it was on exit if it’s not, which I suspect it is not.

Sorry, odd place to post this I know, but the bit at the top got me thinking about it.

• This reply was modified 5 years, 9 months ago by Hyacin.

[Hyacin]

Absolutely nothing to do with driver4vr!

I’m having trouble getting my Kinect to work at all … when it is working, driver4vr works perfectly! 🙂

I’m just having issues with USB buses and bandwidth – unsupported controller, etc. … I wish I had known they recommended Renesas – there was a Renesas card at the store I went to for the same price as I paid for my ASMedia card, I would have got that instead.

[Hyacin]

I thought the same about using it for hands – but I would assume we can not do that. Doing that would replace our controllers with “Trackers” as far as SteamVR is concerned … so where then would the input be coming from? Unless you did some complex back-end mapping stuff maybe …

I’m still having problems with my Kinect cutting out. In my initial configuration it wasn’t working for Windows Hello at all practically, but once the system was fully booted I could get it going in software. After adding a PCI-E controller and disabling a couple of the onboard controllers, I seem to have the opposite now … on a fresh wake-up it works perfectly for Windows Hello, but any attempt to access the Kinect after the system is up and running fails – so I don’t think I’m going to get a lot of play or configuration testing done until I get that sorted out 🙁

[Hyacin]

I just got my Kinect v2 … the trial of driver4vr didn’t even give me enough time to get things set up, so, that kinda sucked … I bought it though as it was looking promising at that point …

I had to seriously fight with my system to get WMR and the Kinect working at the same time … they are both major USB bandwidth hogs …

Despite having two distinct controllers on my motherboard, and separating them off to have a dedicated one for each, and getting everything else off those controllers – the Kinect was still VERY flaky, Windows Hello (the first thing I set up) would often report “Something went wrong, log in using PIN” …

I got them both steady and stable at one point and managed to do the calibration … “no head” “no hands” “yes body” … all looked well …

I fired up VAM, and while it was loading and I was on the SteamVR “Holodeck” I was able to see three extra Vive controllers! One on each of my feet, and one for my hips …

Sadly, VAM does not support the Vive trackers yet :'(

But, while in there and doing a “hard reset” to bring me back to the Holodeck environment, I was clearly being fully tracked … two feet, one hips, two hands, and there was no mirror, but I’m sure my head.

So this IS working with a WMR (Dell Visor) setup for me! Just the one title I bought all this for doesn’t support it yet, lol …

I’ll try to find some other things that do support the trackers this weekend and play around and probably report back.

OH, and even with having them stable for long enough to confirm things were working – the Kinect still eventually flaked out, so I figured it was still a bandwidth thing and went out and got a USB 3.1 PCI-E 4x controller to dedicate to it. So far that has done nothing but cause other system issues (my onboard Intel NIC stopped working so I had to switch over to the Realtek) – so I’m not 100% sure if the issues are resolved … but I wanted to report in quick to say that I do have a Kinect v2 + driver4vr + WMR setup working perfectly.

[Hyacin]

I hope MMV because I just caught a sweet deal on a Kinect 2 modded for PC use, so I picked it up! Should be here in a week or so, and aside from VRidge/Riftcat, the Dell Visor is the only headset I have (and I am not going to drop cash on a new headset just for it to play nice with Driver4VR for the couple games I can use it in.)

[Hyacin]

I’m hoping to pick up a Kinect & Adapter simply for the full body tracking it (with this) can add to my WMR setup. I’m just hoping the IR blasting from the Kinect doesn’t interfere with the IR emitting from the controllers and confuse the cameras on the WMR HMD.

[Author]

Posts