Reply To: Calibration instructions not showing in HMD (Rift; Kinect 2.0)

Homepage Forums How-to and troubleshooting Calibration instructions not showing in HMD (Rift; Kinect 2.0) Reply To: Calibration instructions not showing in HMD (Rift; Kinect 2.0)

#3178
bluekunbluekun
Participant

Aaand 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\driver4vr

2018-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.
`