Jump to content
 

Search the Community

Showing results for tags 'question'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

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

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. so we got an cosmos elite bundle, we got a face plate coming and the elite headset stand alone are we going to get a face plate bundle? Because that's a lot of individual tech early adopters to the cosmos series have to buy to improve their tracking experience particularly if you don't own a vive og. If the cosmos elite bundle is $1699(aud) and a cosmos without a face plate is about $750 (the elite headset $1099 minus the face plate $349) so $1699 - $750 = $949 worth of needed tech, purchasing theses separately from the store is over $1,148.96 + what ever the converter cable costs( face plate $349 + controller $199.99 + controller $199.99 + base station 199.99 + base station $199.99) so that an extra $150 or so we have to pay to be on par with an elite....(I'm in Australia so sorry but I'm doing everything aud but the point is the same) its better to sell my cosmos and buy a elite bundle plus a little cash because buy the looks of things i could buy the og cosmos controllers and face plate after and have it still end up cheaper (og cosmos controllers x2 is $358 + $750 for a plateless head set + pro link box $86.99 = $1194.99 - $1299 = $104 but its the same price as the other face plate at $349). So if you want to upgrade your tracking from og cosmos its gonna cost you $2447.96 all up including you original cosmos purchase or if you bought the elite for $1699 and wanted base station freeless for some weird reason it be $2406 and just to make an additional point buy an og vive estimate 900(they aint that much but what ever) + og cosmos controllers x2 $358 + elite headset only $1099 + cosmos face plate 349 = $2706 it is literally cheaper if u own a og cosmos to buy an og vive new and an elite face plate for about the same as buying all the the other tech then you still have the option to sell the brand new og vive headset for a profit and yes you can still find them lol you can buy the vive pro starter kit for $1299 or upgrade your cosmos og to elite for + $1148.96 thats fairly brutal hell you could buy the kit sell the head set buy the face plate profit damn was only gonna see if there was gonna be some bundle for us early cosmos adopters but I'm almost certain i just convinced myself to buy a vive or pro kit new or refurb then sell the head set and buy the faceplate ....
  2. I recently, (as a gift to myself) got the HTC Vive VR Headset. It's already tons of fun, and I love it. But thats besides the point. I know that there are a few key things missing that would improve the user experience, however I am still a noob on this topic. Does anybody have a list of the best accessories for the HTC Vive? That would be awesome. Thanks for your support!
  3. According the guide on setting up the Vive Cosmos, it says to make sure to remove the protective film on the lenses. I bought my Cosmos brand new from a retailer and the box was still taped shut, and every other protective film/sticker was still on the headset, yet I don't see or feel any protective film on the lenses. So does the headset actually come with protective film on the lenses? I'm asking this because the edges of the lenses when looking around in the headset are very blurry, no matter how close I can get the headset (it will improve FOV but not the edge clarity). Thanks @stvnxu @C.T.
  4. Hello folks, I am running into a problem interfacing with the OpenVR SDK when using two trackers with one controller. Specifically, the IVRCompositor::WaitGetPoses( ) function will sometimes return incorrectly transformed matrices to my C++ application. I was wondering if anyone has experienced a problem like this before, or if there is a known solution. The scenario: I place two VIVE trackers about 1 foot apart from one another, facing the same direction. I would expected that the matrices of each tracker (stored in TrackedDevicePose_t -> mDeviceToAbsoluteTracking) will be very similar. If I power up in this order - Tracker 1 On, Tracker 2 On, Controller On - the matrices of both trackers are indeed almost identical. However, if I power on in a different order - Controller On, Tracker 1 On, Tracker 2 On - The matrices of one of the trackers will be rotated exactly 90 degrees from what I would expect. The other tracker still retains the correct values/orientation as before. So now, even though both physical trackers are sitting in similar positions and orientations in the real world, their matrices returned by the VIVE SDK's WaitGetPoses( ) are different. In the same session, I can power on/off the controllers in different orders to change whether I get the correct or incorrect matrix values from the tracker. I am certain this is not a problem with my tracked device indices, nor a problem with overflowing array bounds, because the XYZ Position of the "Bad" Tracker is always correct - it is only the rotation of the tracker about that position in space that changes. So at least one value in every row in the matrix is what I expect. The correct Tracker[index == 3] 4x4 matrix (left) vs. the incorrect Tracker[index == 3] matrix (right) [ -0.99, 0.00, -0.17, -0.20 ] [ 0.99, -0.05, -0.12, -0.20 ] [ 0.00, 1.00, 0.00, 0.72 ] [ -0.01, 0.00, -0.99, 0.72 ] [ 0.01, 0.00, -0.99, 1.38 ] [ 0.05, 0.99, 0.00, 1.38 ] [ 0.00, 0.00, 0.00, 0.00 ] [ 0.00, 0.00, 0.00, 0.00 ] To specify the configuration I am using, my OpenVR SDK is version 1.0.10, my VIVE trackers are the newer model with the blue triangle, and my base stations are the older model. If anyone knows of a fix, workaround, or simply something to try, I would be very grateful for the help! Right now I am thoroughly stumped! Thanks! @chengnay
  5. Do you have any plans to resolve the occlusion issue? When one hand is in the front, the other is in the back,the front hand can not be tracked。
×
×
  • Create New...