2019-04-09 at 03:24 #10818Del the GhostParticipant
okay guys i’m having trouble with setting up my full body with xbox one kinect with Driver4vr . looks like the computer doesn’t want to recognize it or something. I have the driver installed. Using htc vive PLEASE HELP2019-04-09 at 23:19 #10822ChunkyMonkey29Participant
Did you check in: Settings (gear on start menu) -> Privacy (Location, Camera) -> Camera
Under Choose which apps can access your camera is Driver4VR listed, and set to ON?
One of the “awesome” updates I received for Windows 10 broke 3d Scan, a MS app, for using the Kinect with anything, so I check it for everything now. The camera privacy can break a lot of different things when you’re not expecting it.2019-04-11 at 08:14 #108292020-05-29 at 17:51 #15124cloud-01Participant
Hi I have a quick question I am having a issue with my driver4vr. Basically the program isn’t seeing the Kinect when I start the program the Kinect switches on and stays on but the app for deiver4vr only seems my headset and controllers, I have absolutely everything installed correctly the right Kinect sdk’s etc I actually watched a tutorial to help me but it just won’t see them when I press the start button nothing happens also, could you help with this as I am unsure what the issue could be.
Regards2020-07-11 at 18:02 #15437SamSamParticipant
I’m facing the same problem with Del the Ghost.
It worked for me a few months ago. But now it suddenly does not recognize my Kinect 360 anymore. Please help.2021-01-12 at 03:27 #40727quarridorsParticipant
Same problem here, I’ve got the Xbox One Kinect working as far as getting a depth view in the verifier app, I even got a different app to display a wireframe of my limb positions. However, as soon as Driver4VR starts up, the Kinect button disappears and there’s no Kinect in the sensors list. Rebooting hasn’t helped, any ideas?
Oh and desktop apps are allowed access to camera, and Driver4VR hasn’t shown up separately on Camera Permissions settings.
Huge thanks if anyone can help!
2021-01-13 at 17:13 #40813
- This reply was modified 8 months, 1 week ago by quarridors.
Same problem here. Xbox One Kinect working fine with Kinect Studio, including depth tracking and skeleton.
Using newest Driver4VR Gold software.
Kinect does not appear in device list, so calibration is not possible.
SteamVR + Ivry with PSVR starts normally.
No errors in Driver4VR log:
2021-01-13 17:51:26: Login user completed with result: 0 2021-01-13 17:51:26: Creating communication thread... 2021-01-13 17:51:26: Creating communication done... 2021-01-13 17:51:26: Initialize communication thread. 2021-01-13 17:51:26: Communication thread test start - #1 2021-01-13 17:51:27: Connecting to SteamVR - start 2021-01-13 17:51:29: Communication thread test end - #1 2021-01-13 17:51:29: Communication thread test start - #2 2021-01-13 17:51:29: Communication thread test end - #2 2021-01-13 17:51:29: Communication thread test start - #3 2021-01-13 17:51:29: Communication thread test end - #3 2021-01-13 17:51:29: Communication thread test start - #4 2021-01-13 17:51:29: Communication thread test end - #4 2021-01-13 17:51:29: Communication thread test start - #5 2021-01-13 17:51:29: Communication thread test end - #5 2021-01-13 17:51:30: Connecting to SteamVR - returned: None 2021-01-13 17:51:30: VRPath reg output: 2021-01-13 17:51:30: Runtime path = C:\Program Files (x86)\Steam\steamapps\common\SteamVR Config path = C:\Program Files (x86)\Steam\config Log path = C:\Program Files (x86)\Steam\logs External Drivers: C:\Program Files (x86)\Steam\steamapps\common\iVRy C:\Program Files (x86)\Driver4VR\lib\drivers\driver4vr 2021-01-13 17:51:30: Connecting to SteamVR - complete 2021-01-13 17:51:30: Detected iVRy Headset. 2021-01-13 17:51:30: Creating VR Event thread... 2021-01-13 17:51:30: Creating VR Event done... 2021-01-13 17:51:30: Initialize VR Event thread. 2021-01-13 17:51:30: Connection status chanced to: Press 'Start Driver4VR' 2021-01-13 17:51:30: Stopping devices... 2021-01-13 17:51:30: Stopping devices... done. 2021-01-13 17:51:31: Status trace: stopped 2021-01-13 17:51:34: Status trace: stopped 2021-01-13 17:51:37: Status trace: stopped 2021-01-13 17:51:40: Status trace: stopped 2021-01-13 17:51:43: Status trace: stopped 2021-01-13 17:51:46: Status trace: stopped 2021-01-13 17:51:49: Status trace: stopped 2021-01-13 17:51:52: Status trace: stopped 2021-01-13 17:51:55: Status trace: stopped 2021-01-13 17:51:58: Status trace: stopped 2021-01-13 18:01:29: Creating Wii Connection... 2021-01-13 18:01:29: Creating Wii Connection... completed with success. 2021-01-13 18:01:29: End communication thread. 2021-01-13 18:01:29: End VR Event thread. 2021-01-13 18:01:29: Shutdown of driver4vr application has been completed.2021-01-13 at 18:37 #40820
Using newest Windows 10 Version + Updates, when installing both the Kinect SDK and runtime, the program manager reports 2 runtimes:
– the first one is installed via the SDK or provided by Windows driver search, so it is at least v2.2 instead of v2.0
– the second one installed manually, matches SDK v2.0_1409
I’ve tried deinstalling the newer runtime, leaving only matching v2.0_1409 runtime and SDK, even restarted Windows in between.
Did not help. Kinect Studio Montitor was working the whole time.
I’ve also noticed, that the 3d Scan Windows app was not detecting the Kinect either, so I followed the driver update instructions via device manager:
I ended up having still the SDK v2.0_1409 but the newer Runtime v2.2_1905, for which the 3d Scan app now works and the Kinect Studio monitor works as good as before.
Sadly, still no kinect device listed in Driver4VR.2021-01-14 at 01:56 #40843quarridorsParticipant
I’ve now also managed to get 3D Scan to work with the Kinect by upgrading the driver to 2.2.1905.1600. Skeleton tracking is working well everywhere else I try it, but Driver4VR always immediately removes the Kinect button once it’s fully loaded, no matter how many times I quit and reload.
I see nothing unusual in the extended logs, but also no mentions of Kinect at all.2021-01-26 at 20:46 #41548
I don’t know what exactly solved the problem, but:
– I’ve uninstalled driver4vr completely, also made sure, that the directory was program files was gone.
– I’ve downloaded and used driver4vr 220.127.116.11.
– I’ve made sure, that only 1 kinect SDK and only 1 kinect runtime are installed at the same time, starting with v2.0.1409 and then even updating the kinect device driver in the windows driver manager window, so it worked even with the v2.2 runtime.
– I realized, that the kinect one did actually activate AFTER pressing “start” in driver4vr. Only then thnb buttons for kinect calibration got enabled.
Steam VR room scaling/setup and kinect settings/calibration shows me correct body tracking at the moment. Even managed to get the psmove controllers to run using the “iVRy PSMoveService Driver for SteamVR” on steam, but I think it would have worked with the psmoveservice that you driver4vr suggests. As for me, kinect one detection works now.2021-02-12 at 22:19 #42430FarclaimerParticipant
For me I’m just not getting any power for some reason, it worked perfectly with my older pc and since i got a new one it dont wanna work anymore, saying it failed to connect ‘no power’
And yes it is plugged in2021-02-23 at 14:56 #42880
- You must be logged in to reply to this topic.