Quote Originally Posted by pochrist View Post
This is shot in the dark as I have not had to deal with USB / Com port resources issues for a while (until I got my 3D printer in December). I have no experience with Kinect or the software your trying to use. But way back when 20+ years ago during system builds it was wise to check which Slot on the main board you plug into, does this USB Card use PCI or PCIe slots? Many times the bus paths on the main board will cover multiple ports and slots and if you where to plug into a slot that also shares your Video Bus (for example) you could end up with a conflict or problem when both devices on the same bus are in use. It could explain why the verification software will Pass, but when you go to use it it has a fault (it may be choking when it needs to get exclusive access to the resources on the bus). Just for the hell of it you could try the Main board USB ports (if their are any USB 3.0 ports on it) sure can't hurt, if you get something other then a gray screen it could shed some light on the problem. If you have the manual for the main board it will tell you what ports and slots share the same buses.
The motherboard has a single PCIe slot, which I am using for the USB 3.0 card. The built-in USB 3.0 ports actually give the same response as the card: the Verifier tool is able to recognize the port as being supported but having unknown bandwidth, and then it is able to actually receive 3d video data at 30 FPS. Meanwhile, 3D Scan gives a gray screen for both.
If my motherboard just can't handle it, that's too bad, but the Kinect isn't even turning on when 3D Scan runs. Maybe 3D Scan gets to the stage of unknown bandwidth and just gives up.