Ixixly

It's a screen burn in issue, doesn't happen super often but does occasionally happen. I'll usually go away after a week.

Hey Guys, are there instructions on how to do the USB enrollment?

Sounds like you're angry at HTC for Virtual Desktop not having Hand Tracking built in so that you can use several different manufacturers/developers products altogether in a very niche way?

@C.T. are there patch notes for the latest 760 version please?

Ok, fixed it, leaving this up for prosperity sake incase others have the same issue. Needed to use AMD Adrenalin to update the iGPU drivers and this allowed VBS to pickup the 4090 properly, go figure!

Latest Nvidia Drivers are installed 527.56, also tried the main branch and beta branch for VBS with no success.

I tried disabling the iGPU to force it to use the 4090, now when I launch VBS it tells me "330 : Error: No supported GPU found", so confirmed it was trying to use the iGPU before and doesn't seem to recognise the 4090 at all. I tried uninstalling VBS and installing again after disabling the iGPU but no success there either.

So unsure when exactly this started but for some reason the Focus 3 and my 4090 are not working together, it seems to be trying to use the iGPU with my CPU which is absurb as that doesn't get used by anything else. PC Config as below: AMD Ryzen 5 7600x RTX 4090 Suprim Liquid X Aorus B650e Master Mobo 32GB DDR5 5600mhz Any suggestions on this? Yes, I've already tried changing the Nvidia Panel settings, it only gives an option to set the 4090 for OpenGL, doesn't even list the iGPU in here. When I run fpsVR it shows only 0.5gb of memory available for the GPU and absolutely nothing seems to run properly.

Oh yeah, way too plain!! You need to get some markings on the walls and floors if you want to get it working properly.

I see, then it could come down to your area that you are trying to use the Headsets in. As I understand, without a map that stores specific tracking points to reference the area needs to be very considerate towards tracking, it needs to have decent light levels and lots of unique tracking points. Could you include some photos of the area you're using it in?

EddyChan, can you confirm which colour the loading logo is? It's useful to know that White Loading Logo is for tracking whilst the blue is related to app loading. For example if you see the App Logo and a blue loading logo then it's something to do with the app hanging or not loading properly whilst white would mean it has lost tracking. If it is white then likely you're having tracking issues, have you tried using the Android App to do a map refinement to help give better tracking?

We've noticed this happen several times as well in a variety of titles, the controllers appear find in the SteamVR Overlay but are broken in the game and don't display properly even after a restart of the controllers which does indicate some kind of Device ID issue when re-establishing a connection. This is something that Vive need to work on to make sure it re-connects in the same way otherwise it requires the game/app to be exited and started again which is a pain for customers and operators alike.

Should only have the Vive button on the right controller disabled. Use the button on the side of the headset, hold down till you see a pop up and from here select "Exit Kiosk"

Agreed with Tausendberg, this is an enterprise oriented Headset, I'm having to go around and update 22 of them individually like this with a damned cable, not good enough.

With the arUCo symbols, the information I've seen has me under the impression that they are more Application specific rather than System specific, as in developers need to include support for them and for specific ones rather than being able to put them around an area for the Headset itself to recognise? Could you elaborate a bit more for us on this?