Rift S and Rift 1.39 PTC Release Notes — Oculus
New to the forums? Click here to read the "How To" Guide.

Developer? Click here to go to the Developer Forums.

Rift S and Rift 1.39 PTC Release Notes

OculusSupportOculusSupport Posts: 296 Oculus Staff
edited July 11 in Oculus Rift S and Rift

Dash

  • From the Dash Settings panel, you can now set your Passthrough session length to “unlimited,” which will make Passthrough visible 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.

Fixes

  • Fixed an issue where Dash could crash if you had non-Unicode characters in your username.

Note:

Update 7/11/19 - This issue has been resolved with the latest PTC update (1.39.0.268010).

There is currently a known issue with 1.39 PTC that prevents it from working properly on Windows 7/8. If you are on Windows 7/8, please do not opt into the PTC at this time. If you already received the PTC update and are experiencing issues on Windows 7/8, please use the Oculus installer and perform a repair install to go back to the 1.38 release.


«13456

Comments

  • OrkelOrkel Posts: 103
    Art3mis
    I guess the flash fixe comes as a firmware update later. Just the fact we can finally play FPS games without having the controllers glitch out near the headset makes this one of the better S updates so far imo.
  • kavangekavange Posts: 21
    Brain Burst
    There are obviously tracking improvements in this update but it isnt even mentioned in the notes. Very strange.
  • profanicusprofanicus Posts: 12
    NerveGear
    Are close-up tracking improvements also coming to Quest? :)
  • KrueschelKrueschel Posts: 5
    NerveGear
    While trying to calibrate the Guardian Setup a "Fatal dash error" eccoured.
    Cant finish the setup... great work
  • ivanbrazzaivanbrazza Posts: 2
    NerveGear
    This update brought back the issues with OVRService not starting again. It was fixed with 1.38 but after opting into the 1.39 PTC release it's happening again. After just closing the installer I can start OVRServer_x64.exe manually and it all works fine. Anyone else?
  • pcfarrarpcfarrar Posts: 21
    Brain Burst
    This update brought back the issues with OVRService not starting again. It was fixed with 1.38 but after opting into the 1.39 PTC release it's happening again. After just closing the installer I can start OVRServer_x64.exe manually and it all works fine. Anyone else?
    Yes same problem again, I copied the 1.37 version of OVRServiceLauncher.exe over the top of the new one and it's working for me now.
  • pcfarrarpcfarrar Posts: 21
    Brain Burst
    edited June 28
    Here's a link to the working OVRServiceLauncher.exe (1.38.1).

    https://www.dropbox.com/s/zisxcernv3y5c3a/OVRServiceLauncher.zip?dl=0

    When the update to 1.39 is installing at the end (final stage) you need to navigate to C:\Program Files\Oculus\Support\oculus-runtime

    Copy the 1.38.1 OVRServiceLauncher.exe over the top of the new 1.39 one and then manually start the Oculus VR Runtime Service in Windows Services, the install will then complete and your back in business.
  • ivanbrazzaivanbrazza Posts: 2
    NerveGear
    pcfarrar said:
    Here's a link to the working OVRServiceLauncher.exe (1.38.1).

    https://www.dropbox.com/s/zisxcernv3y5c3a/OVRServiceLauncher.zip?dl=0

    When the update to 1.39 is installing at the end (final stage) you need to navigate to C:\Program Files\Oculus\Support\oculus-runtime

    Copy the 1.38.1 OVRServiceLauncher.exe over the top of the new 1.39 one and then manually start the Oculus VR Runtime Service in Windows Services, the install will then complete and your back in business.
    Awesome that worked perfectly - thanks!
  • V12-StevenXV12-StevenX Posts: 25
    Brain Burst
    pcfarrar said:
    Here's a link to the working OVRServiceLauncher.exe (1.38.1).

    https://www.dropbox.com/s/zisxcernv3y5c3a/OVRServiceLauncher.zip?dl=0

    When the update to 1.39 is installing at the end (final stage) you need to navigate to C:\Program Files\Oculus\Support\oculus-runtime

    Copy the 1.38.1 OVRServiceLauncher.exe over the top of the new 1.39 one and then manually start the Oculus VR Runtime Service in Windows Services, the install will then complete and your back in business.
    Mhhh...that's incredible! ... Another time with this issue  :o
  • RahotepRahotep Posts: 51
    Brain Burst
    Unable to play first person shooter on Rift S - no word if this is fixed ...
  • dburnedburne Posts: 2,408 Valuable Player
    edited June 28
    It would be nice if the Rift S Touch controllers would turn off when not in use and PC still powered up. For me as long as PC is powered on, even with Oculus Home closed, they only go into standby ( white flashing light). I was going through a set of batteries once a week with moderate use. Now I take the batteries out when not using Rift S and PC powered on, and have gone 10 days now and they are still showing a full charge. I am a little concerned though on wear and tear of those contact points for the batteries in the controllers.

    I did notice improved tracking with the Rift S controllers in 1.39 when near my head, so that is certainly nice.
    Don

    EVGA Z390 Dark MB | I9 9900k| EVGA 2080Ti FTW3 Ultra |32 GB G Skill 3200 cl14 ram | Warthog Throttle | VKB Gunfighter Pro/MCG Pro grip | Crosswind Pedals | EVGA DG 87 Case|
  • ShocksOculusShocksOculus Posts: 376
    Trinity
    edited June 28
    1.39 is working great for me thus far (Win 10, no Service.exe issues).

    I will say the closeup tracking is another level of black magic (Carmack Magic ?).  The controllers now track when close enough to physically touch the hmd (like how?); crazy cool !!

    Thanks Oculus!
    i7-7700k, GTX 1080Ti (11G) || MSI B150m (1 USB controller) + Inateck 4-port USB to PCIe (2nd USB controller)
    Oculus Rift S
    Oculus GO
    Oculus RIFT - 3 sensor Room-scale
  • nalex66nalex66 Posts: 4,530 Volunteer Moderator
    I will say the closeup tracking is another level of black magic (Carmack Magic ?). 
    We call that "Carmagic."
    i7 5820K @ 4.25 GHz | EVGA GTX 1080 SC | Gigabyte GA-X99-UD4 | Corsair DDR4 3000 32 GB | Corsair HX 750W
    Corsair Hydro H100i | Samsung SSDs: 860 Evo 1 TB, 850 Evo 1 TB, 840 Evo 1 TB | Seagate BarraCuda HDD 3 TB
  • MaXKiLLzMaXKiLLz Posts: 18
    NerveGear
    If you play games such as Pavlov and Contractors, you need to update to 1.39 PTC right away.  Wow!
  • sraurasraura Posts: 447
    Trinity
    Note:

    There is currently a known issue with 1.39 PTC that prevents it from working properly on Windows 7/8. If you are on Windows 7/8, please do not opt into the PTC at this time. If you already received the PTC update and are experiencing issues on Windows 7/8, please use the Oculus installer and perform a repair install to go back to the 1.38 release.


    ...I do hope that not many cv1 users are on PTC channel, or this will turn ugly fast. I mean it doesn't help that you come to forums and read the fineprint after the damage is already done.
  • pcfarrarpcfarrar Posts: 21
    Brain Burst
    It’s not just Windows 7/8 it has issues with Windows 10 - 1903 too.
  • snowdogsnowdog Posts: 6,749 Valuable Player
    I don't have ANY sort of sympathy for ANYONE still using Windows 7.

    LOve the tracking close to the headset, I'm going to give In Death a spin later on tonight, and turn Realistic Bow back on again in Skyrim VR. I knew it wouldn't take Carmack long to sort something out, the man is a genius of the highest order.
    "This you have to understand. There's only one way to hurt a man who's lost everything. Give him back something broken."

    Thomas Covenant, Unbeliever
  • kavangekavange Posts: 21
    Brain Burst
    edited June 28
    pcfarrar said:
    It’s not just Windows 7/8 it has issues with Windows 10 - 1903 too.

    I have no issues on 1903. I feel there must be something else on your machines that causes your issues.
  • XeXXeX Posts: 19
    NerveGear
    Hope this fixes my 1.38 stuttering issues
  • sraurasraura Posts: 447
    Trinity
    From steam users 96% uses windows and from those around 24% are windows 7 computers... So would say that globally there are quite many windows 7's out there still and many are used for gaming too.
    Only reason why many are ditching it is the hardware support which is diminishing.
    As good news from steam stats - oculus rift seems to still be the most popular headset with 46% and vive is following behind with 41%. May not be the case after index, but for now...
  • pcfarrarpcfarrar Posts: 21
    Brain Burst
    kavange said:
    pcfarrar said:
    It’s not just Windows 7/8 it has issues with Windows 10 - 1903 too.

    I have no issues on 1903. I feel there must be something else on your machines that causes your issues.
    Yes there must be some specific configuration that is causing it, Oculus fixed it in 1.38.1 so they must be aware of the issue and it’s cause.
  • Digikid1Digikid1 Posts: 1,919 Valuable Player
    kavange said:
    pcfarrar said:
    It’s not just Windows 7/8 it has issues with Windows 10 - 1903 too.

    I have no issues on 1903. I feel there must be something else on your machines that causes your issues.
    Erm....no.  Look around the forums.


  • kavangekavange Posts: 21
    Brain Burst
    Digikid1 said:
    kavange said:
    pcfarrar said:
    It’s not just Windows 7/8 it has issues with Windows 10 - 1903 too.

    I have no issues on 1903. I feel there must be something else on your machines that causes your issues.
    Erm....no.  Look around the forums.



    What do you mean? Did you read what I said ? I have had 1903 since it was released, I dont have any of those issues described and I would bet most dont.
  • snowdogsnowdog Posts: 6,749 Valuable Player
    sraura said:
    From steam users 96% uses windows and from those around 24% are windows 7 computers... So would say that globally there are quite many windows 7's out there still and many are used for gaming too.
    Only reason why many are ditching it is the hardware support which is diminishing.
    As good news from steam stats - oculus rift seems to still be the most popular headset with 46% and vive is following behind with 41%. May not be the case after index, but for now...

    It'll still be the case after Index because of Valve's greedy price gouging. The Index will sell well at launch and probably continue to sell at a reasonable rate through the launch window but those sales will soon slow down. For what you get for your money (a 1600p headset and a 20% increase in FOV depending on the size and shape of your head and face) it's WAY overpriced.
    "This you have to understand. There's only one way to hurt a man who's lost everything. Give him back something broken."

    Thomas Covenant, Unbeliever
  • RattyUKRattyUK Posts: 732
    3Jane
    kavange said:
    Digikid1 said:
    kavange said:
    pcfarrar said:
    It’s not just Windows 7/8 it has issues with Windows 10 - 1903 too.

    I have no issues on 1903. I feel there must be something else on your machines that causes your issues.
    Erm....no.  Look around the forums.



    What do you mean? Did you read what I said ? I have had 1903 since it was released, I dont have any of those issues described and I would bet most dont.
    Thankfully you have no issues - read around and you will find others do, but don't worry your head about it :)
    PC info: AMD Ryzen 7 2700X, Asus ROG Crosshair VII Hero, 16GB Tforce Pro Dark DDR4 3200, Gigabyte GTX 1080, Samsung 870 Pro M.2, 2x 240GB SSD, 3TB WD Green HDD & 4 TB Seagate Barracuda HDD, Corsair Modular 750w PSU, custom watercooling loop. (Win 10 Pro & Opensuse Leap 15 Linux) 32" AOC 4K Monitor.

    Laptop: Aorus X5 V6-CF1 (I7-6820HK, GTX 1070, 2* 256GB M.2 NVME, 1TB 7200 HDD 3K screen)
  • ShocksOculusShocksOculus Posts: 376
    Trinity
    sraura said:
    From steam users 96% uses windows and from those around 24% are windows 7 computers... So would say that globally there are quite many windows 7's out there still and many are used for gaming too.
    Only reason why many are ditching it is the hardware support which is diminishing.
    As good news from steam stats - oculus rift seems to still be the most popular headset with 46% and vive is following behind with 41%. May not be the case after index, but for now...
    Ya, but 97.9% of Oculus Rift users are on Windows 10.

    Even before Oculus dropped Windows 7/8 support, the Win10 users was still above 95%.

    i7-7700k, GTX 1080Ti (11G) || MSI B150m (1 USB controller) + Inateck 4-port USB to PCIe (2nd USB controller)
    Oculus Rift S
    Oculus GO
    Oculus RIFT - 3 sensor Room-scale
  • ShocksOculusShocksOculus Posts: 376
    Trinity
    edited June 28
    Someone posted a video of the tracking improvements on Onward, looking really good!



    i7-7700k, GTX 1080Ti (11G) || MSI B150m (1 USB controller) + Inateck 4-port USB to PCIe (2nd USB controller)
    Oculus Rift S
    Oculus GO
    Oculus RIFT - 3 sensor Room-scale
  • kavangekavange Posts: 21
    Brain Burst
    RattyUK said:
    kavange said:
    Digikid1 said:
    kavange said:
    pcfarrar said:
    It’s not just Windows 7/8 it has issues with Windows 10 - 1903 too.

    I have no issues on 1903. I feel there must be something else on your machines that causes your issues.
    Erm....no.  Look around the forums.



    What do you mean? Did you read what I said ? I have had 1903 since it was released, I dont have any of those issues described and I would bet most dont.
    Thankfully you have no issues - read around and you will find others do, but don't worry your head about it :)


    Going around insinuating it's because of a windows update that is globally rolled out rather than some other stuff on your computer is just silly. There would be literally thousands of threads if that was the only issue.

Sign In or Register to comment.