cancel
Showing results for 
Search instead for 
Did you mean: 

Rift 1.38 Release Rolling Out Now

MetaQuestSupport
Community Manager
Community Manager
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!
258 REPLIES 258

Anonymous
Not applicable
Sooo, still no word from dev? Is the service just going to be broken forever, and we're going ot have this abortion of a work around as common practice now?


xSTONEMANx
Expert Protege
Just updated to 1.38 Everything seems to be running  Smooth. 4790k ASUS Z97 pro

lebar63
Honored Guest


After Oculus Update 1.38 my headset display black screen!
On Device Panel everything seems right.Windows Update OK, GPU driver update OK.
But in the headset there are black screen. What could be the problem and what is the solution


The same for me. did you find the solution ?

Anonymous
Not applicable
My Update took 10 to 15mins. 2days ago it took about 45min! Blackscreen and doesn't work except audio but it did that before the update and I think it's either a broken Oculus App from trying to fix an issue over the GPU Drivers OR it's broke. I really don't get why a Desktop seriously needs:
1. A really shit Audio Chip
2. A really shit Graphics Chip
Both of which are just shit and ruin what we want to do when using other superior Cards/Devices.
It's just shit. Windows also has so many shit things like that blurred Login and "Wait at LOGIN if Network is not found" (so waits literally forever!) as used for the loading of images which last 0.1secs on your STARTUP  LOGIN. Longer if you use the LOGIN for Awake but it's a blurred image now. It's just shit!

zkosn
Honored Guest
I have resolved two of the 3 main issues for me.   

Resolve might be a strong word since it's still not totally fixed, but it does survive reboots.

1. Finish the install (or presumably the repair, though I'm long past that). 
Thumbass's post above led me to search for Daybreak.Core.Smc+SmcException and this came up in 2017.
Follow CU_zachshaver's suggestion, which is creating a batch file to run while you're installing the Oculus software.  The basic command is (from admin prompt):  sc.exe config "OVRLibraryService" obj= "LocalSystem"  
The batch repeats it over and over until the Oculus setup gets to that point (progress bar right before Capital O).
The install finishes, praise be, under his eye.

The primary thing that seems to be fixed here is the OVRLibarary service will now start automatically.

2. After running OVRServer_x64.exe manually I have a lot of programs requiring redistributables.  
They are located in C:\Program Files\Oculus\Redistributables.    I believe they were downloaded, so I can't say what you have, nor say what you *should* run.  The ones for me that were already installed said so.   (For instance, I have every Visual C++ redist 32 bit and 64 bit since 2005.  Obviously every one of those is not needed on my 64 bit system.  They were already installed.  My feeling is that the openal installer was the trick for me.)    Make sure to restart OVRServer_x64.exe so it can load the manifests.

3.  OVRServer_x64.exe from the C:\Program Files\Oculus\Support\oculus-runtime  still doesn't run automatically.   Maybe someone can figure that out.   Running it (with it's console window open) manually brings everything back to "normal".     If you don't do this first, you'll get the dreaded Verifying App or Can't reach service.  Don't repair. Run OVRServer_x64.exe because that's what it's looking for.

Anonymous
Not applicable
Are you all seeing the same OVRService_x64 version as this long named one in Tasks>Processes?

ws6ykm21t7dq.png

thumbass
Explorer

zkosn said:

I have resolved two of the 3 main issues for me.   

Resolve might be a strong word since it's still not totally fixed, but it does survive reboots.

1. Finish the install (or presumably the repair, though I'm long past that). 
Thumbass's post above led me to search for Daybreak.Core.Smc+SmcException and this came up in 2017.
Follow CU_zachshaver's suggestion, which is creating a batch file to run while you're installing the Oculus software.  The basic command is (from admin prompt):  sc.exe config "OVRLibraryService" obj= "LocalSystem"  
The batch repeats it over and over until the Oculus setup gets to that point (progress bar right before Capital O).
The install finishes, praise be, under his eye.

The primary thing that seems to be fixed here is the OVRLibarary service will now start automatically.

2. After running OVRServer_x64.exe manually I have a lot of programs requiring redistributables.  
They are located in C:\Program Files\Oculus\Redistributables.    I believe they were downloaded, so I can't say what you have, nor say what you *should* run.  The ones for me that were already installed said so.   (For instance, I have every Visual C++ redist 32 bit and 64 bit since 2005.  Obviously every one of those is not needed on my 64 bit system.  They were already installed.  My feeling is that the openal installer was the trick for me.)    Make sure to restart OVRServer_x64.exe so it can load the manifests.

3.  OVRServer_x64.exe from the C:\Program Files\Oculus\Support\oculus-runtime  still doesn't run automatically.   Maybe someone can figure that out.   Running it (with it's console window open) manually brings everything back to "normal".     If you don't do this first, you'll get the dreaded Verifying App or Can't reach service.  Don't repair. Run OVRServer_x64.exe because that's what it's looking for.

I don't think that OVRServer_x64.exe normally runs when you open the Oculus home by default...We are running this, which allows Oculus home to work but if you look in services the Oculus runtime service isn't even running when OVRServer_x64.exe is running, allowing us to use the Oculus Home app.  

Richooal
Consultant

MAC_MAN86 said:

Are you all seeing the same OVRService_x64 version as this long named one in Tasks>Processes?

ws6ykm21t7dq.png



Yes, I have this background process too.
i5 6600k - GTX1060 - 8GB RAM - Rift CV1 + 3 Sensors - 1 minor problem
Dear Oculus, If it ain't broke, don't fix it, please.

Anonymous
Not applicable
Those 3 Processes always run which is normal. If your old RIFT were to start the APP at launch it's due to having the sensor pick up your VRCover which RIFT S hasn't got yet.
2 Services we should see are OVRService=Running & OVRLibraryService = Stopped. This is normal. If you have to manually Start the OVRService then you should look into reinstalling Oculus.

lieoyv
Honored Guest

lebar63 said:



After Oculus Update 1.38 my headset display black screen!
On Device Panel everything seems right.Windows Update OK, GPU driver update OK.
But in the headset there are black screen. What could be the problem and what is the solution


The same for me. did you find the solution ?


I'm also having this issue - bad firmware update for some Rift revisions?