Dash
- From the Dash Settings panel, you can now set your Passthrough+ session length to “unlimited,” which will allow you to see your real-world environment while using Dash.
- Guardian setup will now attempt to automatically detect the floor height for you. You can still manually adjust the height if needed.
- When using the virtual desktop feature in Dash, the virtual keyboard will now automatically open when you select a text field.
Oculus Home
- Your Home UI now includes a history of the Homes you’ve visited in the Places UI section. Homes you’ve visited in the last 30 days can be visited again with a quick button press. You can clear out your history or opt out entirely in the Settings UI.
- Never miss a Home reward pack again! Updated notifications now let you know when you have a reward ready to open. Also, notifications in Home have been redesigned to make things easier to read and understand.
- Now you can use Home gateways to load directly into your favorite app. In addition to setting up destination gateways to your own home and your friends' homes, you can now set up an app as a destination and use it as a simple and quick way to get into your favorite experiences.
- Home now features a camera, accessible straight from the Home Menu. Look on the bottom for the camera icon, and open the camera to capture your favorite moments in your Homes or Homes you're visiting. Take selfies, or screenshots, and find these images in your Documents/OculusHome/Camera folder.
Touch Controllers
We’ve made performance improvements to better track your Touch controller movements in VR. These updates, which are also applicable for Oculus Quest, include:
- Improved tracking when controllers are close to the headset, and at angles turned away from the headset.
- Improved tracking in difficult poses such as under-hand throwing motion.
- Reduced re-acquisition time when controller tracking is lost.
- You can now use both of your Touch controllers at the same time when interacting with different elements like the keyboard, Oculus Store, and Library.
Fixes
- Fixed an issue where Dash could crash if you had non-ASCII characters in your username.
As always, if you encounter any issues with this software release, please be sure to report them using the Help Center > Provide Feedback option within the Oculus desktop software. If you have any feature requests or suggestions to make the Oculus software even better, please head over to
our UserVoice page to share your feedback. Thanks for your continued help!
Comments
Dear Oculus, "If it ain't broke, don't fix it", please.
Custom built gaming desktop; i9 9900k (water cooled) oc to 5ghz, gtx 1080 ti, 32 gb 3000hz ram, 1 tb ssd, 4 tb hdd. Asus ROG Maximus xi hero wifi mb, StarTech 4 port/4 controller sata powered usb3.0 pcie card, PCI-E PCI Express to USB 3.1 Gen 2 card, Asus VG248QE 1080p 144hz gaming monitor, Oculus Rift cv1 w/2x sensors, Vive Pro w/2.0 base stations/Index controllers, Quest 1 w/Link and VD wireless (good/close 5Ghz wifi and PC with Ethernet cable to my Router).
But it's posted in Rift S and Rift, not Quest.
Dear Oculus, "If it ain't broke, don't fix it", please.
Custom built gaming desktop; i9 9900k (water cooled) oc to 5ghz, gtx 1080 ti, 32 gb 3000hz ram, 1 tb ssd, 4 tb hdd. Asus ROG Maximus xi hero wifi mb, StarTech 4 port/4 controller sata powered usb3.0 pcie card, PCI-E PCI Express to USB 3.1 Gen 2 card, Asus VG248QE 1080p 144hz gaming monitor, Oculus Rift cv1 w/2x sensors, Vive Pro w/2.0 base stations/Index controllers, Quest 1 w/Link and VD wireless (good/close 5Ghz wifi and PC with Ethernet cable to my Router).
With 1.39.0.272909, Static Flash Is Gone. Finally. Good Job Oculus. (This kind of bug should not be released to customer in the beginning though, lol)
Still got:
1. Buzzy microphone noise. This happens randomly, but once it happens it will keep happen every few seconds, which makes social games like VRChat unplayable. Some people says this is because of extension cable, but I directly plug USB to a USB 3.0 port on motherboard. And this was not happening before 1.39 PTC second update (1.39.0.268010).
(I saw signal analyze on Reddit says Rift S compress voice very hard. Is the noise also a compression problem?)
2. Black Screen. This used to happen in 1.38, but in first 1.39 PTC update, this problem was gone. In the second update of 1.39 PTC (1.39.0.268010), the problem come back and happens very frequently. Usually it happens after I restart Oculus Service for fixing other bugs.
3. Controller drifting. Somehow controller just drifting suddenly, and automatically return to normal in several seconds. This also brings by 1.39.0.268010, not happening in 1.38 or the first version of 1.39PTC.
Previous post:
I did not get any notification for update, is that means the 1.39 Release is the same as 1.39.0.268010 PTC?
Please no, the 1.39.0.268010 is very buggy. All of static flashes, black screen this kind of bugs remains; the controller tracking improvement of the first 1.39 PTC version was downgraded; and brings new bugs, such as USB warning, microphone noise problems and controller drifting problems.
Please tell me that Oculus will not use this buggy version as release version.
Or maybe Oculus just want to use the bugs to annoy users, for fun?
History repeats itself. The bugs are never fixed before the release goes public.
Dear Oculus, "If it ain't broke, don't fix it", please.
I have not necessarily noticed a degradation of tracking in latest 1.39, but may be due to the type of games I play.
USB warning - agree they really need to get that fixed, especially for new users that may not be aware it means nothing.
Black screens, in my case I finally found after much troubleshooting if I disabled my secondary monitor and only have monitor 1 running during Rift S use, I do not get them. I am probably in the minority on this, so other causes I am sure exist.
I would certainly like to be able to run both monitors while in VR like I could with Rift CV1. Hopefully the info they get from users who do use the submit feedback feature will help.
EVGA Z390 Dark MB | I9 9900k| EVGA 3090 FTW3 Ultra |32 GB G Skill 3200 cl14 ram | Warthog Throttle | VKB Gunfighter Pro/MCG Pro grip | Crosswind Pedals | EVGA DG 87 Case| Rift S | Quest |
Alternatively you might can select the Public Test Channel in the Beta tab, and it might go ahead and download right away still.
EVGA Z390 Dark MB | I9 9900k| EVGA 3090 FTW3 Ultra |32 GB G Skill 3200 cl14 ram | Warthog Throttle | VKB Gunfighter Pro/MCG Pro grip | Crosswind Pedals | EVGA DG 87 Case| Rift S | Quest |
Custom built gaming desktop; i9 9900k (water cooled) oc to 5ghz, gtx 1080 ti, 32 gb 3000hz ram, 1 tb ssd, 4 tb hdd. Asus ROG Maximus xi hero wifi mb, StarTech 4 port/4 controller sata powered usb3.0 pcie card, PCI-E PCI Express to USB 3.1 Gen 2 card, Asus VG248QE 1080p 144hz gaming monitor, Oculus Rift cv1 w/2x sensors, Vive Pro w/2.0 base stations/Index controllers, Quest 1 w/Link and VD wireless (good/close 5Ghz wifi and PC with Ethernet cable to my Router).
My guess is the cable is to long as display port is rated at 3 meters and the cable is longer than that but who knows.
Games are literally impossible to play after this update. Any kind of haptic feedback or vibration causes the tracking to stop in any game that uses more than a tiny amount of haptic. I had reverted from PTC cause of these issues and upon updating today, I had hoped that this glaring issue would of been fixed before public release.
I have keep submitting logs and bug reports for several weeks, non of the bugs was fixed, and non of the bugs seems like going to be fixed.
And yes, for static flash Oculus have official announcement that they are NOT fixing it in 1.39, which is already more than 50 days after the problem was found.
Seems like they just ignoring the bug reports and let Oculus Support telling users that “We will fix it as soon as possible. ”, meanwhile redefining the word “soon”.
However, in the oculus software, its states that there is no sound ?? I'm at work at the moment, so haven't done much trouble shooting yet . . that's tonight's job i think.
Sorry guys i've only owned VR for about a month . . everything was going great until i updated, i'm wondering if anyone else has had this problem (Audio seems to be a bit of an issue it seems).
I thought I had latest but I didn't so I installed 1903 and I'm now waiting for 1.39 to make its rounds to me. Please enter in your search bar the word winver and the latest update version will appear.
It's strange, the update has given me a ghost controller as well, everything else checks out other than the oculus device tab says the headset has no audio . . Sigh . .
So, i'll be updating round the wrong way, Rift first then Windows. ha ha.
Thanks again for your input, i'll look forward to trying these things out when i get home . . If not i'll be sending my first ticket.
Loving VR so far though . . so lets hope we can get this fixed.