Jump to content
 

Search the Community

Showing results for tags 'tracking'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • VIVE
    • Vive Community Forums
    • Developer Forums
    • Vive Technical Support

Blogs

  • Viveport Blog
  • Viveport Reviews
  • Viveport SDKs and Downloads
  • Developer Blog
  • Vive Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 5 results

  1. There has been quite a bit of speculation on the types of cameras used on the Cosmos. Windows Mixed Reality and Oculus headsets reportedly use IR cameras, while the Cosmos uses RGB cameras. IR cameras are known for better low light performance. Many report poor exposure and dynamic range with the Cosmos RGB cameras while using them as a passthrough, which may explain why the headset has so much trouble with lighting conditions. If the root problem is the type of cameras used, then this can't be solved by software fixes, correct? Is there anything the team can say to assuage worries that core problems with Cosmos tracking can be resolved via software fixes, specifically addressing the types of cameras used on the Cosmos?
  2. SDK contains methods to check eyes blinking state: Is there some way to track each eye position separately? For now, the result is "combined": @Corvus
  3. Hi, I try to install the plugin of ViveHandTracking but doesnt work. When started the Engine Unreal 4.20 or 4.22 appear this mesages that could not be compile and try rebuilding from source manually. I try to install in Unreal 4 and use Vive pro. What i can do ?
  4. Hello, I'm having trouble with tracking when I have more than 2 VIVE TRACKERS connected. Tracking becomes very poor, I experience a lot of jitters. It''s actually unusable. I think it has something to do with bluetooth connection quality and I seek any helpful tips how to improve it. Here is what I have already tried: 1. I have no reflective surfaces in the room. I've even had to replace my wardrobes as those had reflective doors :-). My windows are completely covered. 2. I have tried a couple of setups with base stations. I used 2x VIVE Base Stations 2.0, 4x VIVE Base Stations 2.0, 2x VALVE Index Base Stations 2.0 and finally 4x VALVE Index Base Stations 2.0. Multiple positions were tested. The results didn't vary much. After connecting 4 - 5 VIVE Trackers, I get very poor performance on some of them. And of course - it's random - most of the times one or two trackers has tracking issues, sometimes the controllers start to jitter. 3. I've noticed that when I connect 2 VIVE Trackers wireless with dongles and 3 VIVE Trackers with USB cables, tracking is good or perfect even. To connect the tracker with an USB cable, you need a little trick - first you have to plug in a dongle to an USB port, pair the tracker to that dongle and then remove the dongle and connect the tracker to the same port with USB cable. 4. I've tried turning off my WIFI router as it sends 2,4 GHz signal and can interfere with Bluetooth connections (at least in theory). 5. The trackers aren't placed near any metal objects that could interfere with their antennas. I use the TrackStraps and TrackBelt from the VIVE US store. Do you have any ideas or tips, what else I could test to have good quality, full wireless tracking with two controllers, and 5 VIVE Trackers?
  5. I've recently purchased a VIVE Pro with the wireless kit. I originally installed the WiGig card into a PCIe 1x slot. Upon encountering rather random (yet frequent) watchdog violations, I decided to try switching to a the second 'large' (16x?) PCIe slot. According to my mobo's manual, all 1x PCIes are only 2.0, while the two larger ones are both 3.0 (AB350 Pro4). However, the WiGig does not get recognized in this slot, even after cleaning, checking connections, etc. ('Please shut down your pc an d make sure the WiGig PCIe card is properly inserted'-error). No idea why, no change in bios settings seems to make the card recognizeable to the system. When I slot it into the 1x PCIe, it gets recognized without a problem. In both slots, the card is powered (blue LED glowing). My question is the following: is it even true that you need PCIe 3.0? I haven't actually heard any official statement to this effect. I.e.: should I try to somehow connect the WiGig to a PCIe 3.0-like slot (e.g. via an M.2 adapter) or is this likely not the issue at all? If it's the latter, I'd just try and solve the issue whilst using the PCIe 2.0 slot (where the HMD actually works most of the time). That said, so far all watchdog bsods happened during intensive first-time asset load events (i.e. they didn't occur during subsequent loadings of the same app, typically). This suggests that the watchdog violation has something to do with bandwidth bottlenecks. But that's just guesswork at this point :( Any suggestions? Any surefire ways to make my mobo recognize the WiGig in the 3.0 slot? Any reassurances that PCIe 2.0 is perfectly okay for the WiGig, bandwidth-wise? Specs: Motherboard: AB350 Pro4 CPU: Ryzen 5 1600, 16 gigs of RAM GPU: Radeon RX 580 Bios fully updated, new AMD chipset drivers, Ryzen gaming mode activated, SATA AHCI controller drivers updated, gfx drivers updated, UEFI reset to defaults.
×
×
  • Create New...