copelandmaster

This is posted in the Focus 3 subcategory of the VIVE Technical Support sub forum of the VIVE Community forum. Welcome to niche street, in niche city, in niche county, in niche state, in niche country, on niche planet. I'll be your guide to requesting basic functionality for our face brick portals to digital alternative dimensions. The Focus 3 has had its Eye and Face tracker out since last October. VRCFT also reached version V5 in April. Again, it won't matter when the VIVE Self Trackers and the Eye and Face Tracker for the XR Elite come out later this year. A huge chunk of standalone use is for PCVR, and PCVR use is a major feature for both the Focus 3 and XR Elite. PCVR means loads of control schemes and freedom of use and expression. Here's a nice link on HTC's website championing features like PC VR use and Space Calibrator, which allows business to continue to use the Steam VR equipment they already bought from HTC. https://blog.vive.com/us/introducing-new-features-vive-focus-3/ Even if the camera tracked products and lighthouse products cannot talk directly to each other, they should at least get out of one another's way. HTC sells ALL of them don't they? Not only that, but upcoming commercial products like the Diver-X contact glove are going to support both the Steam VR tracking AND the VIVE Self Tracker while most likely still emulating the Index control/finger tracking software. https://www.kickstarter.com/projects/diver-x/contact-glove/posts/3777038 That, and Steam VR by itself does not care whether or not you have any controllers turned on. That's HTC VIVE, VIVE Pro, VIVE Cosmos w/ Steam VR tracker (?), VIVE Pro 2, and Index users without a problem. Possibly Pimax users as well, other than all their other problems. If I had any experience with Oculus or WMR products, I might be able to list them too.

Thanks for the tip for VBS, but having to sign back into my account for license verification every time I use it is like pulling teeth. Crossed my fingers that it would work in VD, but of course you're auto kicked from the app on restart and you're still locked out of the app due to the no hand tracking thing. XR Elite probably doesn't have a kiosk mode. That's a wild, aggravating hoop HTC...

A helpful video to illustrate the problem. https://www.youtube.com/watch?v=vqPBG5oQUoM

Its been almost 2 years. Hand tracking support in VBS mitigated the problem, but now its impassible if I want to use the $20 Virtual Desktop app that does not support hand tracking. Asking users to stash the Focus 3 controllers inside their playspace and not trip over them is too much. VD can disallow their input into Steam VR, but the headset boundary can still see them. This causes performance problems in games and both VBS and VD. HTC, you made a big deal out of the VIVE Self Trackers not to long ago, so you know that FBT and Index Controller use with your hardware (and Meta hardware) is lucrative. And yet, when those people buy the Self Trackers for like $200 - $2000 total and try to use them with older lighthouse hardware, they are going to get a huge dose of the pain I've been experiencing for YEARS at this point. Now, extrapolate my frustration to people looking at the XR Elite, especially when its Face+Eye Tracker comes out. Do you even subject XR Elite users to this difficulty? Let me turn my Focus 3 controllers off and not be bothered by the nagging OS anymore. Also, I'm still mad about Space Calibrator 2.0 straight up not existing no matter how many times you contact HTC's reps.

Coming back to ask this question again, as Shen Ye himself brought up "foveated compression" in a Tested interview about the XR Elite: https://youtu.be/almTJ6qv9Uc?t=2007 He says this is something that the Focus 3 already does, but does that mean in a developer prototyping sanbox or an actual end user feature that can be turned on in VBS/the HMD OS? I upgraded to the 4070 Ti since the last post, and while the dual encoder handles Ultra with 30-50% usage just fine/much better than the 3080, any performance that could be won back system wide through the chain would be greatly appreciated. Especially in ridiculously in heavy games like VR Chat. I was considering the eye tracker over the holiday, but was holding out on information regarding the XR Elite (and other HMDs like the Pimax Crystal and Somnium VR1. Pimax is doing "foveated transport"/"DFR" and the Somnium is somehow using it for the 4k passthrough cameras). The XR Elite doing eye tracked "foveated compresssion" as a casually mentioned feature by the GHoP for an unreleased add-on while the Focus 3 being ???-status after having its add-ons available since last October is something that should be cleared up.

I supposed the latest VBS thread is the appropriate place to ask this: does the VIVE Focus 3 Eye Tracker support eye tracked foveated rendering via VBS into (any) Steam VR PC VR titles using an NVIDIA RTX GPU? Would the function that controls this/turns it on or off be handled by the headset OS settings, VBS PC side, by SRanipal, something in the NVIDIA Control panel or software suite on their extensive website, or by some .exe that you have to search a Github project for? And I mean by an end user for a game/experience, not a developer plugin for a game engine or an SDK.

I'd like to report similar performance in Pavlov and Beat Saber. 5800X3D, RTX 3080, Asus GT-AXE16000 in both 5GHz and 6GHz (I'll test my GT-AXE11000 later). It's still really cool that there appears to be a whole bunch of headroom headset side. If it really is a GPU encoder deficiency, I'm now curious if there will be a 2 slot RTX 4070 Ti FE with the same encoder as the 4080/4090. That, and if HTC's new "Flowcus" headset has the same or better headroom... I'd like to suggest an 'Extreme Quality' setting, say 2.5k x 2.5k@90hz. How about introducing 120hz Balanced or 120hz Quality modes?

Just to be clear, games with existing VIVE Pro Eye+FT support still have to be patched/updated on the developer side before Eye and Face tracking will work on a Focus 3, correct?

I don't want to get banned for spam, but because this thread is active, I'd like to repeat my request for access to Space Calibrator 2. Original post: https://forum.htc.com/topic/13694-vive-focus-3-software-50999514-–-release-notes/?do=findComment&comment=48592 Sorry, I also used the Vive support request bar on the page header of the thread on Monday but have received no response.

I've just found this thread and would like to have the Space Calibrator 2.0 installation file. Or should we contact Vive Sales and fill out a form? Should we uninstall 1.21 before installing 2.0? A question though: the update patch notes states: "This new version can allow trackers to work with multiple base stations and improve accuracy". This was the previous release, correct? Release v1.2.1 · MikeHYChao/OpenVR-SpaceCalibrator · GitHub I've been using a 3pt and 7pt Tundra tracker setup along with Vive wands/Index controllers for months with 4 Steam VR 2.0 base stations. What exactly was Space Calibrator/Steam VR doing beforehand? Using 2 only base stations? Or is this change only reflected in the setup/calibration process/accuracy? I've had my fair share of instability problems with trackers+controllers shooting everywhere or disappearing periodically. There are so many layers to everything involved in my setup: PCVR quirks, wireless streaming via VBS, Sensor Fusion discrepancies, Tundras being smaller than Vive pucks, Tundra dongles being heavy on USB, FPSvr and DecaMove program overhead, Ryzen system quirks, etc. I chalked it down to "that's just how things are". Will version 2 be released to Github eventually?

I own 6E router hardware, ASUS GT-AXE11000. Restarted my router multiple times yesterday to make sure everything was working properly. TL;DR feedback: this update is not very good. The speed should be 4800Mbps, right? I'm getting 2400Mbps, same as 5GHz. I would've figured the desktop app would get an update with higher bitrate+resolution support as well. Videos where I test Wifi 6 and 6E, timestamps in the description for the portions where I play on 6E. https://www.youtube.com/watch?v=_mD70xFdGWA https://www.youtube.com/watch?v=kD_Y3BsYuok I would like to emphasize that when I was not recording, 6E stability was significantly worse. I could not finish the song at all, maybe get halfway through if I was lucky. Crashes maxed out at Quality+100Mbps and even on Auto+70Mbps. Crashes all day yesterday. As far as I can tell, my problem is HMD side only. Does the device/wireless hardware run hotter internally under 6E vs 6? I can't tell. I sent a report earlier yesterday via the business streaming app.