The latest Rift system software v1.38 is beginning to roll out, and we wanted to take a moment to share an update on our development progress. This release contains a number of fixes for issues that some Rift S users reported, most notably a reduction in black screen occurrences and improvements to audio quality. Over the course of the 1.38 PTC, we released 3 additional stability updates to the software. These updates were directly informed by the feedback we received from the community members who opted into the PTC. Thank you so much for all your help, and please continue to utilize the Help Center > Provide Feedback option within the Oculus desktop software. Please note that 1.38 does not resolve all reported Rift S issues as some are still being investigated and debugged, including the white / static flashing issue and sporadic instances of tracking loss. Our team greatly appreciates your patience while we work on these outstanding issues. We will continue to share updates with the community as we have them. Thank you!
Oculus Home:
You can now rename your Homes! In the details page for any of your own Homes, there is now an edit icon next to the Home name that will bring up a VR keyboard. Express yourself with a brand new Home name that will be reflected in recommendations, gateways, and friends' Places lists.
We've made it easier to manage items. You can now easily relocate items directly from the inventory menu to move or reposition them. We've also reduced download sizes for faster item delivery.
We've polished up the presentation of Homes in our menus to be much faster and more intuitive.
Rift S:
Updated audio driver to improve Rift S audio quality.
Updated firmware to reduce occurrence of display issues.
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
Finger tracking was mentioned. They already did it with Leap Motion I think but here's an article on it without. Hey after 2yrs and there's still no STRAFE IN HOME!!! https://uploadvr.com/rift-s-finger-tracking-possible/
Anyone having the issue where the update is stuck at 51%? Seems to not advance even after leaving the desktop app running for hours. Cheers, AussieStig
Since version 1.38 I have problems viewing some objects in the room. To test, we were 3 to visit several room: 2 rift cv1 and 1 rift S. We compared what we see in the room.
Some objects appear without texture, so all white. Some objects were replaced by a red cube with inside a red circle with an exclamation point. Other objects that represent paintings or photos have become white or gray panels with no picture in them.
We compared, the 2 rift CV1 had the same vision of the objects described above, only the rift S saw the objects correctly.
MSI Z790 ACE, MSI RTX 4090 SUPRIM X, I7 14700K, Corsair Dominator Platinum DDR5 32 go, 2 x Samsung SSD 980 PRO M.2 PCIe NVMe 2 To
Just use their new download of setup and select REPAIR.
Ta mate, new download? Where can I find that? The CV1 is still working properly, so I am not really fussed tbh. Just annoying to have the blue dot on the Notifications tab. It seems odd that I would need to repair something that is working correctly though?
Well it is supposed to work as designed and just update. I tried your idea but not working.
You had a blackscreen issue too, right?
I reached a German Support after the Englisch one did not read what I write and just act like a bot (maybe it was a bot IDK), but the German Support was just,
"Hello Neona,
The following suggested solution may seem strange, but may resolve the problem: Please check if your Windows user name contains umlauts or special characters (ä, ö, ü, ß, é, etc.). If this is the case, please change the user name once or create a new user so that the user name does not contain any umlauts or special characters (or log in with an already existing user who does not contain any umlauts or special characters). Then test the Rift again. Please let us know shortly, if no image is displayed in the Rift. Yours sincerely, Stefan
Oculus support"
So yes, I createt a new User with the Name "HP", because my PC is from HP. (this PC is 10 years old with a i5-3350P, with originally one AMD/ATI Radeon 7570 HD which was replaced with a NVIDIA msi gtx 1050)
Now with the new user my Rift is working again without any problems.
so try it out maybe it's fix your problem too, if it still not fixed. ^ . ^
I finde it actuelly really funny that my real Name caused the Problem, which I could actuelly thing by myself because the Error's in the runtime showes me, that it's can't read the ö and ü! XD
p. s. I only remember that you have responded to my commend with blackscreen, and said that you have the same problem. so i just took a rendom commend from you to tell you this.
My PC name was "STUDIO" and changing that did not fix it. My issue was a corrupted files from all the trying out how to fix it in 1.37 until I needed to start a fresh OS. The Regscanner can help out but I broke other links by trying to also fix my onboard sound also. RIFT S got returned as a precaution so back on my CV1.
Well try your glb imports again on V1.38 - My preveous post got deleted, because i had put a link in to another thread in this forum. I think it may have triggered the Spam Filter... Hence why my link is dead... Saddly.
My PC name was "STUDIO" and changing that did not fix it. My issue was a corrupted files from all the trying out how to fix it in 1.37 until I needed to start a fresh OS. The Regscanner can help out but I broke other links by trying to also fix my onboard sound also. RIFT S got returned as a precaution so back on my CV1.
