Forum Replies Created
-
AuthorPosts
-
2018-02-13 at 10:08 in reply to: What is the optimal environment/ set-up for Kinect 2.0 to body track? #3237bluekunParticipant
Kinect for Xbox One. I’m just using it for legs/ hips. I since tried putting the Kinect up higher and it does a better job when I’m sitting (still missing most of the leg movement, but it does something now).
I’ll try putting it even higher and point it down, as you’ve suggested.
Perhaps the biggest issue I’m having is how the framerate on the Kinect tracking seems to fall dramatically when I open VRChat (and then seems to persist once I’ve closed VRChat). It’s not a CPU issue (pleasantly surprised on that front) – I think it might be a USB bandwidth issue. I’ve had problems with my KB/M disconnecting after a bit when using Driver4VR in VRChat, which might be related.
I have 3 sensors, the Rift, the Kinect, my Keyboard (2 USB slots) and my mouse. Is the mobo getting overloaded, perhaps?
Thanks for the advice.
2018-02-10 at 14:56 in reply to: Calibration instructions not showing in HMD (Rift; Kinect 2.0) #3178bluekunParticipantAaand here’s some logs:
`
2018-02-10 14:41:08: Initializing driver4vr application ver: 3.8.0.0
2018-02-10 14:41:09: Attempting to login user: bluekun
2018-02-10 14:41:10: Login user completed with result: 3000
2018-02-10 14:41:10: Creating communication thread…
2018-02-10 14:41:10: Creating communication done…
2018-02-10 14:41:10: Initialize communication thread.
2018-02-10 14:41:10: Communication thread test start – #1
2018-02-10 14:41:10: Connecting to SteamVR – start
2018-02-10 14:41:11: VRPath reg output:2018-02-10 14:41:11: 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)\Driver4VR\lib\drivers\driver4vr2018-02-10 14:41:11: Connecting to SteamVR – complete
2018-02-10 14:41:11: Connection status chanced to: Driver4VR detected and not running… press ‘Start Driver4VR’ ->
2018-02-10 14:41:12: Status trace: stopped
2018-02-10 14:41:15: Status trace: stopped
2018-02-10 14:41:15: Communication thread test end – #1
2018-02-10 14:41:15: Communication thread test start – #2
2018-02-10 14:41:18: Status trace: stopped
2018-02-10 14:41:20: Communication thread test end – #2
2018-02-10 14:41:20: Communication thread test start – #3
2018-02-10 14:41:21: Status trace: stopped
2018-02-10 14:41:24: Status trace: stopped
2018-02-10 14:41:25: Communication thread test end – #3
2018-02-10 14:41:25: Communication thread test start – #4
2018-02-10 14:41:27: Status trace: stopped
2018-02-10 14:41:29: Start/Stop sequence starting.
2018-02-10 14:41:29: Kinect 360 Runtime detected: False
2018-02-10 14:41:29: Kinect One Runtime detected: True
2018-02-10 14:41:29: Kinect One – Starting connection.
2018-02-10 14:41:30: Kinect One – connected.
2018-02-10 14:41:30: Communication thread test end – #4
2018-02-10 14:41:30: Communication thread test start – #5
2018-02-10 14:41:31: Creating processing thread… start.
2018-02-10 14:41:31: Creating processing thread… done.
2018-02-10 14:41:31: Sending communication to start driver – start.
2018-02-10 14:41:31: Initialize processing thread.
2018-02-10 14:41:31: Sending communication to start driver – complete.
2018-02-10 14:41:31: Start/Stop sequence done.
2018-02-10 14:41:31: Status trace: running
2018-02-10 14:41:31: Connection status chanced to: Driver4VR detected and running!
2018-02-10 14:41:31: Enumeration of devices starting… with 0
2018-02-10 14:41:31: PS Move Service not required… skipping.
2018-02-10 14:41:31: Enumeration of devices starting completed with 0 total.
2018-02-10 14:41:31: Creating Wii Connection…
2018-02-10 14:41:31: Creating Wii Connection… completed with success.
2018-02-10 14:41:31: Starting devices…
2018-02-10 14:41:31: Starting devices complete
2018-02-10 14:41:31: Tracker update test start – #1
2018-02-10 14:41:31: Tracker update test end – #1
2018-02-10 14:41:31: Tracker update test start – #2
2018-02-10 14:41:31: Tracker update test end – #2
2018-02-10 14:41:31: Tracker update test start – #3
2018-02-10 14:41:31: Tracker update test end – #3
2018-02-10 14:41:31: Tracker update test start – #4
2018-02-10 14:41:31: Tracker update test end – #4
2018-02-10 14:41:31: Tracker update test start – #5
2018-02-10 14:41:31: Tracker update test end – #5
2018-02-10 14:41:34: Status trace: running
2018-02-10 14:41:35: Communication thread test end – #5
2018-02-10 14:41:37: Status trace: running
2018-02-10 14:41:40: Status trace: running
2018-02-10 14:43:37: Enumeration of devices starting… with 0
2018-02-10 14:43:37: PS Move Service not required… skipping.
2018-02-10 14:43:37: Enumeration of devices starting completed with 0 total.
2018-02-10 14:48:05: Shutdown of driver4vr application has been completed.
`
2018-02-10 at 14:46 in reply to: Calibration instructions not showing in HMD (Rift; Kinect 2.0) #3176bluekunParticipantNeither of these stay ticked if I close the settings or click on another tab in the settings. Not sure if relevant.
2018-02-10 at 14:32 in reply to: Calibration instructions not showing in HMD (Rift; Kinect 2.0) #3175bluekunParticipantVideo showing what I can see when calibrating. I noticed there’s head and feet indicators behind me, but I suppose that’s SteamVR. Shows that it at least recognises the Driver4VR inputs.
2018-02-10 at 14:10 in reply to: Calibration instructions not showing in HMD (Rift; Kinect 2.0) #3173 -
AuthorPosts