New to the forums? Click here to read the "How To" Guide.

Developer? Click here to go to the Developer Forums.

DK2 tracker issues Win 10 GTX970

naplandgamesnaplandgames Posts: 6
NerveGear
edited March 2016 in Support
I am trying hard to get this Oculus to work and failing.
I finally have the display working, but the tracker does not work properly.
I have Windows 10 64-bit,
AMD Phenom II x6 1090T (yes, apparently this doesn't meet min requirements, but I've seen folks using it).
EVGA GeForce GTX 970.
2 monitors connected via DVI
DK2 is connected on the HDMI.
Rift runtime 0.8.0.0
I do use Logitech products - wireless mouse, keyboard, and headset. Unfortunately I don't have any wired keyboard or mouse to try out, but I have tried with the mouse plugged in and headset disconnected.

Rift and Tracker are plugged in to USB 3.0 ports.
If I run the config util with debugging off it says everything is fine, though I usually have to reconnect the USB on the tracker to get a blue light to show on it.
I can run the demo scene and view it in the headset, but the tracking does not work and I cannot look around.

If I place the config utility into debugging for DK2, it reports that the tracker sync cable is not attached. The blue light is off, and reconnecting does not get it back on. I cannot run the demo scene and the headset's light is off. The Rift DK2 Sensor appears in USB Device Tree Viewer as connected to my 3.0 host controller. It shows as an H connection, though, instead of an S. I assume the DK2 is actually running via USB 2.0. I do see that enabling debug actually disconnects the hardware and makes things not work. So I guess the info on that screen is meaningless.

What I've tried:
    Multiple USB ports - config not in debug mode, USB 2.0 or 3.0 ports don't change anything. Front connectors report unable to get bandwidth. Connecting the tracker directly to the headset. Absolutely nothing. I do not have a power adapter so, I imagine the headset can't power both devices without it. Different USB cables for the tracker - same result. Older versions of the runtime - no go... that was scary and supplied lots of excitement with driver crashes and flashing monitors. Multiple suggestions from these threads that just seem to be luck.

Not sure what I can do from this point out.

Logs are attached.
Thanks

Comments

  • cyberealitycybereality Posts: 26,156 Oculus Staff
    Can you provide these log files:

    viewtopic.php?f=34&t=23521
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i
    Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
  • naplandgamesnaplandgames Posts: 6
    NerveGear
    Yup, thought they were all attached, but I see only the first two now...
    Here's the two logs from the rift (server and prefs).
  • cyberealitycybereality Posts: 26,156 Oculus Staff
    So it's failing to get a response from the camera. It is detected, which likely means the USB cable is working. I would guess the camera is defective. However it's strange that the headset sensor is also failing. Even if the camera is unplugged, you would still get orientation tracking. Something is very strange.

    Maybe the tracking driver didn't install. Can you try running this?

    C:\Users\You\AppData\Local\Temp\Oculus Inc\OculusPTDriver_Win8_x64.msi
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i
    Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
  • naplandgamesnaplandgames Posts: 6
    NerveGear
    I was not permitted by to install OculusPTDriver_Win8_x64.msi, but I was able to install the Win8.1 version. I now have head tracking, but positional isn't working. In the Oculus World demo I can see the tracking acquired / lost message every time I move my head (not rotate). There's also a semi-frequent jitter/jump around the time this happens. It's as if positional tracking starts, but then immediately stops.
    I'm going to talk to my client (who owns the device - I have it in my possession) and see if he ever had positional tracking working. If not I'm betting there is also an issue with the camera. However, I'd like to try a different "sync" cable and any other possible software fixes before trying to replace the tracker (if we can even do so). Now if I can just find a 2.5mm audio cable!

    Thanks for the help. Further suggestions are quite welcome.

    EDIT: I was mistaken. Positional tracking does seem to work in the Oculus World demo. I do get the warning frequently (tracking acquired/lost), but I can actually move around. Would be nice if I could solve that.
  • cyberealitycybereality Posts: 26,156 Oculus Staff
    Yeah, that could certainly be a cabling issue. Or maybe one of the ports are damaged.

    Here are all the cables you need if you want to replace them.

    http://www.amazon.com/Cable-Matters%C2% ... B00HNF0OS8
    http://www.amazon.com/Your-Cable-Store- ... 000Z0YECU/
    http://www.amazon.com/Monoprice-18Gbps- ... 00H7N4Z1I/
    http://www.amazon.com/Steren-feet-2-5mm ... B00291F4RM
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i
    Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
  • PalmerEldritchPalmerEldritch Posts: 1
    NerveGear
    After no problems for many weeks, my DK2 Tracker Camera stopped working and started giving me a brand new error:

    "Tracker can not get USB bandwidth"

    Besides the poor grammar within the error, it's odd. I cannot find anything online even referencing this error message. The USB cables are all plugged into USB 3.0 ports and nothing in my configuration had changed. The headset is detected and can display images just fine, only just without head depth tracking. I've uninstalled / reinstalled the runtime and drivers, including the ones within %TEMP%/Oculus Inc. Anyone have any thoughts or a similar experience? Thanks in advance. My Diagnostics log is below.


    {
    "Time": "2016-03-20_21:14:55",
    "SDK Version": "0.8.0.0",
    "Local SDK Version": "0.8.0.0",
    "Service Running Time": {
    "Hours": 0,
    "Minutes": 3,
    "Seconds": 54
    },
    "Display Status": {
    "Display Mode": 2,
    "Win10 Native": {
    "Capable": 1,
    "Available": 1,
    "ResultCode": 0,
    "Status": "DXGI 2 Preview available"
    },
    "IHVDirect": {
    "Capable": 1,
    "Available": 1,
    "ResultCode": 0,
    "Status": "Direct Display available"
    },
    "Legacy Direct": {
    "Capable": 0,
    "Available": 0,
    "ResultCode": -3005,
    "Status": "OVRDirect not supported on this OS. Please use one of the more supported modes"
    },
    "Summary ResultCode": 0,
    "Summary Status": ""
    },
    "System Specifications": {
    "Operating System": "Microsoft Windows 10 Pro",
    "Processor": "Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz",
    "Graphics Adapters": [{
    "Name": "NVIDIA GeForce GTX 980 Ti",
    "Video Controller RAM (MB)": 4095,
    "Driver Version": "10.18.13.6451",
    "Video Mode": "1920 x 1080 x 4294967296 colors"
    }],
    "Total RAM (GB)": 32,
    "USB Tree": [{
    "name": "Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)",
    "deviceid": "PCI\\VEN_8086&DEV_A12F&SUBSYS_06B81028&REV_31\\3&11583659&0&A0",
    "caption": "Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)",
    "manufacturer": "Generic USB xHCI Host Controller",
    "Devices": [{
    "manufacturer": "(Standard USB HUBs)",
    "name": "USB Root Hub (xHCI)"
    }, {
    "manufacturer": "(Standard USB Host Controller)",
    "name": "USB Composite Device"
    }, {
    "manufacturer": "Logitech (x64)",
    "name": "USB Input Device (Logitech Download Assistant)"
    }, {
    "manufacturer": "(Standard keyboards)",
    "name": "HID Keyboard Device"
    }, {
    "manufacturer": "(Standard system devices)",
    "name": "USB Input Device"
    }, {
    "manufacturer": "Microsoft",
    "name": "HID-compliant mouse"
    }, {
    "manufacturer": "Microsoft",
    "name": "HID-compliant consumer control device"
    }, {
    "manufacturer": "(Standard system devices)",
    "name": "HID-compliant system controller"
    }, {
    "manufacturer": "(Standard system devices)",
    "name": "HID-compliant vendor-defined device"
    }, {
    "manufacturer": "(Standard system devices)",
    "name": "USB Input Device"
    }, {
    "manufacturer": "(Standard system devices)",
    "name": "HID-compliant vendor-defined device"
    }, {
    "manufacturer": "(Standard system devices)",
    "name": "HID-compliant vendor-defined device"
    }, {
    "manufacturer": "(Standard system devices)",
    "name": "HID-compliant vendor-defined device"
    }, {
    "manufacturer": "(Standard USB Host Controller)",
    "name": "USB Composite Device"
    }, {
    "manufacturer": "(Standard system devices)",
    "name": "USB Input Device"
    }, {
    "manufacturer": "Microsoft",
    "name": "HID-compliant mouse"
    }, {
    "manufacturer": "(Standard system devices)",
    "name": "USB Input Device"
    }, {
    "manufacturer": "(Standard keyboards)",
    "name": "HID Keyboard Device"
    }, {
    "manufacturer": "Microsoft",
    "name": "HID-compliant consumer control device"
    }, {
    "manufacturer": "(Standard system devices)",
    "name": "HID-compliant system controller"
    }, {
    "manufacturer": "(Standard system devices)",
    "name": "HID-compliant device"
    }, {
    "manufacturer": "(Standard system devices)",
    "name": "HID-compliant device"
    }, {
    "manufacturer": "(Standard system devices)",
    "name": "USB Input Device"
    }, {
    "manufacturer": "(Standard keyboards)",
    "name": "HID Keyboard Device"
    }, {
    "manufacturer": "Broadcom",
    "name": "DW1560 Bluetooth 4.0 LE"
    }, {
    "manufacturer": "Microsoft",
    "name": "Microsoft Bluetooth LE Enumerator"
    }, {
    "manufacturer": "Microsoft",
    "name": "Bluetooth Device (RFCOMM Protocol TDI)"
    }, {
    "manufacturer": "Microsoft",
    "name": "Microsoft Bluetooth Enumerator"
    }, {
    "manufacturer": "Broadcom",
    "name": "Bluetooth Hands-free Audio"
    }, {
    "manufacturer": "Broadcom Corp.",
    "name": "Bluetooth L2CAP Interface"
    }, {
    "manufacturer": "Microsoft",
    "name": "Bluetooth Device (Personal Area Network)"
    }, {
    "manufacturer": "Alcor Micro, Corp.",
    "name": "Alcor Micro USB 2.0 Card Reader"
    }, {
    "manufacturer": "(Standard disk drives)",
    "name": "Generic- Compact Flash"
    }, {
    "manufacturer": "(Standard disk drives)",
    "name": "Generic- SD/MMC"
    }, {
    "manufacturer": "(Standard disk drives)",
    "name": "Generic- MS/MS-PRO"
    }, {
    "manufacturer": "(Standard disk drives)",
    "name": "Generic- xD-Picture"
    }, {
    "manufacturer": "(Standard USB HUBs)",
    "name": "Generic USB Hub"
    }, {
    "manufacturer": "(Standard USB HUBs)",
    "name": "Generic USB Hub"
    }, {
    "manufacturer": "(Standard system devices)",
    "name": "USB Input Device"
    }, {
    "manufacturer": "(Standard system devices)",
    "name": "HID-compliant device"
    }, {
    "manufacturer": "(Standard USB Host Controller)",
    "name": "USB Composite Device"
    }, {
    "manufacturer": "Oculus VR",
    "name": "Rift DK2 Sensor"
    }]
    }]
    },
    "Video Device Tree": [{
    "Name": "NVIDIA GeForce GTX 980 Ti",
    "VRAM (MB)": 6047,
    "Monitors": [{
    "Name": "\\\\.\\DISPLAY1",
    "Width": 1920,
    "Height": 1080,
    "Refresh Rate": 60
    }]
    }, {
    "Name": "Microsoft Basic Render Driver",
    "VRAM (MB)": 0,
    "Monitors": []
    }],
    "Devices": [{
    "Product ID": 33,
    "Product Name": "Oculus Rift DK2",
    "Manufacturer": "Oculus VR",
    "Serial Number": "209F01030QAN",
    "Vendor ID": 10291,
    "EDID Serial": "H1DEM8R6N1E23",
    "Firmware": {
    "Major": 2,
    "Minor": 12
    },
    "Frustum": {
    "Far Z Metres": 2.500000,
    "H Fov Radians": 1.291544,
    "Near Z Metres": 0.400000,
    "V Fov Radians": 0.942478
    },
    "Tracking Error": "Tracker can not get USB bandwidth"
    }, {
    "HMDNRFVersion": "",
    "TrackerNRFVersion": ""
    }],
    "Profile": {
    "Player Name": "Kevin01",
    "IPD": 0.064000,
    "Eye height": 1.675000,
    "Eye Cup": "A",
    "Eye Relief": 3,
    "Gender": "Unknown",
    "Eye To Neck": 0.075000,
    "Player Height": 1.778000,
    "Camera Centered From World": {
    "Camera Centered From World": {
    "x": 0,
    "y": -0.670773,
    "z": 0,
    "w": 0.741663
    },
    "Rotation": {
    "x": 0.139568,
    "y": -0.024100,
    "z": -0.000984
    }
    }
    }
    }
  • rdkirkdenrdkirkden Posts: 1
    NerveGear

    I’ve had similar problems with my Oculus Rift DK2 tracker and found a solution that I’d like to share, since there seems to be very little advice about this on the internet. It boiled down to a problem with the USB ports.

     

    My hardware set-up is:

    Windows 7, 64-bit

    Intel Xeon E5520 (4 cores, 8 threads, 2.26 GHz) – below minimum spec, I think

    NVIDIA GTX970 – just meets minimum spec

    Oculus SDK 0.5.0.1 (also got it working with SDK 0.8.0.0)

     

    To begin with, I had only USB 2.0 ports on my PC. The HMD device was working fine, but the tracker was not working at all. The Oculus Configuration Utility failed to detect it: ‘Oculus Rift DK2 Attached; No Tracker Attached’. The blue tracker LED was off.

     

    I fitted a USB 3.0 card (with 2 ports) into a spare PCIe slot and plugged both the tracker and the HMD into it. This made no difference: the tracker was still not working and the Oculus Configuration Utility still said ‘Oculus Rift DK2 Attached; No Tracker Attached’. I did notice, though, that the tracker was being recognised by Device Manager. It was listed under ‘Oculus VR Devices’ > ‘Oculus Video Camera’, was reported to be working and had the correct driver installed. The HMD was listed separately as an HID device.

     

    At this point, I decided to try updating to Oculus SDK 0.8.0.0, which includes newer drivers for the tracker and the HMD. This didn’t solve the problem, but it did give me some useful error messages which enabled me to find a solution. The error messages I got were the same as the ones reported by earlier posts in this thread. The Oculus Configuration Utility periodically alternated, apparently at random, between two sets of error messages:

     

    1) Oculus Configuration Utility alternates between ‘Oculus Ridt DK2 Attached; No Tracker Attached’ and ‘Oculus Rift DK2: Ready’. Also, there is a warning message saying ‘! Tracker can not get USB bandwidth’. The blue tracker LED flashes on and off.

    2) Oculus Configuration Utility reports ‘Oculus Rift DK2: Ready’. But there is also a warning message saying ‘! Tracker synch cable disconnected’. The blue tracker LED is on continuously.

     

    The bandwidth error message suggested that the tracker was not getting a sufficient data rate through the USB 3.0 port. Some PCIe slots share their bandwidth with other slots on the motherboard, so I tried fitting a second USB 3.0 card (which I happened to have) to another free PCIe slot.

     

    This almost worked. Now the Oculus Configuration Utility continuously reported ‘Oculus Rift DK2: Ready’, the blue LED was on continuously, and there were no warning messages most of the time. However, a new warning occasionally appeared: ‘! Tracker truncated a higher than acceptable number of frames in the last time period (expected <= 1, got 2)’. Also, when viewing the demo program, the image being viewed would occasionally jump to a new position.

     

    This warning about frames being dropped suggested that there was still a problem with the data rate. This was because the tracker and HMD were plugged into ports on the same USB 3.0 card and were sharing bandwidth. The problem was solved by plugging the HMD into a port elsewhere (either on the other USB 3.0 card or one of my USB 2.0 ports – it didn’t matter which), so that the tracker no longer had to share bandwidth. Finally, the tracker worked with no error messages.

     

    Having got the tracker working, I rolled back to Oculus SDK 0.5.0.1 and found that the tracker worked just as well with this Oculus SDK version. So the problem had to do entirely with the USB ports.

     

    I’ve seen another post that advised connecting the Oculus DK2 hardware to USB ports attached directly to the motherboard, avoiding USB hubs and extensions (https://www.reddit.com/r/oculus/comments/2fl2yj/usb_20_or_30/). I think this is good general advice to ensure an adequate data rate; but as my experience shows, it is sometimes possible to get enough bandwidth from a USB card as long as it is plugged into the right PCIe slot.
Sign In or Register to comment.