Sensor became unresponsive

Depthkit Depthkit Studio
1

I’m working on a livestreaming project in Unity 2022.3.21f1.
However, when I start the game, it unpredictably crashes within 1 to 10 minutes.

The error messages:

2025-03-07 15:51:42.407 INFO [12824] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::startStream@796] Orbbec Femto Bolt CL8FC310081: Starting streams in subordinate sync mode
2025-03-07 15:51:43.437 INFO [24728] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::frameProcessingThreadFunction@914] Orbbec Femto Bolt CL8FC310081: Waiting for controller to begin…
2025-03-07 15:51:43.438 INFO [12824] [Depthkit::DepthSensorStage::setSensor@226] Using sensor: Orbbec Femto Bolt, id: CL8S93P00B3
2025-03-07 15:51:43.441 INFO [12824] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::startStream@796] Orbbec Femto Bolt CL8S93P00B3: Starting streams in subordinate sync mode
2025-03-07 15:51:44.495 INFO [17796] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::frameProcessingThreadFunction@914] Orbbec Femto Bolt CL8S93P00B3: Waiting for controller to begin…
2025-03-07 15:51:44.496 INFO [12824] [Depthkit::DepthSensorStage::setSensor@226] Using sensor: Orbbec Femto Bolt, id: CL8S93P009W
2025-03-07 15:51:44.500 INFO [12824] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::startStream@796] Orbbec Femto Bolt CL8S93P009W: Starting streams in subordinate sync mode
2025-03-07 15:51:45.529 INFO [25340] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::frameProcessingThreadFunction@914] Orbbec Femto Bolt CL8S93P009W: Waiting for controller to begin…
2025-03-07 15:51:45.529 INFO [12824] [Depthkit::DepthSensorStage::setSensor@226] Using sensor: Orbbec Femto Bolt, id: CL8A842011T
2025-03-07 15:51:45.533 INFO [12824] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::startStream@796] Orbbec Femto Bolt CL8A842011T: Starting streams in subordinate sync mode
2025-03-07 15:51:46.569 INFO [26224] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::frameProcessingThreadFunction@914] Orbbec Femto Bolt CL8A842011T: Waiting for controller to begin…
2025-03-07 15:51:46.570 INFO [12824] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::startStream@793] Orbbec Femto Bolt CL8A8420146: Starting streams in controller sync mode
2025-03-07 15:51:47.606 INFO [25340] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::frameProcessingThreadFunction@985] Orbbec Femto Bolt CL8S93P009W: Controller started!
2025-03-07 15:51:47.606 INFO [17796] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::frameProcessingThreadFunction@985] Orbbec Femto Bolt CL8S93P00B3: Controller started!
2025-03-07 15:51:47.606 INFO [26224] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::frameProcessingThreadFunction@985] Orbbec Femto Bolt CL8A842011T: Controller started!
2025-03-07 15:51:47.732 INFO [24728] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::frameProcessingThreadFunction@985] Orbbec Femto Bolt CL8FC310081: Controller started!
2025-03-07 15:52:32.364 INFO [17796] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec Femto Bolt CL8S93P00B3: [03/07 15:52:32.364320][warning][17796][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66

2025-03-07 15:52:33.435 INFO [26224] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec Femto Bolt CL8A842011T: [03/07 15:52:33.435128][warning][26224][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66

2025-03-07 15:52:33.436 INFO [25340] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec Femto Bolt CL8S93P009W: [03/07 15:52:33.436083][warning][25340][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66

2025-03-07 15:52:33.473 INFO [24728] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec Femto Bolt CL8FC310081: [03/07 15:52:33.473677][warning][24728][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66

2025-03-07 15:52:33.827 INFO [30308] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec Femto Bolt CL8A8420146: [03/07 15:52:33.827343][warning][30308][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66

2025-03-07 15:52:36.473 INFO [26968] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:52:36.473311][warning][26968][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [5 logs in 4108ms, last: 15:52:34.747658]

2025-03-07 15:52:36.690 INFO [26224] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec Femto Bolt CL8A842011T: [03/07 15:52:36.690211][warning][26224][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [7 logs in 3255ms]

2025-03-07 15:52:36.692 INFO [25340] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec Femto Bolt CL8S93P009W: [03/07 15:52:36.692222][warning][25340][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [7 logs in 3256ms]

2025-03-07 15:52:36.694 INFO [24728] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec Femto Bolt CL8FC310081: [03/07 15:52:36.694219][warning][24728][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [7 logs in 3220ms]

2025-03-07 15:52:36.888 INFO [30308] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec Femto Bolt CL8A8420146: [03/07 15:52:36.888780][warning][30308][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [4 logs in 3061ms]

2025-03-07 15:52:42.694 INFO [28812] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:52:42.694174][warning][28812][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [8 logs in 6220ms, last: 15:52:41.772666]

2025-03-07 15:52:43.164 INFO [30308] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec Femto Bolt CL8A8420146: [03/07 15:52:43.164022][warning][30308][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [10 logs in 6275ms]

2025-03-07 15:52:43.164 INFO [26224] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec Femto Bolt CL8A842011T: [03/07 15:52:43.164461][warning][26224][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [8 logs in 6474ms]

2025-03-07 15:52:43.165 INFO [25340] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec Femto Bolt CL8S93P009W: [03/07 15:52:43.165012][warning][25340][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [6 logs in 6472ms]

2025-03-07 15:52:43.181 INFO [24728] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec Femto Bolt CL8FC310081: [03/07 15:52:43.181570][warning][24728][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [4 logs in 6487ms]

2025-03-07 15:52:55.167 INFO [21644] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:52:55.167862][warning][21644][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [2 logs in 12473ms, last: 15:52:46.556174]

2025-03-07 15:52:55.365 INFO [20520] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:52:55.365008][warning][20520][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [1 logs in 12200ms, last: 15:52:43.364912]

2025-03-07 15:52:55.377 INFO [28764] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:52:55.377531][warning][28764][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [2 logs in 12212ms, last: 15:52:45.599853]

2025-03-07 15:52:56.829 INFO [20504] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:52:56.829775][warning][20504][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [1 logs in 13648ms, last: 15:52:44.829468]

2025-03-07 15:52:58.390 INFO [28940] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:52:58.390788][warning][28940][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [1 logs in 15226ms, last: 15:52:46.389992]

2025-03-07 15:53:07.367 INFO [30308] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec Femto Bolt CL8A8420146: [03/07 15:53:07.367002][warning][30308][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [6 logs in 12002ms]

2025-03-07 15:53:07.590 WARN [17796] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P00B3] Frame set is missing depth frame. 2
2025-03-07 15:53:07.613 WARN [17796] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P00B3] Frame set is missing depth frame. 3
2025-03-07 15:53:07.613 WARN [17796] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P00B3] Frame set is missing depth frame. 4
2025-03-07 15:53:07.613 WARN [17796] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P00B3] Frame set is missing depth frame. 5
2025-03-07 15:53:07.622 WARN [30308] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A8420146] Frame set is missing depth frame. 2
2025-03-07 15:53:07.625 WARN [25340] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P009W] Frame set is missing depth frame. 2
2025-03-07 15:53:07.634 WARN [24728] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] Frame set is missing depth frame. 2
2025-03-07 15:53:07.634 WARN [24728] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] Frame set is missing depth frame. 3
2025-03-07 15:53:07.634 WARN [17796] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P00B3] Frame set is missing depth frame. 6
2025-03-07 15:53:07.640 WARN [26224] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A842011T] Frame set is missing depth frame. 2
2025-03-07 15:53:07.641 WARN [26224] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A842011T] Frame set is missing depth frame. 3
2025-03-07 15:53:07.643 WARN [30308] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A8420146] Frame set is missing depth frame. 3
2025-03-07 15:53:07.652 WARN [25340] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P009W] Frame set is missing depth frame. 3
2025-03-07 15:53:07.657 WARN [24728] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] Frame set is missing depth frame. 4
2025-03-07 15:53:07.657 WARN [17796] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P00B3] Frame set is missing depth frame. 7
2025-03-07 15:53:07.658 WARN [26224] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A842011T] Frame set is missing depth frame. 4
2025-03-07 15:53:08.839 INFO [24728] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec Femto Bolt CL8FC310081: [03/07 15:53:08.839381][warning][24728][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [13 logs in 12009ms]

2025-03-07 15:53:08.907 WARN [24728] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] Timed out waiting for a frame set. 2
2025-03-07 15:53:09.148 WARN [24728] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] Timed out waiting for a frame set. 2
2025-03-07 15:53:09.208 WARN [30308] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A8420146] Timed out waiting for a frame set. 2
2025-03-07 15:53:09.213 WARN [17796] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P00B3] Timed out waiting for a frame set. 2
2025-03-07 15:53:09.214 WARN [24728] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] Timed out waiting for a frame set. 3
2025-03-07 15:53:09.268 WARN [24728] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] Frame set is missing depth frame. 5
2025-03-07 15:53:09.299 WARN [24728] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] Frame set is missing depth frame. 6
2025-03-07 15:53:09.321 WARN [25340] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P009W] Frame set is missing depth frame. 4
2025-03-07 15:53:09.324 WARN [24728] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] Frame set is missing depth frame. 7
2025-03-07 15:53:09.334 WARN [17796] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P00B3] Frame set is missing depth frame. 8
2025-03-07 15:53:09.334 WARN [17796] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P00B3] Frame set is missing depth frame. 9
2025-03-07 15:53:09.344 WARN [30308] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A8420146] Frame set is missing depth frame. 4
2025-03-07 15:53:09.344 WARN [30308] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A8420146] Frame set is missing depth frame. 5
2025-03-07 15:53:09.344 WARN [30308] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A8420146] Frame set is missing depth frame. 6
2025-03-07 15:53:09.346 WARN [25340] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P009W] Frame set is missing depth frame. 5
2025-03-07 15:53:09.346 WARN [25340] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P009W] Frame set is missing depth frame. 6
2025-03-07 15:53:09.346 WARN [25340] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P009W] Frame set is missing depth frame. 7
2025-03-07 15:53:09.349 WARN [24728] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] Frame set is missing depth frame. 8
2025-03-07 15:53:09.349 WARN [24728] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] Frame set is missing depth frame. 9
2025-03-07 15:53:09.349 WARN [24728] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] Frame set is missing depth frame. 10
2025-03-07 15:53:09.349 WARN [24728] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] Frame set is missing depth frame. 11
2025-03-07 15:53:09.349 WARN [24728] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] Frame set is missing depth frame. 12
2025-03-07 15:53:09.349 WARN [24728] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] Frame set is missing depth frame. 13
2025-03-07 15:53:09.356 WARN [26224] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A842011T] Frame set is missing depth frame. 5
2025-03-07 15:53:09.356 WARN [26224] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A842011T] Frame set is missing depth frame. 6
2025-03-07 15:53:09.365 WARN [30308] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A8420146] Frame set is missing depth frame. 7
2025-03-07 15:53:09.366 WARN [30308] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A8420146] Frame set is missing depth frame. 8
2025-03-07 15:53:09.372 WARN [17796] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P00B3] Frame set is missing depth frame. 10
2025-03-07 15:53:09.373 WARN [17796] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P00B3] Frame set is missing depth frame. 11
2025-03-07 15:53:09.373 WARN [17796] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P00B3] Frame set is missing depth frame. 12
2025-03-07 15:53:09.375 WARN [25340] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P009W] Frame set is missing depth frame. 8
2025-03-07 15:53:09.375 WARN [24728] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] Frame set is missing depth frame. 14
2025-03-07 15:53:09.375 WARN [25340] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P009W] Frame set is missing depth frame. 9
2025-03-07 15:53:09.378 WARN [26224] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A842011T] Frame set is missing depth frame. 7
2025-03-07 15:53:09.378 WARN [26224] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A842011T] Frame set is missing depth frame. 8
2025-03-07 15:53:09.386 WARN [17796] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P00B3] Frame set is missing depth frame. 13
2025-03-07 15:53:09.397 WARN [26224] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A842011T] Frame set is missing depth frame. 9
2025-03-07 15:53:09.397 WARN [26224] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A842011T] Frame set is missing depth frame. 10
2025-03-07 15:53:18.375 INFO [30288] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:53:18.375362][warning][30288][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [14 logs in 19984ms, last: 15:53:09.312830]

2025-03-07 15:53:30.375 INFO [27672] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:53:30.375727][warning][27672][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [16 logs in 34998ms, last: 15:53:09.281958]

2025-03-07 15:53:30.375 INFO [20748] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:53:30.375731][warning][20748][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [18 logs in 35207ms, last: 15:53:09.282945]

2025-03-07 15:53:31.452 INFO [29268] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:53:31.452155][warning][29268][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [10 logs in 24085ms, last: 15:53:09.278448]

2025-03-07 15:53:32.907 INFO [13300] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:53:32.907247][warning][13300][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [5 logs in 24067ms, last: 15:53:09.214877]

2025-03-07 15:53:50.479 INFO [26224] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec Femto Bolt CL8A842011T: [03/07 15:53:50.479684][warning][26224][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66

2025-03-07 15:53:53.254 WARN [24728] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] Frame set is missing depth frame. 15
2025-03-07 15:53:53.254 WARN [24728] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] Frame set is missing depth frame. 16
2025-03-07 15:53:53.254 ERROR [24728] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] Sensor became unresponsive.
2025-03-07 15:53:53.255 ERROR [27380] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8FC310081] [127.797s (127797/1000)] Sensor disconnected.
2025-03-07 15:53:53.259 WARN [17796] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P00B3] Frame set is missing depth frame. 14
2025-03-07 15:53:53.259 WARN [25340] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P009W] Frame set is missing depth frame. 10
2025-03-07 15:53:53.259 WARN [17796] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P00B3] Frame set is missing depth frame. 15
2025-03-07 15:53:53.259 WARN [25340] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P009W] Frame set is missing depth frame. 11
2025-03-07 15:53:53.305 WARN [25340] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P009W] Frame set is missing depth frame. 12
2025-03-07 15:53:53.550 INFO [26224] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec Femto Bolt CL8A842011T: [03/07 15:53:53.550422][warning][26224][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [7 logs in 3070ms]

2025-03-07 15:53:53.687 WARN [17796] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P00B3] Frame set is missing depth frame. 16
2025-03-07 15:53:53.687 ERROR [17796] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P00B3] Sensor became unresponsive.
2025-03-07 15:53:53.688 ERROR [27780] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P00B3] [128.197s (128197/1000)] Sensor disconnected.
2025-03-07 15:53:53.695 WARN [26224] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A842011T] Frame set is missing depth frame. 11
2025-03-07 15:53:53.697 WARN [25340] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P009W] Frame set is missing depth frame. 13
2025-03-07 15:53:53.711 WARN [26224] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A842011T] Frame set is missing depth frame. 12
2025-03-07 15:53:53.713 WARN [25340] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P009W] Frame set is missing depth frame. 14
2025-03-07 15:53:53.724 WARN [26224] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8A842011T] Frame set is missing depth frame. 13
2025-03-07 15:53:53.725 WARN [25340] [Depthkit::DepthSensorStage::onSensorEvent@378] [Orbbec Femto Bolt CL8S93P009W] Frame set is missing depth frame. 15
2025-03-07 15:53:55.300 INFO [12824] [Depthkit::IO::DepthSensor::DepthSensorKFW2::getConnectedDevices@388] Kinect for Windows version 2 DLL via SDK/Runtime not detected. If you intend to capture with the Kinect V2, install the Kinect for Windows Runtime 2.0 from Microsoft. If you are capturing with the Azure Kinect or Orbbec camera, this message can be ignored.
2025-03-07 15:53:55.420 INFO [12824] [Depthkit::IO::DepthSensor::DepthSensorKFW2::getConnectedDevices@388] Kinect for Windows version 2 DLL via SDK/Runtime not detected. If you intend to capture with the Kinect V2, install the Kinect for Windows Runtime 2.0 from Microsoft. If you are capturing with the Azure Kinect or Orbbec camera, this message can be ignored.
2025-03-07 15:53:59.007 INFO [26348] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:53:59.007211][warning][26348][ObException.cpp:5] Resource busy! You can try again later!

2025-03-07 15:53:59.007 INFO [26348] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:53:59.007425][warning][26348][FemtoBoltUvcDevice.cpp:384] Execute failure! A libobsensor_exception has occurred!
- where:384#libobsensor::FemtoBoltUvcDevice::initDepthProcessParam::<lambda_1d0ea5edbaa213cd81a8ccf5fe619a93>::operator ()
- msg:Resource busy! You can try again later!
- type:class libobsensor::wrong_api_call_sequence_exception

2025-03-07 15:53:59.007 INFO [26348] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:53:59.007533][warning][26348][FemtoBoltUvcDevice.cpp:384] Get temperature failed.

2025-03-07 15:53:59.986 INFO [21608] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:53:59.986827][warning][21608][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [3 logs in 6436ms, last: 15:53:54.257331]

2025-03-07 15:54:32.363 INFO [30268] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:54:32.363645][warning][30268][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [11 logs in 61987ms, last: 15:53:53.551919]

2025-03-07 15:54:33.364 INFO [20548] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:54:33.364668][warning][20548][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [6 logs in 60457ms, last: 15:53:53.156836]

2025-03-07 15:54:39.146 INFO [23156] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:54:39.146370][warning][23156][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [10 logs in 68770ms, last: 15:53:54.223254]

2025-03-07 15:54:39.151 INFO [30068] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/07 15:54:39.151521][warning][30068][Pipeline.cpp:327] Wait for frame timeout, you can try to increase the wait time! current timeout=66 [9 logs in 67699ms, last: 15:53:54.226762]

2

@ChengYunLiu - Sorry to hear you’re experiencing this issue. To help narrow down the cause, please share some more information about your livestream configuration:

  • Quantity of sensors connected to Depthkit - From the log you shared, it appears you are using 5 sensors, but let us know if there are more than that.
  • Color and Depth resolution of each sensor - The settings of each sensor as they appear in the SENSOR CONFIGURATION pane.
  • Allocated memory - How much RAM have you allocated in Preferences > Memory Usage?
  • Livestream resolution - What are the values set in Preferences > Live Output Maximum Resolution?
  • Hardware specifications of your Depthkit capture PC - Including:
  • CPU model
  • GPU model
  • RAM speed, total capacity, and configuration
  • the model of any USB expansion cards if applicable.
  • Livestream signal path - Is the Depthkit Livestream being rendered in Unity on the same computer (i.e. Local Livestreaming, or are you relaying it to another device via LAN, WebRTC, or CDN? Please provide details about the other software/processes running on the Depthkit capture computer.
  • Computer performance metrics - While the livestream is running, what usage percentages are reported in Windows Task Manager for CPU, GPU, and Memory?
3

@CoryAllen - Thanks for reaching out. Here’s the requested information regarding my livestream setup:

  • Quantity of sensors: I am using 5 sensors.
  • Color and Depth resolution: Color:1080p / Depth: 640x576 Narrow raw
  • Allocated memory: 4GB
  • Livestream resolution: 4096px * 4096px
  • Hardware specifications:
    • CPU: 13th Gen Intel(R) Core™i9-13900k
    • GPU: NVIDIA GeForce RTX 4090
    • RAM: 64GB
    • USB expansion card (if applicable): None
  • Livestream signal path: Local Livestreaming in Unity
  • Computer performance metrics: While the livestream is running, the reported usage in Windows Task Manager is:
    • CPU: 60~70%
    • GPU: 40~50%
    • Memory: 10GB (16%)

Please let me know if you need any further details.

Best,
ChengYunLiu

4

Thanks for this information - The only potential issue I can identify from what you have shared is that if there are no USB expansion cards in your computer that are likely plugging all 5 sensors all into the motherboard - Is this correct? If this is the case, multiple sensors might be plugged into ports which share a common USB host controller, you may see stutters in the Depthkit stream as data is bottlenecked there. We have guidance for keeping each sensor on separate USB host controllers in our documentation. Please reconfigure the sensors to ensure that there is sufficient bandwidth in each USB host controller.

Otherwise, is there any other information that can help us narrow this down? Are you able to capture successfully, and is there any revealing behavior in the log or backlog/dropped frame diagnostics while trying to capture?

Can you share a more detailed description (or better yet - screen recording) of the crash? Is the Depthkit app crashing/closing? If not, are the sensors freezing, and do they resume streaming automatically after some time?

Are you seeing the same issue if you reduce the number of connected sensors to 2? Are you seeing the same issue when the color resolution of all cameras is set to a lower resolution like 720p?

If any of the above lead you to configuration which eliminates the issue, please share the difference between your current configuration and the configuration that works, and we’ll investigate from there.

5

You’re right, we do have no USB expansion cards.
Do I have to install a USB expansion card for it to function properly?

I tested different configurations by removing individual cameras and using only four sensors, but the issue persisted. Even when reducing to three sensors, the disconnection frequency decreased but still occurred.

I also noticed that the problem only happens when using Unity LiveStreaming—Depthkit alone does not cause any interruptions.

Ultimately, I found that lowering the voxel count in Unity’s Mesh Source to a certain level prevents the disconnections, but this significantly reduces visual quality.

Do you have any recommendations for maintaining stability while preserving better image quality?

6

@ChengYunLiu

Ultimately, I found that lowering the voxel count in Unity’s Mesh Source to a certain level prevents the disconnections, but this significantly reduces visual quality.

Do you have any recommendations for maintaining stability while preserving better image quality?

This leads me to believe that some other part of your system is struggling to receive and encode the sensor data in Depthkit and simultaneously reconstruct and render the Depthkit asset and the rest of the scene in Unity. This kind of performance constrain led us to develop the Livestreaming over Local Area Network (LAN) workflow, which offloads the work of reconstructing the Depthkit asset and rendering the scene Unity to a different computer. With Depthkit and Unity running on separate dedicated computers, there is more performance overhead available to, for example, increase the mesh density of the Depthkit asset to achieve higher quality.

Do I have to install a USB expansion card for it to function properly?

Not necessarily - some motherboards contain enough USB host controllers to support multiple sensors, but installing a card like the recommended StarTech model will guarantee that each sensor connected to it has a compatible controller and sufficient bandwidth.

7

After installing the PTU314C expansion card, I observed that while other USB devices function correctly when connected to the expansion card, the Orbbec Femto Bolt camera does not operate as expected. Specifically, when attempting to use the Depthkit console, the following error messages are displayed:

2025-03-20 16:30:11.275 ERROR [19216] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/20 16:30:11.275516][error][19216][WinHelpers.cpp:522] CreateFile failed

2025-03-20 16:30:11.275 ERROR [19216] [Depthkit::IO::DepthSensor::DepthSensorOrbbec::sdkLogCallback@637] Orbbec SDK: [03/20 16:30:11.275673][error][19216][WinHelpers.cpp:557] could not find camera in windows device tree

Additionally, attempts to detect the camera using the Orbbec Viewer have been unsuccessful.
Steps Taken:

  • Connected the Orbbec Femto Bolt directly to the computer’s USB 3.0 port, bypassing the expansion card.
  • Ensured that the expansion card’s SATA power connector is properly connected.

Given the troubleshooting steps already undertaken, I kindly request your guidance on the following:

  • Compatibility Verification: Could you confirm whether the PTU314C PCI-E USB3.0 expansion card is officially supported for use with the Orbbec Femto Bolt camera?
  • Alternative Solutions: If the expansion card is not compatible, are there recommended alternatives or specific USB 3.0 expansion cards known to work reliably with the Orbbec Femto Bolt?
  • Additional Troubleshooting: Are there further diagnostic steps or settings adjustments that you would recommend to resolve this issue?
8

@ChengYunLiu - It seems like the PCIe card you added has introduced a new issue so I would revert the computer configuration to how you had it when it was working. If Depthkit fully functions when Unity is either not running, or has the volume density reduced, then I anticipate that the the Livestreaming over Local Area Network (LAN) workflow will be a more effective solution than changing the connection of the sensors to the computer.

9

Hi @CoryAllen,
I appreciate your response, but I don’t think reverting my setup is a viable solution. The issue persists specifically when connecting the Orbbec Femto Bolt to the PCIe USB expansion card, while other USB devices (such as a mouse) work fine on the same card.

Could you clarify the following points?

  1. Does Orbbec Femto Bolt have known compatibility issues with PCIe USB expansion cards?
  2. Are there any specific requirements for USB controllers or drivers that might be causing this issue?
  3. The error message in the Orbbec SDK logs suggests a failure in device recognition. Is there a way to manually force device detection or troubleshoot this further?

Reverting my setup is not ideal since I need the additional USB ports. I’d appreciate a more technical explanation or workaround for making the camera work with the expansion card.

10

@ChengYunLiu - Apologies for the confusion. I believe there are multiple issues present in this thread, so my recommendation to revert your configuration was meant only to isolate and confirm the nature of each issue.

The errors from your first post combined with the apparent solution of lowering the volume density of the Depthkit object rendering in a Unity scene on the same computer suggest that this specific issue is caused by resource contention between Depthkit and Unity running on the same computer, hence the recommendation to try the LAN Livestreaming workflow.

The could not find camera in windows device tree error you later posted appears to be a separate issue relating to the connection of the Femto Bolt to the computer. Bypassing the PTU314C is intended to confirm that this PCIe card or the USB host controllers contained within it are the source of the connection issue.

I hope this helps clarify. Per your questions:

  1. Does Orbbec Femto Bolt have known compatibility issues with PCIe USB expansion cards?

The Femto Bolt does not have issues with PCIe USB cards in general. As we have tested and verified, the Bolt is fully compatible with the StarTech PEXUSB3S44V. I am having trouble finding/translating specific information about the PTU314C card you mentioned, so I cannot confirm that that specific model of PCIe USB card has specs and USB controllers which are compatible with the Femto Bolt.

  1. Are there any specific requirements for USB controllers or drivers that might be causing this issue?

Per our testing, the best practices listed in the Depthkit Studio hardware requirements documentation are to ensure each sensor uses a dedicated USB host controller, and that the controller is either Intel, Renesas, or Texas Instruments (TI) - not ASMedia controllers - and that Renesas controllers use the default Windows-provided Intel driver rather than an older Renesas driver. This guidance comes from Microsoft’s specifications for the Azure Kinect upon which the Femto Bolt is based, however Orbbec’s documentation for Femto Bolts is not as specific. I have posted on a thread in the Orbbec forums to confirm the accuracy of this information as it applies to Femto Bolt sensors.

  1. The error message in the Orbbec SDK logs suggests a failure in device recognition. Is there a way to manually force device detection or troubleshoot this further?

As I understand it, this is likely a hardware incompatibility between the Femto Bolt and the PTU314C card you are using, so I don’t believe there is any way to force the connection.

11

Product Specification

■ Supports PCI Express 2.0 standard
■ PCI Express transfer speed up to 5Gbps
■ USB 3.0 specification version 1.0, compatible with USB 3.1 / 2.0 / 1.1 devices
■ Expansion: 4 x USB 3.0 Type-A ports / 1 x USB 3.0 Type-C port
■ Supports front panel 19-pin expansion for 2 additional USB ports
■ Supports USB transfer speeds of 1.5Mbps / 12Mbps / 480Mbps / 5Gbps
■ Compliant with Intel xHCI Revision 1.0 standard
■ Each USB port provides +5V / 900mA maximum output for external USB devices
■ Built-in SATA power connector
■ Hot-swappable USB ports without requiring system restart
■ Interface: PCI Express 2.0 / USB 3.0 (compatible with USB 3.1 / 2.0 / 1.1)
■ Number of USB ports: 4 x USB 3.0 Type-A / 1 x USB 3.0 Type-C, supports front panel 19-pin expansion for 2 additional USB ports
■ Supported operating systems: Windows XP / Vista / 7 / 8 / 8.1 / 10 / 11 (32-bit / 64-bit)
■ Power supply: Built-in SATA power connector (must be connected for stable power supply)

Additionally, we would like to confirm whether this card is compatible with the Femto Bolt camera. Please let us know if this setup meets the requirements.

12

@ChengYunLiu - The specifications you have shared don’t point to any specific incompatibility, but there might still exist some unlisted incompatibility between this PCIe card and the Femto Bolt sensors - For example, the model of USB host controller present within the card may be unsupported by the Femto Bolt. Unfortunately, further testing of the PTU314C is outside the scope of support for Depthkit. I recommend contacting Orbbec support to see if they can provide any insight into compatibility between their product and the PTU314C, or provide any solutions to get that combination of components to work.

Once you are able to resolve this connection issue with Orbbec, or you are able to remove the PTU314C and replace it with a StarTech PEXUSB3S44V which has been confirmed to be compatible, I am happy to resume troubleshooting any remaining issues you are experiencing with the Depthkit application and/or Depthkit Expansion Packages for Unity.