Jump to content

Search the Community

Showing results for tags 'focus plus'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


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


  • Viveport Blog
  • Viveport Reviews
  • Viveport SDKs and Downloads
  • Developer Blog
  • Vive Blog

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me

Found 22 results

  1. We've been working on an application in Unity using the XR framework, targeting different headsets. Originally developing towards the Quest 1, recently we have ported the project to Vive (minimal work required due to XR framework support) and found that the performance is vastly inferior to what we were seeing on the Quest, despite very similar hardware specs. While the Quest 1 happily runs around 72 fps, the Focus Plus easily dips into the 60's, and sometimes even goes south of 50 fps. This is entirely down to GPU performance. Looking into the profiler, it appears the Vive is rendering an awful lot more for the same scene and viewing point/direction: The render counts are almost 4 times that of the reported numbers on Quest. For reference, the Quest numbers are similar to what we're seeing on PC, while the Vive numbers are unrealistic and completely off the charts. Rendering is configured as Single pass on both targets, though even that wouldn't account for the perceived x4 increase in overhead. Any idea what's going on here? The builds are made from the same scene and project, with no differences except for which XR plugin is active. Project context: Unity 2019.4.18f1 LTS XR Plugin management 3.2.17 Wave XR Plugin 1.0.1 Oculus XR Plugin 1.7.0 XR Rig prefab Release build for both targets
  2. Hi, So I've been building an app for the Vive Focus plus. Occasionally when running the app I seem to notice tracking just doesn't start. I can see controllers working but the headset is basically just stuck to the floor (looking like 0,0,0 position). I'm using the xr interaction toolkit plugin with the xr plugin management to build to wave. I seem to have to quit then put the headset to sleep and then put it back on again for it to reinitialize. Any thoughts about what could be causing this? Thanks,
  3. I got a new HTC vive focus plus , the controller didnt pair to the hmd out of the box (its wierd issue the controller pairs with the headset but the UI doesnt change in the headset ). tried cache clearance and factory reset . can some one share the url or upgrade file for the firmware . I got this device 20 days ago all i see is pair your controller screen , The support team guided me here, Please help
  4. I am using Unreal Engine 4.22 and WaveVR version 3.1.94. When I build my project and run it on Focus Plus, it crashes immediately. The error shown in the log file is below: [2021.01.28-17.34.56:666][ 2]LogAndroid: Error: === Critical error: ===[2021.01.28-17.34.56:666][ 2]LogAndroid: Error:[2021.01.28-17.34.56:666][ 2]LogAndroid: Error: Assertion failed: Result == 1 [File:D:\UEPixo\Engine\Source\Runtime\OpenGLDrv\Private\Android\AndroidEGL.cpp] [Line: 333][2021.01.28-17.34.56:666][ 2]LogAndroid: Error: ERROR: SetCurrentSharedContext eglMakeCurrent failed : 0x300d[2021.01.28-17.34.56:666][ 2]LogAndroid: Error: [Callstack] 0x0000007F6A348A58 (0x000000000461BA58) libUE4.so!FDebug::CheckVerifyFailedImpl(char const*, char const*, int, char16_t const*, ...) [][2021.01.28-17.34.56:666][ 2]LogAndroid: Error: [Callstack] 0x0000007F6D1ED19C (0x00000000074C019C) libUE4.so!AndroidEGL::SetCurrentContext(void*, void*) [][2021.01.28-17.34.56:666][ 2]LogAndroid: Error: [Callstack] 0x0000007F6D211E2C (0x00000000074E4E2C) libUE4.so!FOpenGLDynamicRHI::RHIAcquireThreadOwnership() [][2021.01.28-17.34.56:666][ 2]LogAndroid: Error: [Callstack] 0x0000007F6B0D7B30 (0x00000000053AAB30) libUE4.so!FRenderingThread::Init() [][2021.01.28-17.34.56:666][ 2]LogAndroid: Error: [Callstack] 0x0000007F6A253F14 (0x0000000004526F14) libUE4.so!FRunnableThreadPThread::Run() [][2021.01.28-17.34.56:666][ 2]LogAndroid: Error: [Callstack] 0x0000007F6A1D43C0 (0x00000000044A73C0) libUE4.so!FRunnableThreadPThread::_ThreadProc(void*) [][2021.01.28-17.34.56:666][ 2]LogAndroid: Error: [Callstack] 0x0000007F8FC25F18 (0x0000000000068F18) libc.so![Unknown]() [][2021.01.28-17.34.56:666][ 2]LogAndroid: Error: [Callstack] 0x0000007F8FBDAFC4 (0x000000000001DFC4) libc.so![Unknown]() [] Has anyone experienced this error? Any help would be appreciated. @MariosBikos_HTC
  5. Greeting, Currently I having some issues that my app will crash whenever my client are using it from his side. I tested and casted from my side here that every time, there are no crashes. But when my client using it, it will crash and specially during casting at Windows Connect at his PC and using Windows Display Wireless Adapter. Here are my client PC hardware specs are:- Lenovo p330 i7 8th, 16G memory, LEADTEK p400 display card with 2G memory. Please, if anyone with have these kind of experiences, please share your solutions. Thank you.
  6. Hi, maybe somebody knows how is it possible to capture video in Focus Plus and save it to disk? I mean start/stop capture inside application
  7. Hi there! Im developing the port of a desktop VR application from Vive Cosmos to Focus plus, it was working, but in one day the app started to give me this error when i launch it in the Focus, some idea? Im ussing Unity 2019.2.21f1,Wave VR, Open VR and Steam Vr are in the project
  8. Focus and Focus Plus Firmware Update Released: October 27, 2020 VIVE Focus Plus ROM: 4.14.623.1 VIVE Focus ROM (Global version): 3.13.623.1 VIVE Focus ROM (China version): 3.13.1405.1 Great news! We have a big firmware update packed with new features that just released today. Please read below for the highlights and full list of features: When you’re ready to upgrade your device(s) - From the Viveport Home Menu > Settings > System Update to upgrade. HIGHLIGHTS: · Show non-VR apps (e.g. Mobile Device Management) in the Library. · Record VR experience with Screen Recording. · Adjust casting screen ratio from 1:1 to 16:9. · Support VPN connection in More Settings. · Activate Kiosk mode by default. · Upgrade WAVE SDK to version 3.2. FEATURES: 1. Support two MDM solutions, AirWatch and MobileIron. Note: In this update, the Launcher > Library will show 2D apps installed by users. (apps in data partition) 2. Adjust casting screen ratio from square (1:1) to rectangular (16:9). Note: Any app rebuilt with WAVE SDK 3.1.94 can support 16:9 casting. (even it runs on older ROM version) In-house apps (ex: Launcher) will support 16:9 casting in this SU update. 3. Support debugfs and atrace for developers to perform app profiling. 4. Support screen recording. User can start/stop screen recording via Quick Menu. The ratio of video is 1:1, and will be saved in internal storage. 5. Enhance screen share experience. Add “Casting”, “Screenshot” functions to Quick Menu. 6. Support MediaProjection permission for app developing. 7. Add Wi-Fi domain setting into COTA configuration. Enterprise customer can batch configure Wi-Fi connectivity with domain setting via COTA. 8. Lower the volume of boot animation. 9. Support VPN function in More Settings. The same UI and settings of VPN function in smartphone. 10. Make Tutorial app visible in Library. 11. Upgrade to WAVE SDK v3.2. 12. Activate Kiosk mode by default. Thank you again for your patience and support. Cheers, The VIVE Team
  9. Hi, Everyone. Today, I started making VR contents for Vive Focus by unity. I could build now but this windows popup everytime. How can I solve this?
  10. I am creating a VR project for Vive Focus with Unity. Run WaveVR Attributes and the following screen will appear. This screen is also displayed when you execute a build. Which manifest file should I modify?
  11. We realise how important it is for the development community to have easy-to-use tools that improve content performance. We recently released the new update of Wave SDK 3.1.94 [Early Access] with several Experimental Features for developers who create content for standalone VR headsets of the Wave Ecosystem such as the Vive Focus Plus and Vive Focus. In this update, we introduced changes to the Adaptive Quality feature, which can help to automatically adjust the rendering quality of your VR application according to the system workload in order to achieve better performance and improve battery life by up to 15%. This blog post will explain more about Adaptive Quality, why it is important and how to apply it to your own projects. We will provide an overview of the solution and its design/implementation and share a few tips on how developers can get started using it. We also describe how it works in synergy with other features of the Wave SDK such as Dynamic Fixed Foveated Rendering and Dynamic Resolution for better results. * Please note that Wave SDK 3.1.94 is an Early Access version that includes new features for developers to experiment with and provide feedback or suggest changes. These features are available only with a specific developer ROM update (and Adaptive Quality requires ROM v3.07.623.336 for Focus Plus) but content developed with this Developer ROM can't be published to Viveport until we release a public ROM update (coming soon!). Please refer to this article for more information on how to get access to the Developer ROM and test Wave SDK 3.1.94. Introduction Standalone VR headsets may have all the necessary components required to provide VR experiences, but unlike PC-based VR headsets, utilising the full power of their hardware requires an intricate balance for VR apps to run smoothly and with consistent performance. Heat generated from headsets working extra hard trying to render VR content can result in Throttling. The hardware will detect the high temperatures and when a predefined limit is crossed it will attempt to lower the clock speed of the CPU/GPU to prevent the system from overheating. When the temperature levels get back to normal, the system will increase the CPU/GPU clock speed and performance will bounce back again. Unfortunately, this process may be repeated and leads to poor battery life and inconsistent performance as the system is not able to quickly get rid of the generated heat. Although developers can mitigate this issue by trying to make sure games perform at their best at all times, this is not always possible. Adaptive Quality Adaptive Quality works by providing a way for developers to balance the performance of their VR applications and power consumption in real time, offering automatic adjustment of the CPU/GPU performance according to the workload of the system. Furthermore, it allows defining a set of strategies on how the application should respond to system changes to improve FPS when the rendering performance is insufficient. Adaptive Quality can be combined with the Dynamic Resolution feature to adjust the image quality of the application according to system changes and with Fixed Foveated Rendering to dynamically change the quality of the peripheral region when improving the performance is essential. This results in better battery consumption management and smooth frame rates, as developers have more control and can create and customise their own policies to dynamically handle hardware changes. Especially for GPU fragment-bound apps, this leads to less throttling and a better experience for the end users. Adaptive Quality v1.0 was first introduced in Wave SDK 3.1.1 supporting automatic CPU/GPU adjustment and system events according to workload. Starting from Wave SDK 3.1.94 we introduced new features and changes (v2.0) adding Dynamic Resolution and Fixed Foveated Rendering to the mix. Auto CPU/GPU Adjustment Standalone VR headsets are powered by a battery so making sure that power is not drained too quickly is important. With Adaptive Quality, we’ve made the management of CPU and GPU clock rates much simpler by making it almost entirely automatic. If Adaptive Quality is enabled, the system can dynamically change the CPU and GPU performance level to maintain performance based on the system load. So when the performance of your application is insufficient, CPU/GPU clock speeds will increase to improve the FPS. Likewise, if the application already runs at high FPS and the complexity of the scene is low, Adaptive quality can scale down the clock rates to save battery power for the headset and prolong its usage. Although we don’t provide direct access to the maximum/minimum-allowed clock speeds, Adaptive Quality can configure those properties based on its knowledge about the current system load and define if the levels should be lowered or raised. Of course, when Adaptive Quality is disabled, developers can still manually increase/decrease the CPU/GPU performance based on practical demands according to this API. System Events & Custom Policy Although we can change the clock rates to reduce power consumption or improve performance, that may not always be enough to achieve better results. Sometimes, more things need to change within the VR application software itself to get a stable performance. Adaptive Quality can be configured to broadcast events whenever there are changes to the system workload. This mechanism is really useful, since developers can create and customise their own policy to reduce GPU load and ensure constant frame rates over a longer period of time. Depending on the situation, the VR application can react differently according to those events and developers may create their own policies and choose whether and how to handle those changes and change scene complexity themselves. Developers can subscribe to receive performance events that recommend lowering or raising the rendering quality of the application and actively modify the rendering settings of the application in an equivalent way by enabling or disabling MSAA or other rendering settings that can help boost performance. Dynamic Resolution Dynamic Resolution is a feature that works together with Adaptive Quality and helps adjust the image quality of the application by changing the eye buffer size according to the events broadcasted (that we mentioned in the previous section). More specifically, the Resolution Scale will be increased automatically when the event received denotes that the quality can be higher and similarly, when the event type received recommends lowering the quality of the running application, the resolution scale will be decreased. In order to ensure that the Resolution Scale will not decrease to a point where the application is unusable, Dynamic Resolution comes with built-in functionality that helps determine the lower bound of Resolution Scale for different VR devices to maintain text readability. What’s great about this feature is that there is no extra latency introduced with the change in resolution scale. Dynamic Fixed Foveated Rendering Foveated Rendering is a technique that exploits the anatomy of the human eye and suggests that applications can drop the quality of graphics in the peripheral vision by lowering the resolution in that region while focusing all of the available processing power on a smaller area of the image(foveated region). The term “Foveated” derives from the word “Fovea”, the part of the eye retina that allows us to have a sharp central vision (Foveal Vision) which lets us focus on the visual details of what is important in a narrow region right in front of us. Anything outside the fovea region belongs to the peripheral vision and despite the fact that it is also useful, it can only detect fast-moving content changes and color, hence why it feels comparatively less detailed and blurry. It’s worth noting that there are 2 types of Foveated Rendering and the terms are sometimes confusing: Fixed Foveated Rendering assumes that the foveated region should always be at the center of the field of the view of the user and that lower resolution pixels should be rendered at the distortion region around the lens as things are already not clearly visible there. Eye-Tracked or Dynamic Foveated Rendering can be used with headsets that support eye tracking modules (Check Vive Pro Eye) to accurately define the foveated region based on gaze direction. It’s called dynamic because as the human eye moves, the foveated region keeps changing and the peripheral region keep changing dynamically. Adaptive Quality can be combined with Fixed Foveated Rendering to help increase the performance of VR applications according to system workload (dynamically). Fixed Foveated Rendering can be automatically enabled by Adaptive Quality to further reduce the GPU load and improve performance whenever it’s required. Results The benefits of Adaptive Quality can become more clearly articulated through some examples. The graph below illustrates how Adaptive Quality helps deliver smooth and high frame rates with a native fragment-bound application. In green, you can see the frame rate fluctuating when Adaptive Quality is disabled, with FPS going down as GPU workload increases. In pink, you can see the stable results after enabling Adaptive Quality running at 75 FPS. The x-axis indicates the time passed since the start of the application and the y-axis shows the FPS on the left and the GPU Level on the right. The yellow letters show the fragment loading values that increase every 5 seconds. Notice how the GPU clock rates go down when the FPS are high to save power(after 11 seconds and 61 seconds). Another graph below shows the results of a test using a Unity application and a GPU fragment-bound application. When Adaptive Quality and Dynamic Resolution are both enabled there is an increase of 13 FPS on average. In green you can see the case where Adaptive Quality is disabled, while in yellow you can notice how Dynamic Resolution tries to decrease the resolution scale to improve FPS and when FPS are high enough we increase the resolution scale back up again. We also tested Adaptive Quality with other applications such as Viveport’s Sureshot Game and SPGM. As you can see from the results, the energy consumption was improved by 10% and 15% respectively, indicating how useful it can be to use this feature in order to extend the battery life of the VR headset. How to use Adaptive Quality WaveVR SDK 3.1.0 to 3.1.6: Adaptive Quality is not enabled by default. The Wave SDK provides an API function called WVR_EnableAdaptiveQuailty that needs to be called manually so that the CPU/GPU performance levels can be adjusted automatically. The system events WVR_EventType_RecommendedQuality_Lower or WVR_EventType_RecommendedQuality_Higher will be broadcasted based on system workload and can be monitored to initiate actions according to them using the Wave System Event. Check System event to know how to listen these system events. WaveVR SDK 3.1.94 or later: Adaptive Quality is enabled by default and system events are broadcasted to change rendering quality when needed. One or multiple strategies can be used to adjust display quality and improve the FPS when performance is insufficient (WVR_QualityStrategy_Default, WVR_QualityStrategy_SendQualityEvent, WVR_QualityStrategy_AutoFoveation) Unity The WaveSDK package for Unity supports all the features of Adaptive Quality including the new features introduced with Adaptive Quality 2.0 (Dynamic Resolution and Dynamic Fixed Foveated Rendering) and it’s really easy to use. The WaveVR_AdaptiveQuality script can be used to enable the AdaptiveQuality feature. However, starting from WaveVR 3.1.94, this component will be pre-attached to the WaveVRAdaptiveQuality GameObject of the WaveVR Prefab. In this case, WaveVR_AdaptiveQuality is enabled by default. As you can see in the screenshot below, the WaveVRAdaptiveQuality game object is part of the WaveVR game object that is required to build VR applications that support the Wave ecosystem. There are 2 scripts attached to it: WaveVR_AdaptiveQuality: When this script is enabled, automatic CPU/GPU clock adjustment will take place and developers can tick the boxes under the Rendering Performance Improve Strategy section to define what strategies should be used (e.g I want system events to be broadcasted and Fixed Foveated Rendering to be enabled. In this case I need to tick both boxes). WaveVR_Dynamic_Resolution: This script is responsible for the Dynamic Resolution feature that adjusts the resolution scale of the VR application according to workload. An list of Resolution Scale values can be defined that will be used to adjust the resolution scale whenever there are events triggered by Adaptive Quality. Also the Text Size slider can be used to define the smallest size of text that will be used in the application to avoid having Dynamic Resolution making text unreadable. Unreal Engine Adaptive Quality can also be used with the Wave Plugin in Unreal Engine. Two functions are provided to enable the Adaptive Quality Feature and query whether Adaptive Quality is enabled or not. Although Auto CPU/GPU Adjustment is automatically supported when Adaptive Quality is enabled, Dynamic Resolution and Dynamic Fixed Foveated Rendering can’t be utilised at the moment with this plugin. There will be more updates on this soon. Wave 3.2 is expected to be released soon, adding support for system events in Unreal Engine. Summary Table Best Practices & Tips Now that you know more about Adaptive Quality here are some tips and advice: Rendering improvements by WaveVR AdaptiveQuality has limits. It is still highly recommended to optimise your app as much as possible first. Check our Mobile VR performance optimisation tips. Enabling WaveVR AdaptiveQuality can help lightweight VR apps, such as photo or video playing apps, be used longer. Enabling WaveVR AdaptiveQuality with WVR_QualityStrategy_SendQualityEvent and WVR_QualityStrategy_AutoFoveation can improve the rendering quality by up to 15% if the rendering bottleneck is GPU fragment processing bound. Always build optimized versions of the application for distribution. Even if a debug build performs well, it will draw more power and heat up the device more than a release build. Power management is a crucial consideration for Android VR development. Wave SDK force disables Adaptive Quality during map loading to increase performance and restores Adaptive Quality status after the map is loaded. Useful Links To implement Adaptive Quality in your own application, check the documentation pages below: Wave Native SDK Unity Integration Unreal Engine Integration Also see: System Event & how to listen to events Foveated Rendering Dynamic Resolution We gave a talk about Adaptive Quality and the new features introduced in the latest Wave SDK during the Virtual Vive Ecosystem Conference back in March 2020. You can watch the presentation below: What do you think? Feel free to try this feature and provide feedback from your tests in our forums. You can also find the complete list of new features for each Wave SDK update in our release notes.
  12. Back in release 2.1.8 we were told to make sure to handle BOTH the new Alias1_Trigger and Alias1_Digital_Trigger in our code. In Wave SDK 3.1.6 the new WaveVR_Button List was introduced but for some reason the DigitalTrigger is commented out. Our app needs to run on BOTH focus and focus plus. Can someone help us figure out what buttons map to which enum values as of 3.1.6 See the Assets\WaveVR\Scripts\WaveVR_ButtonList from the latest unitypackage for Wave SDK 3.1.16: @Cotta @Tony PH Lin
  13. What's the main difference between Kiosk mode on the Vive Focus Plus and Vive enterprise private content management from Vive STARTER. I'm having some people use a Vive Focus Plus and I only want them to run one program. I know I can use Kiosk mode but can I do that with STARTER? Thanks in advance. @Tony PH Lin @Cotta @JustinVive
  14. Today, we've released a new ROM update version 3.07.623.3 for the Focus Plus. This update is available as a FOTA and you should receive a message in your device prompting you to make the update. It includes a medley of improvements, listed below. Here are the release notes: Add support for Wi-Fi 2.4GHz band. Add support for VIVEPORT Streaming. Add Wi-Fi setting and Cast function on the Power button menu when in Kiosk mode (to disable, go to More Settings > Kiosk mode). Enable/Disable “Lost tracking” warning in Developer options. Adjust the play area size (2x2m, 3x3m, or 4x4m) in Developer options. Show controller firmware version in Quick Settings > Controller. Add a 5GHz regulatory e-label for Japan in More Settings > About > Certification. Add Korean language support. Update WAVE SDK version to 3.1.7.
  15. Hey, I made some VR with HTC Vive, the workflow wasn't perfect but it was ok : a simple play in the Unity editor, and you remove quickly the helmet you grab the error etc. Debugging on the Vive Focus is an other challenge. How do you do guys? I compile with development build and script debugging, and I set the console for remote, but I must leave my helmet to see if I've an error. I found this plugin https://assetstore.unity.com/packages/tools/gui/vr-console-106491 it works ok : just put the console in the scene and you have live error & log. What process are you using?
  16. This might be a dumb question, but I haven't found anything in the documentation on it specifically. I assume there's a straight-forward way of showing/hiding the default controller models during runtime? I guess on that same thought process is there a simple way to replace the controller models with something different if desired? Thanks Vive Focus Plus Unity 2018.4.14f1 Wave SDK 3.1.4 @Cotta @Tony PH Lin
  17. Dear HTC I am trying here as i now have tried 3 times through your advantage program without any response on the matter from Lisa. We are a development company in EU, primarily developing for Vive and Vive Focus+ the casting is still very unreliable and exact as other have mentioned back from September 2019 and onwards. The casting to MiraCast doesn't work on all devices and are very buggy. I could cast to PC, Win10 the first 2 times and after a software update from VIVE the casting to PC wont work, and casting to anything else than Microsoft Wireless Display Adapter wont work. We have tested 17 different HTC Vive Focus+ with the danish government over the past year and all with the same result, so no its not a issue in 1 headset but a software issue. I am, while writing, sitting at my pc, with the Vive Focus+ headset next to me, on the same 5GhZ internet and can see the PC name in casting on HTC Vive Focus+ but when connecting it crasches and cannot connect. So the statement that it works for Pc is not correct. It wokrks for Pc 20% of the time and for casting to a dongle 80% of the time. (Based on 1 year of daily usage with the Danish government, conferences, event and presentaitons) It is very unreliable as we not have been to events and conferences with it all working and next day no casting, with same setup and not changes from prior day. Please please please fix the casting, its a standard format as you HTC mention yourself in your documentation and should work 100% as in any other product on the market. The headset is sadly unusable without casting when developing and using with patients and governmental rehabilitation, as the staff need to monitor the patient when training. - Best VR Rehab @Tony PH Lin @Cotta @JustinVive
  18. I am investigating HMDs for a game soon to be in development, and I was hoping someone could fill me in on best practices for the Focus Plus units. Is there a functional difference between the developer kit version and the consumer model of the Focus Plus? This unit appears to be the old version of the Focus. Is there a dev kit for the Plus model? The units would be running a single application at any given time so I presume something akin to kiosk mode would be used, or are apps only intended to be loaded via Viveport? Thanks @Tony PH Lin @Cotta @JustinVive
  19. We've run into an issue migrating our app from the Focus to the Focus Plus. We are using the Native Media SDK (NdkMediaCodec.h) for decode. For whatever reason the same NDK decoder that works fine on Vive Focus, doesn't work on the Focus Plus. What happens on the Plus is, a couple frames get decoded, and then decoder stops producing output. There are no related errors in Logcat. The only difference I can see between the two devices is the Wave SDK version. Any ideas? Thanks, Krasi @Tony PH Lin
  20. Hi everyone, The last week i bought a HTC Vive Focus plus with the Vive Entreprise Advantage for Focus Plus. To test it, i download on unity the WaveVr SDK with Samples scenes, but i can not build or export this example on my HTC Vive Focus Plus. Can you help me solve this problem please? @Cotta @Tony PH Lin
  21. In order to build for the Focus Plus you will need to integrate your apps with the Wave SDK. For more information about Focus and Wave development check out our Vive Developer Resources Site. You can find both the Wave SDK and Documentation linked from this Resource page. If you’re a Unity Developer, then Getting Started with Unity and Wave SDK will be very helpful. If you’re looking for community help, be sure to visit the Wave SDK Forum to find answers to your questions or to ask new ones you may have. You can find best practices for HMD and controller tracking - Room Setup and Controller Tracking Tips. Read the Vive Focus Plus User Guide to get acquainted with it. Make sure to update your HMD to the latest ROM (currently version 4.14.623.x). You can update the device by tapping on the controller’s Vive button and then > Settings > System Update (Note: You must be connected via Wi-Fi in order to receive system updates). If you need to debug your app, check out this post about ADB Logcat. Once you’re ready to publish your app on Viveport, visit the Viveport Developer Console. If you need inspiration, feel free to find some fun right away and get to know some of the Wave experiences. Visit the Viveport M store in the HMD and peruse the titles with the 6+6dof label. This label indicates that the experience is compatible with the 6dof headset and the 6dof controllers. Here are some great suggestions: Browse the Virtual Web with Firefox Reality. Download Sureshot: RPO Edition. In this Ready Player One app you can freely move and shoot in full room scale glory! Check out Skyworld Kingdom Brawl, which is Vive Studios’ tactical card-battler, Clash Royale-inspired collaboration with Vertigo Games. Or try Kingdom of Blades for some sword swinging, shield bashing action! If you’re looking to purchase a Focus Plus, they are available at this link https://enterprise.vive.com/us/focus-plus/. For bulk orders, please reach out to your Vive contact for more information. If you have any questions, please don’t hesitate to reach out to us. We look forward to experiencing what you create. See you in VR, Justin and the Vive Team
  • Create New...