Unable to utilize GPU on GTX1060 6gb laptop

[Zi Yong Chua]

I am connected to my xbox sensor with my Win10 laptop, on the latest 1.9.1 Skanect. However, when I tried to process the files, it shows that CPU is 100% while my GPU usage on my 1060 is not being used >3-4%. I checked the logs and I see the following. Is there something wrong in my configuration?

WARNING: Can't determine number of cores. Unknown SM version 6.1!

[Zi Yong Chua]

INFO: Starting Skanect 1.9.1 (64 bits)
INFO: Configuration file: C:/Users/chuaz/AppData/Roaming/ManCTL/Skanect.ini
INFO: License configuration file: C:/Users/chuaz/AppData/Roaming/ManCTL/SkanectLicense.ini
INFO: Number of CUDA devices: 1
INFO: Device 0:  "GeForce GTX 1060"  5085Mb / 6144Mb

WARNING: Can't determine number of cores. Unknown SM version 6.1!

INFO: Device 0: sm_61, 0 cores
INFO: Device 0: Driver/Runtime ver.10.0/8.0
INFO: CUDA major: 6
INFO: CUDA GeForce GTX 1060, global memory: 6144M
INFO: CUDA device specs seem ok.
INFO: Could instanciate a GPU fusion successfully.
INFO: License type: PRO

WARNING: Can't determine number of cores. Unknown SM version 6.1!

INFO: No support for Kinect One SDK.
INFO: Initializing Kin4Win driver

INFO: Number of Kinect for Windows devices found: 1.
INFO: OpenNI2: Number of devices: 0
INFO: No support for softkinetic, skipping.
INFO: [Kinect ece6b100] connecting

INFO: Kinect for Windows: initialized successfully

INFO: Kinect for Windows: color stream opened.

INFO: Kinect for Windows: depth stream opened.

WARNING: Kinect for Windows: could not set near mode

WARNING: Kinect for Windows: must be an Xbox Kinect.

INFO: Kinect for Windows: flags set.

INFO: Image processing framerate: 29.910269
INFO: Live reconstruction framerate: 19.249279
INFO: Image processing framerate: 29.940121
INFO: Live reconstruction framerate: 18.500486
INFO: Write on disk frame rate: 15.938087
INFO: Image processing framerate: 29.880478
INFO: Live reconstruction framerate: 15.137180
ERROR: Number of images not written to disk because of overload: 5
INFO: Image processing framerate: 29.980658
INFO: Live reconstruction framerate: 14.985015
INFO: Image processing framerate: 29.880478
INFO: Live reconstruction framerate: 14.534883
INFO: Write on disk frame rate: 13.521672
ERROR: Number of images not written to disk because of overload: 7
INFO: Image processing framerate: 30.009680
INFO: Live reconstruction framerate: 15.194682
ERROR: Number of images not written to disk because of overload: 9
ERROR: Number of images not written to disk because of overload: 11
INFO: Write on disk frame rate: 20.225506
INFO: Image processing framerate: 30.038759
INFO: Live reconstruction framerate: 18.867924
ERROR: Number of images not written to disk because of overload: 28
ERROR: Number of images not written to disk because of overload: 31
ERROR: Number of images not written to disk because of overload: 38
INFO: Image processing framerate: 30.155642
INFO: Live reconstruction framerate: 19.493177
ERROR: Number of images not written to disk because of overload: 52
ERROR: Number of images not written to disk because of overload: 66
INFO: Image processing framerate: 30.009680
INFO: Live reconstruction framerate: 18.719212
ERROR: Number of images not written to disk because of overload: 74
ERROR: Number of images not written to disk because of overload: 87
INFO: Image processing framerate: 29.922779
INFO: Live reconstruction framerate: 15.223597
ERROR: Number of images not written to disk because of overload: 106
INFO: Write on disk frame rate: 5.132350
ERROR: Number of images not written to disk because of overload: 113
INFO: Image processing framerate: 29.910269
INFO: Live reconstruction framerate: 14.985015
ERROR: Number of images not written to disk because of overload: 115
ERROR: Number of images not written to disk because of overload: 119
ERROR: Number of images not written to disk because of overload: 127
INFO: Image processing framerate: 30.067896
INFO: Live reconstruction framerate: 15.399423
ERROR: Number of images not written to disk because of overload: 129
ERROR: Number of images not written to disk because of overload: 134
ERROR: Number of images not written to disk because of overload: 145
INFO: Image processing framerate: 30.038759
INFO: Live reconstruction framerate: 16.377649
ERROR: Number of images not written to disk because of overload: 155
INFO: Write on disk frame rate: 9.614216
ERROR: Number of images not written to disk because of overload: 167
INFO: Image processing framerate: 29.910269
INFO: Live reconstruction framerate: 19.417477
ERROR: Number of images not written to disk because of overload: 187
ERROR: Number of images not written to disk because of overload: 198
INFO: Image processing framerate: 30.214424
INFO: Live reconstruction framerate: 19.065777
ERROR: Number of images not written to disk because of overload: 213
INFO: Image processing framerate: 30.009680
INFO: Live reconstruction framerate: 15.488868
ERROR: Number of images not written to disk because of overload: 225

On Sunday, December 9, 2018 at 1:33:08 PM UTC+8, Zi Yong Chua wrote:

[Simon Fiastre]

Hello,

I have similar problem on a Lenovo Legion Y720 equiped with a 6GB GTX 1060, intel i7 and 8GB DDR4 RAM.

Skanect 1.9.1 app systematicaly closes itself when processing Fusion Reconstruction.

System and graphic drivers are up to date.

LOG here :

INFO: Starting Skanect 1.9.1 (64 bits)

INFO: Configuration file: C:/Users/Lenovo/AppData/Roaming/ManCTL/Skanect.ini
INFO: License configuration file: C:/Users/Lenovo/AppData/Roaming/ManCTL/SkanectLicense.ini

INFO: Number of CUDA devices: 1
INFO: Device 0:  "GeForce GTX 1060"  5085Mb / 6144Mb
WARNING: Can't determine number of cores. Unknown SM version 6.1!
INFO: Device 0: sm_61, 0 cores
INFO: Device 0: Driver/Runtime ver.10.0/8.0
INFO: CUDA major: 6
INFO: CUDA GeForce GTX 1060, global memory: 6144M
INFO: CUDA device specs seem ok.
INFO: Could instanciate a GPU fusion successfully.
INFO: License type: PRO
WARNING: Can't determine number of cores. Unknown SM version 6.1!
INFO: No support for Kinect One SDK.

WARNING: No Kinect for Windows SDK dll found.

INFO: OpenNI2: Number of devices: 0
INFO: No support for softkinetic, skipping.

INFO: Depth Intrinsics: fx/fy/cx/cy [0.000 | 0.000 | 0.000 | 0.000]
INFO: Color Intrinsics: fx/fy/cx/cy [0.000 | 0.000 | 0.000 | 0.000]

[scott...@occipital.com]

Hello,

The 100% CPU utilization issue is believed to be caused by an older USB device driver for Primesense sensors (including the Kinect for Xbox 360 sensor) under Windows 10 and, unfortunately, no updated drivers (for Windows 10) are available. This should not affect the quality of your scans but it can affect performance so I recommend disconnecting the sensor once the capture is complete.

The "WARNING: Can't determine number of cores. Unknown SM version 6.1!" message is a known but harmless warning that you can safely ignore. The next update of Skanect.is expected to resolve this.

-Scott

[scott...@occipital.com]

Hello,

The message "WARNING: No Kinect for Windows SDK dll found." suggests that you need to install the appropriate version of the Kinect for Windows SDK.

For Windows 7, I recommend version 1.7 which you can download from here: https://www.microsoft.com/en-us/download/details.aspx?id=36996

For Windows 10, I recommend version 1.8 which you can download from here: https://www.microsoft.com/en-us/download/details.aspx?id=40278

-Sctt