Jump to content

zzy

Verified Members
  • Posts

    219
  • Joined

  • Last visited

Posts posted by zzy

  1. Hi @JayPark

    Since you are using Google Cardboard, then you are using 2d point mode. In this mode, only 1 2d point is returned to represent each hand.

    If you are working with the sample scene, it already supports 2d point mode and it only displays 1 point for each hand. Although the API returns 21 points, only the first point is meaningful for 2d point mode. All other 20 points should be zero values and should be ignored.

    If you are using the latest v0.9.1 version, there is a switch between skeleton and hand model if you make like gesture with both hands (thumb up). In such case, your hand point may disappear. You can make it appear by making the same gesture again.

  2. Hi everyone,

    Vive Hand Tracking SDK has a new release v0.9.1 today. You can download it from here.

    Highlight of changes:

    1. Update deep learning models for all platform.
    2. Improved skeleton results to be more realistic hand poses for human.
    3. Reworked algorithm to reduce jitterness.
    4. Changed hand 3d model to a robot hand which should be less scary then previous.

    For detailed changes, please refer to release notes.

  3. Hi @yann,

    From the log, it seems that the camera is currently being used by another app, and therefore Vive Console cannot start the camera.

    Please help to check the following items:

    1. Is there any error displayed in Vive Console? Please also check the camera tab in settings.
    2. Please help to identify if there are any other apps that is using camera. Please try to close all unrelevant apps or restart your PC to see if it helps.
    3. Please help to check if the camera see through function is working correctly. Double press the Vive button of your right controller to enable/disable see through. You should be to see your environment if success.
  4. Hi @yann

    I confirmed again about the Vive console, hand tracking sdk v0.9.0 works fine on our test machine with Vive console v1.0.10.4 beta, so maybe I was wrong about the API bug in previous post.

    Please make sure following requirements before start hand tracking:

    1. Cosmos HMD is in ready status. Avoid sleeping, or not tracking status.
    2. Put on your Cosmos HMD

    If you still meet the same problem, can you provide some logs about your failure? You can delete existing logs and run again for more clear logs. Just make sure to close application and vive console when you delete/copy the logs.

    1. Hand tracking  SDK log: %APPDATA%\..\Local\Aristo\Aristo.log
    2. Cosmos runtime log: C:\ProgramData\HTC\ViveSoftware\ViveVRRuntime\logs
  5. Hi @yann

    We are aware of this problem. This is due to Vive console v1.0.9.x has changed the API for camera and breaking the hand tracking SDK.

    We plan to release new version (v0.9.1) by the end of this month, which should have fix for the problem. In the mean time, you can check if it's possible to downgrade Vive Console to version v1.0.8.8 which should work with hand tracking sdk v0.9.0.

  6. Hi @davide445

    3. Someone has asked similar questions ealier, see this post. Unfortunately, it's may not easy to wrap hand tracking as an openvr driver, since hand tracking itself depends on openvr to get camera stream.

    5. I'm not sure about your question.

      a. License to use Cosmos/Vive Pro for commercial? @VibrantNebula can comment.

      b. License for Vive Hand Tracking? It's OK to use Vive Hand Tracking SDK in your commercial VR app. It's not allowed to redistribute/sell the SDK package itself to your customers.

    • Like 1
  7. Hi @davide445

    To answer your questions in order:

    1. All OpenVR API except for camera can work for Cosmos, so most existing VR applications can work directly on Cosmos. For Hand Tracking, please use the latest release (v0.9.0) which already takes care of different camera API. The user interface is same for different operating system or HMD. The prebuilt example works with Cosmos, you can use it to evaluate current performance of hand tracking sdk.
    2. To be honest, this is my first time to hear about Unigine and as @VibrantNebula stated, we currently don't have experts nor plans for Unigine. If you want to use hand tracking in Unigine, you have to do integration yourself using the C++ API. You can reference Unity/Unreal plugin for how to call the API functions.
    3. I think you can emulate controller with limited interactions, you can use gesture to emulate 1 or 2 buttons, but it could be difficult to emulate all buttons.
    4. You have to refer to Leap Motion SDK for integration with Unigine in this case.
    • Like 1
  8. Hi @WOP

    I'm not really familiar with the SteamVR driver part, but since Hand tracking consumes SteamVR camera texture, I think there it's not surprising to have a loop dependency in this case.

    We are still evaluating the possibility to map hand to controllers right now, and there is currently no estimated time for this. If you need to achieve this, you might need to do it in Unity or Unreal instead of doing it in SteamVR driver.

  9. Hi @DLight

    To troubleshoot performance on Cosmos, please make sure:

    1. Your Vive Console version is at least v1.0.7.x, recommended version v1.0.8.8
    2. If you are using other SDKs that uses camera, please turn them off first, so we can make sure the problem is in Hand Tracking SDK
    3. Please use see-through to check your environment and hand condition. Make sure your hand is neither too bright (i.e. no texture is visible) nor too dark (hand barely visible from background). You can open/close the Cosmos see-through by double clicking the Vive button of right controller.

    By the way, can you share the video about cosmos? Let me check what version of SDK it's using.

  10. Hi @UPSImmersiveLab

    The status for Vive Focus and Vive Focus Plus are same, support for skeleton mode is planned to release by the end of this year.

    The current version (v0.8.2) supports gesture and 3D point detection on Focus and Focus plus. If you encounter problems about building with WaveVR SDK, please create a new post with the error you encountered, so we can help you to solve it.

    The supported WaveVR version is 2.1.8 or newer. If you are working with Unity, I would recommend you to use LTS versions (2017.4 or 2018.4), since they are more stable. We do support 2019, but newer version after plugin release may have some features that break the plugin.

  11. Hi @JCSegula

    The current release do have some jittering in the results and we are trying to improve it. Internally, we do have some improvements with the jittering and expect to release new version before the end of the year.

    For now, I would suggest you to make the buttons (or only the trigger area) slightly larger so you can trigger the button easier.

    • Thanks 1
×
×
  • Create New...