jefmes
-
Posts
79 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Downloads
Posts posted by jefmes
-
-
On 10/10/2022 at 4:03 AM, niil said:
As I understand it, now VBS sends a picture at a resolution less than native when using the QUALITY profile. Are there any improvements planned for this part? Is it possible to add a separate profile with native resolution for content that is not critical to delays
One more vote for this, I have a Wifi 6E network and would love to be sending at 2448 x 2448 on Quality, add another option for "Ultra Quality" that allows those of us with the right hardware to send at that resolution?
-
Could someone on the team clarify what is actually happening in the VBS Advanced settings section for OpenXR, VIVE Open XR, when you tell it to "Register"? I'm trying to understand if this is a move to a full VBS OpenXR runtime so that we don't need to run SteamVR, or if this is something else entirely?
Long story short, I am doing some experimenting with StereoKit, and using VBS to interact with a very simple environment, but the hand tracking is counter-rotated by 90 degrees. It seems as though the hands are oriented for controllers rather than actual hands. I've been told that the OpenXR extension XR_EXT_palm_pose that was revised earlier this year should be handling that, but something is amiss and I'm trying to understand where the problem is actually occurring. Here's a short in headset video of what I'm experiencing.
-
On 9/28/2022 at 11:07 PM, C.T. said:
-
Supports OpenXR vive_focus3_controller profile.
- OpenXR developers can now develop with vive_focus3_controller interaction profile to run with SteamVR Runtime on VBS and Focus 3. Uncheck Compatibility mode in Settings > Input > Controller to enable.
- Provides OpenXR API layer register in Settings > Advanced.
Can you clarify what this means for practical use? If I enable OpenXR extensions for VBS, and also disable the "Compatibility Mode" in the Input section, where will I see that effects of that? Any demos/examples you might recommend?
-
Supports OpenXR vive_focus3_controller profile.
-
Also a side note - Firefox Reality seems to not want to uninstall from my headset right now. I don't know if it's flagged as a required system app of some sort, but going into settings and Storage and telling it remove the app there behaved as though it was being uninstalled, but back on the home screen it was still there and still opened up.
-
Just to circle back here in case anyone else has been watching this - VIVE Browser is now supported on the Focus 3, at least on my headset on the "Beta" branch. The performance feels about the same as the old Firefox Reality for now, but hey I'll take it...baby steps toward a fully supported, WebXR compliant browser with enhancements for VIVE products is fine by me as long as it's getting updated regularly. I do hope the team considers making it an open source project on GitHub so people can more directly contribute and follow its development.
https://business.vive.com/appstore/detail/bf2e75be-ff15-4349-8efc-45a16be03ab0
Also please VIVE team, please let us install directly from the headset some day? 🙂 I think I had to 2-factor 4 or 5 times back and forth, from trying on phone, which was blocked no matter what I tried due to cookie requirements, to then PC, to then back to the headset which had decided to log me out again. It is not the most user friendly process, Business focus or not.
-
*Celebration sounds* 🙂 Congrats to the team on officially launching OpenXR support for the Focus 3! Great step for the headset and for OpenXR in general.
-
I may be incorrect here, but you'll likely need to wait until VIVE releases their "VIVE Browser" since Firefox is the only web browser on the Focus 3 at the moment and it's horribly outdated in terms of WebXR support. You might be able to get something very basic to work, but to do what you're talking about I would think the app would need the browser's web framework available (and current) for it to work well. We know VIVE Browser is already available on the Focus, Focus Plus, and Flow, but it appears to still be in development for the Focus 3.
-
Just a heads up on a potential issue with this release. Yesterday and today, so 5 or 6 times total, I've gone into the settings for VBS, changed the Streaming graphics preferences, Sharpening, Streaming bitrate, and Dynamic then restarted the app. The Sharpening and Streaming bitrate settings changed from what I had just entered. I just reset them again, re-opened and this time the Sharpening was all the way down. Something confusing is going on.
Wait...idea! Does enabling "Dynamic bitrate" disable the streaming bitrate and Sharpening settings somehow? If so that might need some clarification (or graying out the bitrate slider completely when dynamic is enabled?) Either way the settings are seeming erratic right now from the user point of view. Performance has been very good overall though.
Edit: Nope, just tried tweaking things a bit more, and even with Dynamic Bitrate disabled, then closing everything and restarting VBS, the streaming bitrate setting is all the way back down to 20 Mbps again (at the bottom.) So something is not right with this.
-
Hah that's almost exactly the settings I used last night! 🙂 Except for the Dynamic Bitrates, I'll have to try that. I had probably the BEST session of Racket NX I've had in long while, everything really looked and played great.
-
Looks like a great update! You mentioned in the other post that the update too for the client needs to be applied through the console via USB. Is that going to be the new normal now, or is that strictly a one-time thing due to it being a larger change?
Also I'm just curious, my setup is about as ideal as one could imagine now minus possibly me having a beefier graphics card (I'm on a RTX 2080.) If you had a solid 2500 Mbps Wifi 6E connection in the same room, would you personally set the VBS settings to 200 Mbps and "Quality" stream settings, or would you leave things at "Auto" and just let things shift dynamically? I'm trying to get to the point where I never have used a wired connection again with equal quality. 🙂
-
Looks like we got a 1.08.2 BETA version over the weekend. I don't know if it's related yet, but I was playing some SteamVR games tonight and twice had compression degradation to the point where I had to stop playing, stop VBS on my PC, restart VBS, and everything looked good again. The image appeared differently than just a blurrier downscaling, it was more blocky like compression artifacts. I don't know if my headset updated the VBS client though (didn't see an update available) so could just be a version mismatch problem too. I tend to leave the settings at "Quality" and 150 Mbps, as I'm running over a Wifi 6E connection in the same room, so it's usually very quick and solid.
-
On 6/8/2022 at 11:06 PM, VRS3DGuru said:
Is this thread still alive? Testing with OpenXR 0.8.0 Preview hasn't seen any updates in a while.
2019.3.4, 2020.x etc isn't of much value here for various reasons per our projects.
Testing against 2021.3.4LTS updated packages and 2022.1.4f1TS updated packages producing same results -
Results:
Built in RP and URP both build and run fine arm64
Head Tracking works.
Left Controller tracking works. Trackpad works, trackpad button works. Grip value and button works. Trigger does not work. X button works, Y button does not work, Menu button is mis-reported.
Right controller tracks but device anchors are way off. No buttons work.
Tried both action and reference based configurations, added openXR ref to AndroidManifest and tried both unity.XR and waveXR libopenxc_loader.so files. Have verified plugin config in player settings.....
Ideas of what I may be doing wrong here?
I would take a look here if you haven't, but it sounds like you're pretty far past the intro basics. 🙂
-
On 5/7/2022 at 2:43 PM, Tausendberg said:
HTC, I have a crazy suggestion, but please hear me out...
What if VBS had an Oculus Quest 2 controller emulation mode?
I don't know how complicated it would be to program something like this but pretty much every steamvr game supports Oculus Quest 2 and so if there was a relatively simple way for SteamVR to just interpret all the joystick, button, trigger, and grip messages as the same messages from the Quest 2 controllers, which it seems like that could be pretty 1 to 1, this way you could guarantee compatibility pretty much forever.I hate it, but that probably would resolve 99% of the compatibility issues...
-
On 5/9/2022 at 7:53 PM, C.T. said:
Can you send me your SN via vive_ct@htc.com? I need to move you to public release, we have stopped the OpenXR alpha release a few weeks before.
You will still be able to use openXR environment when you are back to public release, just need to toggle beta feature there after.Sending email now, thanks CT
-
1
-
-
I'm on the FOTA release - openXR, version 4.0.999.8. Would that include all of those fixes and improvements?
Also do we know what the current status is for screen capture on these releases? I think I lost the ability to screen record entirely on 4.0.999.8.
-
So this popped up today... https://www.viveport.com/bf2e75be-ff15-4349-8efc-45a16be03ab0
And the response via Twitter, "VIVE Browser was created because the Firefox Reality is being removed from stores, this initial VIVE Browser is intended to give you the immersive browser and bring the basic browser you know and love into VR - it is compatible with VIVE products."
But I'm not seeing "VIVE Browser" available for the Focus 3 at all. Am I missing something?
I also asked on Twitter if it's Chromium based or something VIVE has been working on for their version of Firefox Reality/Wolvic? I'd really be nice to get some clear technical information on this - browsers for WebXR are so stuck right now with Chromium and I've given up on WebXR on the Focus 3 for now.
-
I know you guys keep saying it's an Enterprise Product, but there are a few of us at least who consider it more to be the best wireless "Pro" headset on the market...so we'll keep pushing on the game devs to get proper support! 🙂
-
The Focus 3 is essentially my ideal headset at this point. I've realized I want options. Standalone mobile chipset performance AND the ability to do PC VR. I had all of the Oculus headsets up to the Quest, and then got fed up with Facebook and I'm avoiding all Meta products from now on. I also have a HP Reverb G2, but I use it far less often now. For me to upgrade from the Focus 3 I would want...
1. Lighter headset. Always lighter.
2. Improvements to wireless latency - DisplayPort would be a great option too for a true, full resolution wired experience, but I'm trying to do everything wireless now
3. Better lenses. Going from the Focus 3 to the HP Reverb G2, the lens flare on the Focus 3 is extra apparent and the clarity is just not as good.
4. Passive cooling would be wonderful - but for the current state of VR, I'm OK with the front fan.
5. Improved audio - The speakers on the Valve Index and Reverb G2 are just so much better, I wish they would be a standard feature at this point for all headsets. The integrated audio right now is fine though if I had to choose that or having to wear other headphones.
6. Longer battery life - of course. 🙂
7. Integrated eye and mouth tracking - pretty clear this is going to become standard in the next gen or two to give improved presence, but I want assurances that raw data is staying mostly in headset.
For the most part then, I'd be looking for refinements more than substantial changes. It's a very good headset overall and hopefully as new processors come out, and better display technologies arrive, this feels like the true version 1.0 HTC has been shooting for. Hopefully the next one will deliver overall improvements and we'll see them compete in the consumer space too vs Meta Cambria.-
1
-
-
Looks like some of the improvements are working well...just had one of the best fully wireless sessions of Eleven Table Tennis and Beat Saber that I've ever had on the headset. I did have a few audio dropouts (for only a second or so, nothing horrible) and I do still get a slight bit of choppiness when moving physically forward or side to side along the horizontal plane. Improvements there would be welcome if possible, but it's certainly better...in Eleven Table Tennis for example I use to almost fully freeze for a moment if I had to lean forward or step back away from the table. That doesn't happen much at all now.
-
1
-
-
People don't give it enough credit - I've got to play a bunch of VR games I would have never otherwise tried had it not been for Infinity. I'd still like to see official Focus 3 support in there (blah blah blah, business headset, we know HTC) but as a SteamVR headset it's been great for a full wireless experience. I haven't had a chance to try Wanderer, I will give it a look!
-
On 3/20/2022 at 9:08 PM, C.T. said:
You will be able to see 6GHz here if you are in the regions that opens 6E connection.
Due to various local regulations, you have to connect to 2.4GHz or 5GHz first before you can see the 6GHz, but once it is opened, it will always be there unless you did the factory reset.
Thanks again CT. 🙂 I've had interesting discussions with ASUS also...turns out their "Tri-Band Smart Connect" that is advertised to allow a single SSID with 2.4, 5, and 6 GHz to behave as one network....does not actually work right now! The Smart Connect steering only has settings for 2.4 and 5 GHz, so I'm trying to get an answer about it eventually negotiating...smartly...between all 3 bands. I don't know if there's something can be done on the headset to let a user prioritize certain networks over others, but that might be a helpful feature. Then I could add profiles for the 6E only SSID, and for the main 2.4/5 SSID, and then the headset could gracefully switch to the Wifi 5/6 SSID when the 6E one is out of range. It seems pretty manual right now. It would also be great to see some more detailed network information in the headset. I'm pretty much having to open VBS to see what connect rate I'm getting - having that info and other network connection details in settings would be most helpful.
-
On 3/20/2022 at 8:05 PM, C.T. said:
If I read it right, you would like a gesture that can get you back to the VBS connection page where you can choose the server to connect to?
No sorry, it sounds like the right hand palm facing you "OK" gesture to take you back to the main menu is what I'm looking for - I just haven't been able to get it to trigger from the VBS connection page, so that I can go back to the home menu from VBS while inside the headset. Basically I'm just hoping to see the hand tracking overall user experience to "flow" a little better, so that a user is never stuck inside an app and can always get home. Firefox Reality for example, too. Hopefully once you're all moved over to Wolvic it'll get hand support also.
-
On 3/17/2022 at 9:51 PM, niil said:
My router does not support 6GHz, only 2.4 and 5. Wifi6 is based on 5GHz and Wifi 6e is based on 6GHz. Wifi 6e is not currently allowed in my country, so there are no such routers for sale. And those that are on sale in the secondary market have a price of 2 times their official value.
Ah good to know, thank you for the clarification. I've been looking around and also haven't been able to find specifics on the Wifi 6 channel support either, interesting. FWIW when not using the 6 GHz channels, I'm seeing occasional connections from 700Mb-1000 Mb/s, and 1200Mb/s at peak (which matches the max 802.11ax rates my router supports on those frequencies: WiFi 6 (802.11ax) (5GHz) : up to 1201 Mbps
This may not help you either niil but I found this in a recent press release in regards to 6E, I don't know if that informs what the Wifi 6 spectrum might be too: "With up to 1.2 GHz frequency range, it is also able to accommodate more than double the number of devices with their own dedicated channels* – for a numbers comparison, going from WiFi 6 (5GHz) to WiFi 6E is going from 25 to 59 separate 20MHz channels or 2 to 7 separate 160 MHz channels."
Something interesting I did find on 6 Ghz connections while trying to locate more info.... "Before VIVE Focus 3 can detect 6 GHz wireless networks, you need to connect the headset to a 2.4 GHz or 5 GHz network first. You can then scan for 6 GHz networks to connect to." Does anyone on the HTC know why this would be? I've been working with ASUS the past few days to understand why their "Smart Connect" feature doesn't allow a single 2.4/5/6 GHz SSID when they have a feature called "Tri-Band Smart Connect" that sounds like it should do just that.
-
On 3/15/2022 at 8:25 AM, crapshot.ai said:
OK, they seem to plan something then. I also asked them directly via email and got the following reply "Wolvic doesn't support any HTC devices officially yet. We are working currently on trying to close partnerships for 2022-2023 and will release a public roadmap and FAQ with some clarifications about this topic soon. We of course would like to officially suport the Vive Focus 3 headset, but for now we cannot confirm when/if this will happen." So maybe we will see something in the near future. ... I have just order 10 Focus 3 headsets ... in the worst case we have to stick with some commerical content like Vive Sync or get something unity-based running as an app. If you hear anything, I would really appreciate any news regarding this issue.Cheers, Uli
If you're open/able to go with other app based content also (not sure what specifically you're doing of course) I would check out StereoKit. I've been following along with the project for a good while and testing and experimenting with the Focus 3 when I can, and if you have people on your team with OpenXR/C# experience it's pretty straight-forward to make simple VR apps. All depends on your needs tho of course, Unity/Unreal might be better.
VIVE Focus 3 - Vive Business Streaming - "OpenXR - Vive OpenXR - Register to enable OpenXR extensions for VBS"
in VIVE OpenXR
Posted
Ah that makes sense on the facial tracking extension, thank you for clarifying that!
On the 90-degree rotation of the hand tracking, as far as I'm aware it's fully OpenXR, not OpenVR. I don't know if it'd be helpful but you can see more about StereoKit here if you're not familar with it: https://stereokit.net/
I've compiled Android native simple apps like this previously for the headset, and those seemed to work fine, but this is specifically when using SteamVR and streaming to the headset. I know the Focus 3 does have some settings between it and SteamVR that seems to do some sort of controller emulation rather than polling the actual hand tracking data, so I'm curious if that is somehow getting in the way. I've tried disabling "Compatibility Mode" in VIVE Business Streaming and only leaving "Hand Tracking" enabled, but the results are the same.
I'll do a bit more testing again tomorrow and see if I can find any more detailed information, but if you have other ideas I'm open to experiment. 🙂