06-14-2019 12:26 PM
06-17-2019 10:14 AM
06-18-2019 05:31 AM
Due to the launch of the Rift S and Quest, we are
experiencing a higher ticket volume than normal. We will do our best to
get back to you within 3-4 business days, with more information or an
update.
06-18-2019 05:37 AM
WhiteZero said:
Update on my ticket from last night:Thank you very much for the log files. We're going to have to look into them further.Due to the launch of the Rift S and Quest, we are
experiencing a higher ticket volume than normal. We will do our best to
get back to you within 3-4 business days, with more information or an
update.
06-18-2019 05:38 AM
06-18-2019 06:23 AM
06-18-2019 07:46 AM
pcfarrar said:
V12-StevenX said:
So it's correct only to overwrite the 1.38 OVRServiceLauncher.exe.exe with the OVRServiceLauncher.exe 1.37?. Don't you need to launch oculus client right by hand subsequently, right? in this mode should work normally?. I also have this problem from 1.38 ... but I hope Oculus staff patch soon and answer on the forum about this problem.
pcfarrar said:
Was able to downgrade to 1.37.1 and I'm back up and running again. 1.38 is definitely bugged there was no way I could get the Oculus VR runtime service to start. I did wonder if replacing the 1.38 "OVRServiceLauncher.exe" with the 1.37.1 version would work but to be honest I don't want the hassle of reinstalling again.
That’s correct once you’ve overwritten the 1.38 OVRServiceLauncher.exe reboot and it will be fully working. Just put the headset on and it will fire up automatically.
06-18-2019 08:26 AM
pcfarrar said:
V12-StevenX said:
So it's correct only to overwrite the 1.38 OVRServiceLauncher.exe.exe with the OVRServiceLauncher.exe 1.37?. Don't you need to launch oculus client right by hand subsequently, right? in this mode should work normally?. I also have this problem from 1.38 ... but I hope Oculus staff patch soon and answer on the forum about this problem.
pcfarrar said:
Was able to downgrade to 1.37.1 and I'm back up and running again. 1.38 is definitely bugged there was no way I could get the Oculus VR runtime service to start. I did wonder if replacing the 1.38 "OVRServiceLauncher.exe" with the 1.37.1 version would work but to be honest I don't want the hassle of reinstalling again.
That’s correct once you’ve overwritten the 1.38 OVRServiceLauncher.exe reboot and it will be fully working. Just put the headset on and it will fire up automatically.
06-18-2019 09:47 AM
I have found a fix.
MrSheppard said:
My Rift S functioned fine until last night where the 1.38 Update was downloaded.
Today, i only get "Can’t Reach Oculus Runtime" message with the suggestion to restart my PC or try repairing the installation.
So i went and tried the repairing process. After it was done, the headset worked again.
The next day, the Oculus software automatically started the 1.38 update.
After this update the same message mentioned above showed up again.
I suspect this update broke the RuntimeVR service which can not start anymore.
I hope i can get some help.WhiteZero said:
Update on my ticket from last night:Thank you very much for the log files. We're going to have to look into them further.Due to the launch of the Rift S and Quest, we are
experiencing a higher ticket volume than normal. We will do our best to
get back to you within 3-4 business days, with more information or an
update.
06-18-2019 10:17 AM
06-18-2019 11:20 AM
MAC_MAN86 said:
Thanks.
A note on REDIST & Oculus...there are common Games that use C++2013 which the Updater always needs to check for after any update even though it is already installed, it still does the checks.
Yes 2015, 2017 & 2019 all use the same files but they each remove the previous version in doing so but Oculus uses 2015 (or did). So it has in the past and perhaps still does gets stuck in a loop!
Even now Oculus does not install C++2019
One thing that causes Loops is probably Windows Folder Permissions which is common if you do use any OS Folder for either APP or Games so don't! If you do and even make a new folder elsewhere you should "Share" it with "Everybody" (basic dropdown menu) in Properties just in case you do need another User Account for future fixes too.