From ddc3828f21a60fc49d23d9c70088bc74efdc4ba5 Mon Sep 17 00:00:00 2001 From: Marek Date: Fri, 12 May 2017 09:57:03 +0200 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e96d64f..752a2ae 100644 --- a/README.md +++ b/README.md @@ -15,7 +15,7 @@ At the moment connecting multiple Kinect v2 devices to a single computer is diff Because of those limitations, in our system each Kinect v2 sensor is connected to a separate computer. Each of those computers is connected to a server which governs all of the sensors. The server allows the user to perform calibration, filtering, synchronized frame capture, and to visualize the acquired point cloud live. ## How to use it ## -To start working with our software you will need a Windows machine with the Kinect for Windows SDK 2.0, and at least a single Kinect v2 device. You can either build LiveScan3D from source which is easiest using Visual Studio, or you can download the binary release. +To start working with our software you will need a Windows machine with the Kinect for Windows SDK 2.0, and at least a single Kinect v2 device. You can either build LiveScan3D from source which, or you can download the binary release. The current version has to be compiled using Visual Studio 2015 for compatibility with the OpenCV dll versions that are included. Both the binary and source distributions contain a manual (in the docs directory) which contains the steps necessary to start working with our software (it won't take more than a couple of minutes to set up).