Jump to content

jefmes

Verified Members
  • Posts

    79
  • Joined

  • Last visited

Reputation

13 Good

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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. 🙂
  2. 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?
  3. 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. Screenrecord_20221024_162210.mp4
  4. 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?
  5. 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.
  6. 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.
  7. *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.
  8. 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.
  9. 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.
  10. 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.
  11. 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. 🙂
  12. 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.
  13. I would take a look here if you haven't, but it sounds like you're pretty far past the intro basics. 🙂
  14. I hate it, but that probably would resolve 99% of the compatibility issues...
×
×
  • Create New...