Tony PH Lin

Hi @SocoDev, Suppose you already have read the sample we provide: https://hub.vive.com/storage/docs/en-us/UnrealPlugin/UnrealTeleport.html In document we provide simple and basic function to demo functionality, since we think most developers may customize teleport movement on their own design. Thanks.

Hi @zws, Here is the path when you download SDK from the server, and you can find the related document for Unreal development. Hope this info. helps. Thanks. SDK-v1.3.3.0.zip\SDK\03_Unreal\Document

Hi All, The latest SRanipal V1.3.2.0 has been released, and please have a test to verify this issue. https://developer.vive.com/resources/vive-sense/sdk/vive-eye-and-facial-tracking-sdk/ Thanks.

Hi @Federica, We think you're using the pupil_position_in_sensor_area and it means the pupil position in the eye image that’s captured by eye tracking camera. If you want to get the gaze coordinates you may consider to use gaze_origin_mm and gaze_direction_normalized and do some coding in Unity 3D space. ViveSR.anipal.Eye.SingleEyeData Struct Reference Public Member Functions bool GetValidity (SingleEyeDataValidity validity) Public Attributes System

Hi @Khan Mila, You may try to use the saved static mesh file to do any post-processing by other tools such as MeshLab or Blender. Thanks.

Hi @Realter, Maybe this discussion comment by HackPerception is helpful for you. Thanks.

Hi @GregLux, Which SDK version are you trying? Is it 3.2? Currently in Wave SDK 3.2, we support Direct Preview with legacy plugin. For the XR plugin support, it's under development and will be included in next release. Will keep you posted once we confirm the next release schedule. Thanks.

Hi @xunhaosteam, Thanks for your feedback, and this is for our internal development usage. We will remove this in new updated version. Sorry for make your confusion.

Hi @intranuclear, To modify the WaveVR_InputModuleManager will NOT take effect due to the settings will be overwritten by the WaveVR_Pawn. You just need to do what you did for WaveVR_InputModuleManager on the WaveVR_Pawn. The event button settings are controlled by the WaveVR_Pawn, not WaveVR_InputModuleManager. Thanks.

Hi @kaden, Just revisit your issue, have you got the chance to try the latest 1.3.1.1 SDK and runtime or is the issue still existed on your side? Thanks.

Hi @nbhatia, We have listed recent change notes here: https://developer.vive.com/resources/vive-sense/sdk/vive-eye-tracking-sdk-sranipal/ If you're looking for whole history change log, we will extend in future release version. Thanks.

Hi @xunhaosteam, This is the example for OEM customer usage since they may have system permission for app control if they're implemented the app to doing the record for whole system-wise. In other word, this feature is not applicable for generic content developer. Hope this info. is helpful for you. Thanks.

Hello, Yes. thanks for the report. Kotlin library had been included in wvr_client.aar. And we will remove the dependency of Kotlin related libs so that developers can use the version that they want to use. In short term, you should be able to designate the version by using gradle build to avoid the conflict. Thanks.

Hi @ssid, Thanks for the feedback. Regarding the usage of system events in XR Plugin, you are correct (i.e. System events in XR Plugin are handled through the SystemEvent.cs script) As for example usage, WaveEssence.cs contains some code which shows how to subscribe to and unsubscribe from System Events (on Monobehaviour OnEnable and OnDisable).

Hi Martijn, @pascalvanbeek Thanks for feedback, and we've clarified it's our bug and we will have fix on next release. For short-term if you'd like to make it work, please use API below: https://hub.vive.com/storage/docs/en-us/WVR_RenderFoveationMode.html Or refer the C# script Wave.Essence.WaveXR_FoveatedRendering Thanks.