Jump to content

EricLu

Verified Members
  • Posts

    7
  • Joined

  • Last visited

Reputation

1 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. In the Vive XR Elite OS, when I pair the wrist trackers, it always asks me to unpair both controllers. I could not find a way to have both controllers and wrist trackers paired. As such, they never appear simultaneously in the Vive Business Stream portal. Are there specific steps that I should do to pair the wrist tracker as a vive tracker when the controllers are paired?
  2. A follow-up question on this. If I understand correctly, we still cannot use wrist trackers and controllers at the same time, even if wrist trackers are emulated as Vive trackers. Is that correct?
  3. Yes, that is correct! I used the Vive focus 3 profile and used the Vive browser to open it.
  4. Hi. I am trying to build WebXR applications on the Vive XR Elite. When I develop using the WebXR input profiles on the Vive browser, somehow only the grip button and trigger button could be detected on the controller. The A/B/X/Y/Thumbstick buttons are not working. Please check this scene for a demo of the issue: https://playground.babylonjs.com/#28EKWI#490. If you go to this link on the Vive browser and go in immersive vr mode, when you press a button, a cube will change scale. Though only three buttons on the controller is detected. The WebXR input profiles does not support Vive XR Elite (https://github.com/immersive-web/webxr-input-profiles/tree/main/packages/assets/profiles), so I used the Vive focus 3 profile, which has essentially the same controller components. I wonder whether this is the issue, or a vive browser wolvic version issue. Any help would be much appreciated. Thanks.
  5. Hi thank you for the reply! May I know the timeline about when it will be fixed? Thanks.
  6. Hello, I encountered the error while importing the scene perception sample from the Wave XR Essence. It shows the following errors: Assets\Wave\Essence\ScenePerception\5.6.0-r.10\Demo\Scripts\ScenePerceptionDemo.cs(7,12): error CS0234: The type or namespace name 'XR' does not exist in the namespace 'Wave' (are you missing an assembly reference?) Assets\Wave\Essence\ScenePerception\5.6.0-r.10\Demo\Scripts\ScenePerceptionDemo.cs(53,17): error CS0246: The type or namespace name 'InputUsage' could not be found (are you missing a using directive or an assembly reference?) Assets\Wave\Essence\ScenePerception\5.6.0-r.10\Demo\Scripts\ScenePerceptionDemo.cs(59,3): error CS0246: The type or namespace name 'Controller' could not be found (are you missing a using directive or an assembly reference? Assets\Wave\Essence\ScenePerception\5.6.0-r.10\Demo\Scripts\ScenePerceptionDemo.cs(60,3): error CS0246: The type or namespace name 'Controller' could not be found (are you missing a using directive or an assembly reference?) Assets\Wave\Essence\ScenePerception\5.6.0-r.10\Demo\Scripts\ScenePerceptionDemo.cs(54,4): error CS0103: The name 'InputUsage' does not exist in the current context Assets\Wave\Essence\ScenePerception\5.6.0-r.10\Demo\Scripts\ScenePerceptionDemo.cs(55,4): error CS0103: The name 'InputUsage' does not exist in the current context Assets\Wave\Essence\ScenePerception\5.6.0-r.10\Demo\Scripts\ScenePerceptionDemo.cs(56,4): error CS0103: The name 'InputUsage' does not exist in the current context Assets\Wave\Essence\ScenePerception\5.6.0-r.10\Demo\Scripts\ScenePerceptionDemo.cs(57,4): error CS0103: The name 'InputUsage' does not exist in the current context Assets\Wave\Essence\ScenePerception\5.6.0-r.10\Demo\Scripts\ScenePerceptionDemo.cs(58,4): error CS0103: The name 'InputUsage' does not exist in the current context The packages works fine without error without importing the scene perception package. I am using Unity 2022.3.4f1. Thanks.
×
×
  • Create New...