We are using HTC Focus Vision headsets and running Vrsketch via Vive Business Streaming from a PC.
Within the Vrsketch application, the displayed controller model appears to be the HTC Vive Pro controller, which is different from our HTC Focus Vision controllers. please provide guidance on how to adjust the controller visualization within the application when using HTC Focus Vision with Vive Business Streaming?
HTC Focus Vision - Controller Display Issue
The Focus Vision is not explicitly supported by VR Sketch and we don’t have the hardware needed to test it ourselves. That’s why you are not getting the exact correct controller models.
In a perfect world, the software installed on your machine would provide VR Sketch with the correct controller models and all relevant parameters to be able to animate and use them. However, we don’t live in a perfect world and doing so is just not possible. So we fall back to providing a few well-tested, manually-adjusted controller models with VR Sketch, as described in the “Requirements” section in our documentation. For all other controllers, we pick a default model to fall back to and display that.
That said, looking at photos, the Focus Vision controllers are a lot closer to the Oculus Rift/Meta Quest controllers than to the old Vive controllers, and so we should probably attempt to detect that the user is running a Focus Vision and use the Meta Quest controller models. Doing so might already improve the experience by reducing the mismatch. Please note however that even detecting that we are running with a precise headset (that we don’t own ourselves) might involve some trial and error. If we figure it out and post a pre-release version of VR Sketch here, would you be up to trying it out and tell us if we were successful?
We are indeed using the HTC Focus Vision as a testing headset as we explore options for upgrading our VR Lab facility. Absolutely, we would be very happy to test a pre-release version of VR Sketch if you are able to implement this detection and controller model adjustment for the HTC Focus Vision. We are committed to providing thorough feedback on its functionality and any improvements we observe.
Can you let us know which version of VR Sketch you are currently using, and if it’s not the latest one, could you try with the latest one? https://vrsketch.eu/downloads.html
We are currently using VR Sketch version 20.0.2. This is because it’s the last version that we’ve found to be stable and fully functional with our existing facility setup.
We have experimented with the latest VR Sketch versions in the past, specifically with the HTC Vive, but encountered compatibility issues that prevented them from working correctly. This is why we reverted to version 20.0.2, which has been reliable for our needs.
We are now testing the latest version with the HTC Focus Vision, but we are encountering a new issue: the software indicates that no compatible headset is connected, despite the HTC Focus Vision being properly connected to the system.
We are always eager to get reports of regressions (if they are detailed enough), i.e. things that used to work with older versions and no longer work with the latest version. We may struggle to reproduce and fix them if they are related to specific headsets that we don’t regularly test, but getting information about the issues is the first step for us!
The “no compatible headset is connected” problem is an issue outside the scope of VR Sketch. It means that at the time you started VR Sketch, the headset was not considered “connected”. With headsets that work both as standalone or tethered headsets, you usually need to make sure that the headset is in tethered mode. For reference, on Quest you need to start the “Meta Link” application on the PC and then select “Link” in the Quest’s own Quick Settings. Before that, the headset is not considered “connected to the PC” for the purposes of tethering. If you’re still getting the same error, you should try to reboot the PC and the headset, and/or double-check that you can run a different VR program from the PC.
About the original controller display issue: as far as I can tell, the controllers “should” be displayed as Quest-like rounded controllers and not the older-HTC-Vive-like wands. VR Sketch should use the Quest-like controllers by default for all unknown controllers since 2022, and all the versions we are talking about are from 2024/25. I don’t know why in this case it doesn’t work. The VR subsystem might just be reporting the wrong controllers… I’m also slightly confused by the screenshot you sent to me, as the controllers displayed there look a little bit like the ones from a pre-2022 version of VR Sketch (but I’m not sure about that).
If you can confirm first that the latest version of VR Sketch eventually works for you, and that version is still showing the wrong kind of controller, then I could try to make a program that you’d run on your machine; it would display a few lines of information, and I’d ask for you to copy that information back to me.