cancel
Showing results for 
Search instead for 
Did you mean: 

Oculus Rift 1.13 Release Notes

cybereality
Level 15
  • Features:
    • Public Test Channel: You can now enroll in our Public Test Channel program to receive pre-release builds (“beta” versions) of Oculus software. Enroll in Settings > Beta in the Oculus app on your computer. Learn more in our help center (https://support.oculus.com/help/oculus/200468603765391).
    • New User Experience: Improved first experiences for Rift and Touch.
      • Touch Basics: You can now move forward simply by looking at the skip option, as an accessibility feature..
      • First Contact: We updated and enhanced the experience. Check it out for a few new surprises.
      • Minor bug fixes.
  • Bug-fixes:
    • Fixed an issue with your apparent height in VR.
    • Fixed a tracking issue to make headset tracking smoother.
    • Fixed an issue with showing the correct app in VR when running multiple apps at once on your computer.
AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
161 REPLIES 161

cybereality
Level 15
The debug tool should never launch by itself (it's not even part of the Oculus app but rather a separate SDK download for developers). If it is starting that probably means you've done some sort of configuration change on your computer, such as using third party apps to adjust pixel density or things like that.
AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV

xeno3d
Level 6


The debug tool should never launch by itself (it's not even part of the Oculus app but rather a separate SDK download for developers). If it is starting that probably means you've done some sort of configuration change on your computer, such as using third party apps to adjust pixel density or things like that.


That was it, I use Oculus Tray Tool and this was the culprit.  Thank you!

kojack
Volunteer Moderator
Volunteer Moderator
These rolling releases are rather annoying for developers.

We see here that 1.13 is breaking at least two programs (tray tool and debug tool). I'm a developer, but I'm stuck on 1.12 runtime and there's no 1.13 sdk out. But some members of the public are already running 1.13. If one of my apps was broken, there'd be nothing I could do besides wait.



Author: Oculus Monitor,  Auto Oculus Touch,  Forum Dark Mode, Phantom Touch Remover,  X-Plane Fixer
Hardware: Threadripper 1950x, MSI Gaming Trio 2080TI, Asrock X399 Taich
Headsets: Wrap 1200VR, DK1, DK2, CV1, Rift-S, GearVR, Go, Quest, Quest 2, Reverb G2

MikeF
Level 10

kojack said:

These rolling releases are rather annoying for developers.

We see here that 1.13 is breaking at least two programs (tray tool and debug tool). I'm a developer, but I'm stuck on 1.12 runtime and there's no 1.13 sdk out. But some members of the public are already running 1.13. If one of my apps was broken, there'd be nothing I could do besides wait.





you said it, in the same position

cybereality
Level 15

kojack said:

These rolling releases are rather annoying for developers.

We see here that 1.13 is breaking at least two programs (tray tool and debug tool). I'm a developer, but I'm stuck on 1.12 runtime and there's no 1.13 sdk out. But some members of the public are already running 1.13. If one of my apps was broken, there'd be nothing I could do besides wait.


It appears the OculusDebugTool from the 1.12 SDK is not compatible with the 1.13 runtime (and OculusTrayTool includes the older application in their package). This will likely be resolved when the upcoming 1.13 SDK is released in the near future. I spoke with the developer working on the OculusDebugTool and he was not aware (before today) that there were third party apps relying on this functionality. This should be resolved shortly, so I wouldn't worry about it too much.
AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV

danybonin
Level 4
no bad tracking news with 1.13? I fear update since 1.11 fiasco. 1.12 is very good for me with 4 sensors.
core i7 5930k @ 4.4ghz
nvidia rtx 2080 ti
16GB ram
asus pg27uq
oculus cv1 4 sensors on usb3 on 5 distinct usb controller

kojack
Volunteer Moderator
Volunteer Moderator
Yep, I know it won't be a problem for long (I would have run into it tonight though, since I only use the debug tool with Elite and a new community goal came out today) and it's a minor thing.

But it's still an odd situation where some of the public have a runtime before developers have the matching sdk and there's no control over which runtime developers run for testing (since every update there's half with new runtimes and half with old, and the devs can't choose which side they are on for bug fixing). Both sdk and runtime should really be released at the same time, and allow users to do an update or not when they choose.

Author: Oculus Monitor,  Auto Oculus Touch,  Forum Dark Mode, Phantom Touch Remover,  X-Plane Fixer
Hardware: Threadripper 1950x, MSI Gaming Trio 2080TI, Asrock X399 Taich
Headsets: Wrap 1200VR, DK1, DK2, CV1, Rift-S, GearVR, Go, Quest, Quest 2, Reverb G2

Anonymous
Not applicable
No offense, but you guys seem to find new ways of messing with people with every update. Now the Debug Tool doesn't work? That means the TrayTool will stop working, which a lot of people are using.

Anonymous
Not applicable
Maybe I should not try using my Rift now that this update is rolling out until they get the new SDK out, as I rely on the Tray Tool which I have set to run at windows startup.

SicTim
Level 4

xeno3d said:

  • First Contact: We updated and enhanced the experience. Check it out for a few new surprises.
Fun!  Going to go back in tonight and see if I can find anything


As someone who's run the setup several times, and will probably do so again in the future, all I want is for the Oculus button to be functional so I can skip "First Contact" if I want to. I swear that, at this point, I've figured out every possible way to visit mayhem and violence on the robot.