Results 1 to 10 of 16
-
01-01-2017, 11:22 AM #1
- Join Date
- Aug 2015
- Posts
- 15
Gray Screen in Microsoft's 3D Scan app
I set up a machine that meets Microsoft's requirements (including using an approved USB 3.0 card instead of the USB 3.0 ports built into my motherboard), but when I try to use the 3D Scan app, all I get is a gray box where I should see the input from the Kinect camera. I've installed the Kinect Configuration Verifier tool, and I can see both the color and the depth images using that tool. But with 3D Scan, the Kinect doesn't turn on and I see nothing. Google searches turned up only a suggestion to stop and restart the Kinect Monitor service, but that didn't help me. Any other ideas?
-
01-01-2017, 04:21 PM #2
- Join Date
- Jan 2014
- Location
- Oakland, CA
- Posts
- 935
Do you have a Kinnect V2 sensor? This doesn't work with other versions of the Kinnect.
-
01-01-2017, 06:47 PM #3
- Join Date
- Aug 2015
- Posts
- 15
-
01-01-2017, 10:21 PM #4
- Join Date
- Jan 2014
- Location
- Oakland, CA
- Posts
- 935
Maybe it's the USB connection that's at fault, then. Is yours on this list of approved express cards: http://answers.flyppdevportal.com/MV...ry=kinectv2sdk ?
-
01-02-2017, 09:28 AM #5
- Join Date
- Aug 2015
- Posts
- 15
-
01-02-2017, 03:50 PM #6
- Join Date
- Jan 2014
- Location
- Oakland, CA
- Posts
- 935
Bad cables?
-
01-02-2017, 05:59 PM #7
- Join Date
- Aug 2015
- Posts
- 15
I appreciate your interest in brainstorming this with me, but the reason I'm at a loss for an explanation is that I have run the Kinect Configuration Verifier and it reports no issues. The Verifier tool (see https://developer.microsoft.com/en-u...hardware-setup) actually shows me a 30 FPS video feed received from my Kinect, but 3D Scan just gives me a gray screen. If it were a hardware problem, I would expect the Configuration Verifier to also be unable to access the Kinect.
EDIT: Way deep down in the thread regarding compatible USB cards that you posted before, someone posted a response saying that they had tried a Renesas D720202 chipset card and that they were able to use the Kinect for a number of things, but got a grey screen in 3D Scan. That's the same chipset that my SIIG card uses. So let me just ask this: If 3D Scan is working for you personally, what USB 3.0 card are you using?Last edited by dommer2029; 01-02-2017 at 06:11 PM.
-
01-03-2017, 02:50 AM #8
- Join Date
- Jan 2014
- Location
- Oakland, CA
- Posts
- 935
Sorry, I can't say I've got this to work for me, personally. But I'm interested in scanning in general, and this seems like an inexpensive though low-res solution. Isn't there any official tech support offered?
-
01-03-2017, 11:04 AM #9
- Join Date
- Aug 2015
- Posts
- 15
-
01-03-2017, 09:51 PM #10
- Join Date
- Dec 2016
- Posts
- 43
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.
Kickstarter campaing LEGENDARY...
Today, 08:02 AM in Free Self Promotion