dario

Hi Glen, I've managed to get stereo 360 video playback on the Vive Focus working with Unity's VideoPlayer by using their https://github.com/Unity-Technologies/SkyboxPanoramicShader which allows you to specify over/under. Let me know if that works for you, Dario

https://vivedeveloper.com/knowledgebase/vive-srworks-sdk/ SRWorks SDK Updated to version 0.7.0.0 - Changes: 1. Generate colliders by adaptive mesh and patch the fragile colliders together to prevent from holes without physical collision in the previous version, referring to its demo video $(Vive-SRWorks-0.7.0.0)\Unity\Demo Video\ 2-Spatial Scan.mp4. 2. Export more collider properties: Orientation(Horizontal, Vertical, Oblique), Shape(Convex, Bounding Rect, Mesh), Area (Approximate) 3. Export Unity API: GetAllHorizontal(Vertical) / GetLargestHorizontal(Vertical) / GetColliderWithProperties( property array ); 4. Provide a Portal prefab in Unity to facilitate the developer to create a portal for the player passing through between real and virtual worlds, referring to its demo video $(Vive-SRWorks-0.7.0.0)\Unity\Demo Video\ 4-Portal.mp4 and user guide $(Vive-SRWorks-0.7.0.0)\Unity\Plugin\SRWork_Portal_Unity_Guideline.docx for details. full video 5. Fixed Unreal occasionally crash occurred in v0.6.0.0. 6. Fixed Sample3_DynamicMesh of SR Experience would not work issue in v0.6.0.0. 7. Please update NVIDIA graphics driver to 390.77 or later to fix SteamVR occasionally frozen on some platform with NVIDIA Pascal series.

Additional Notes for Unity Developers not currently in the documentation: Please also look at the Experience demo source code for 4 new additional sample scenes (in addition to the main Demo scene). These four additional scenes illustrate the following features: Effect Switch Mode Depth Image Dynamic Mesh Static Mesh Also note there is an existing issue with the Demo scene and the 4 sample scenes: You will need to revert [ViveSR] to its prefab in each scene to correct a duplicated component in the DualCamera child object.

Update to Vive SR SDK: v0.6.0.0 now available to download. 1. Unreal plugin supported. 2. Support live and adaptive mesh creation during static scan. 3. Mesh simplification and categorize plane’s colliders to Horizontal and Vertical in OBJ file if matched criteria. 4. Optimization for see-through judder removal even depth function enabled. 5. Improve dynamic mesh quality and increase its distance range from 2m to 10m. 6. Adjustable frame rate of depth stream adapted to various applications. (default 30 fps) Please see the full release notes for additional information, illustrations and known issues.

I forgot to add the following keyboard input adb command: adb shell input keyevent 23 useful for selecting a popup dialog to set focus on or to 'click' on a selection or button to navigate to a button use the following key codes (includes volume control) 19 --> "KEYCODE_DPAD_UP" 20 --> "KEYCODE_DPAD_DOWN" 21 --> "KEYCODE_DPAD_LEFT" 22 --> "KEYCODE_DPAD_RIGHT" 23 --> "KEYCODE_DPAD_CENTER" 24 --> "KEYCODE_VOLUME_UP" 25 --> "KEYCODE_VOLUME_DOWN" In summary you can use adb commands to avoid having to use or install Vysor. You can also automate standard Android UI navigation with scripts. Eventually all of the Android UI popup dialogs will be in VR, but for now (e.g. for a rom update) you can navigate and click on buttons with the keycodes above and just use adb from the command line.

Hello, I'm curious as to your motion capture use cases and if you've considered a Vive Tracker only setup for motion capture. Were you able to work around the issue with the advice of using just video capture instead of infrared? I would also suggest to look at the hotspots or rather cold spots of coverage in the Tracker documentation as tracker placement could be a factor as well. Relatively speaking sensor coverage is greater on the HMD and controllers compared to the trackers, therefore placement (or how it's held) can affect tracking due to occlusion, Base station placement may need to be higher than usual to avoid occlusion. -Dario