cancel
Showing results for 
Search instead for 
Did you mean: 

Beginning rollout of version 1.15 (PC software update for May)

cybereality
Grand Champion
Hey everyone –
 
Excited to announce that today we started rolling out the Rift 1.15 software update. For a full look at what you can expect, check out the patch and release notes found here: https://ocul.us/releasenotes Along with bug fixes and various tweaks, you’ll also find improved 360 degree tracking and roomscale support, along with a few other features. Thanks again for your feedback and reports, and to everyone who helped us test 1.15 early.


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
53 REPLIES 53

KirilZdravkov
Explorer

Rolz said:

is it possible to see a download progress or a logfile of some sort?

I'm on 1.15.0.392473 (1.15.0.391815) but my computer busy downloading more updates (I guess?)
59z0hxnrbhqg.jpg


OVRServer continually sends and receives bits and pieces, whether there is an update or not.

From what I've gathered its something to do with checking your status, keeping up 2 date with new content, what are you playing etc etc.

Anonymous
Not applicable
I've received the automatic update in 29-may, and since then I can't get my DK2 to work. I use this for development, and this is costing me a lot.

When I try to start a VR app (say, Oculus 360 Photos, or any other app, even my own developed ones), the headset simply doesn't wake from stand by (the orange light doesn't turn blue). The apps from Oculus App usually quit while loading, and other apps just run, but with no headset tracking.

When I try to run a full setup, I get stuck while the app can't detect the headset HDMI and the headset USB (from the three scans, just sensor USB 2.0 is detected).

If I switch to SDK version 0.8, all works fine.

I tried updating my graphics card (GeForce GTX 750, driver version 382.33), and also reinstalling the Oculus App.

I'm on Windows 10, the Oculus App version is 1.15.0.392473 (1.15.0.391815).

Anonymous
Not applicable

brunoleos said:

I've received the automatic update in 29-may, and since them I can't get my DK2 to work. I use this for development, and this is costing me a lot.

When I try to start a VR app (say, Oculus 360 Photos, or any other app, even my own developed ones), the headset simply doesn't wake from stand by (the orange light doesn't turn blue). The apps from Oculus App usually quit while loading, and other apps just run, but with no headset tracking.

When I try to run a full setup I get stuck because the app can't detect the headset HDMI and the headset USB (sensor USB 2.0 is detected).

If I switch to SDK version 0.8, all works fine.

I tried updating my graphics card (GeForce GTX 750, driver version 382.33), and also reinstalling the Oculus App.

I'm on Windows 10, the Oculus App version is 1.15.0.392473 (1.15.0.391815).


I've just read a last log and found some errors (there are INFOs and DEBUGs between these):

Line 103: 02/06 15:31:46.298 {!ERROR!} [GuardianSubsystem] Invalid type in SensorsStateFromString: 
Line 181: 02/06 15:31:47.719 {!ERROR!} [GuardianSubsystem] Invalid type in SensorsStateFromString: 
Line 572: 02/06 15:31:50.716 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 575: 02/06 15:31:50.716 {!ERROR!} [Overlays] [boundary_failed] { message: Failed to create eye render buffers.,  }
Line 576: 02/06 15:31:50.716 {!ERROR!} [Overlays] [overlays_failed] { message: Failed To init BoundarySystem,  }
Line 646: 02/06 15:31:53.068 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 651: 02/06 15:31:53.084 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 656: 02/06 15:31:53.101 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 661: 02/06 15:31:53.117 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 666: 02/06 15:31:53.134 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 671: 02/06 15:31:53.153 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 676: 02/06 15:31:53.174 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 761: 02/06 15:31:55.430 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 764: 02/06 15:31:55.431 {!ERROR!} [Overlays] [boundary_failed] { message: Failed to create eye render buffers.,  }
Line 765: 02/06 15:31:55.431 {!ERROR!} [Overlays] [overlays_failed] { message: Failed To init BoundarySystem,  }
Line 1134: 02/06 15:36:22.739 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 1137: 02/06 15:36:22.740 {!ERROR!} [Overlays] [boundary_failed] { message: Failed to create eye render buffers.,  }
Line 1138: 02/06 15:36:22.740 {!ERROR!} [Overlays] [overlays_failed] { message: Failed To init BoundarySystem,  }
Line 1193: 02/06 15:36:24.827 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 1198: 02/06 15:36:24.846 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 1203: 02/06 15:36:24.878 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 1208: 02/06 15:36:24.895 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 1213: 02/06 15:36:24.911 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 1218: 02/06 15:36:24.928 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 1223: 02/06 15:36:24.945 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 1236: 02/06 15:36:34.045 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 1241: 02/06 15:36:34.079 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 1246: 02/06 15:36:34.097 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 1251: 02/06 15:36:34.114 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 1256: 02/06 15:36:34.129 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 1261: 02/06 15:36:34.145 {!ERROR!} [Kernel:Error] D3D11CreateDevice
Line 1266: 02/06 15:36:34.160 {!ERROR!} [Kernel:Error] D3D11CreateDevice

Stinno
Honored Guest
@brunoleos I had similar issues to those you are describing with my DK2 and a GTX 760. I also tried all the same things you did, reinstalling the Oculus app and updating to Nvidia driver 382.33 with no success.

However, I have been able to resolve my issues, and get the DK2 working with OH 1.15, by installing Nvidia driver 381.89, as someone else mentioned in another thread. I recommend you try this driver version if you are still having issues.

Best regards,
Stinno

JacobVR
Explorer
It makes sense to break it into smaller parts. When you think about the size and scale of just this update it is easier to fix and trouble shoot a "smaller" update. Even things like the AI issue will be easier to sort with existing troops before complicating the mix with cerbs for elves and fairy units, etc.

Anonymous
Not applicable

Stinno said:

@brunoleos I had similar issues to those you are describing with my DK2 and a GTX 760. I also tried all the same things you did, reinstalling the Oculus app and updating to Nvidia driver 382.33 with no success.

However, I have been able to resolve my issues, and get the DK2 working with OH 1.15, by installing Nvidia driver 381.89, as someone else mentioned in another thread. I recommend you try this driver version if you are still having issues.

Best regards,
Stinno


@Stinno, you saved my week, man! Now my DK2 is working again 🙂

Grateful for these good souls for sharing such knowledge.

Tha_Rotiart
Honored Guest

elboffor said:





Hey everyone –
 
Excited to announce that today we started rolling out the Rift 1.15 software update. For a full look at what you can expect, check out the patch and release notes found here: https://ocul.us/releasenotes Along with bug fixes and various tweaks, you’ll also find improved 360 degree tracking and roomscale support, along with a few other features. Thanks again for your feedback and reports, and to everyone who helped us test 1.15 early.




I honestly hope I can start using my 3rd sensor again without having to spend an hour and a half trying to "squeeze the trigger", 'Sorry, LOLNOPE you have to move your sensor 1 cm to the left, but start everything again first!', Squeeze the trigger, 'Again NOPEMATE, It's about 1 degrees off. Try moving it so it points 1 degree right of Mekka and try everything again'. Ahhhh, you were almost there but now we can't really find your 3rd sensor. try again!


Try new batteries in your touch. I had this issue with my 4 sensor setup till i swapped out my apparently "full" batteries for new ones


I'll try, thanks for the tip

Tha_Rotiart
Honored Guest

elboffor said:





Hey everyone –
 
Excited to announce that today we started rolling out the Rift 1.15 software update. For a full look at what you can expect, check out the patch and release notes found here: https://ocul.us/releasenotes Along with bug fixes and various tweaks, you’ll also find improved 360 degree tracking and roomscale support, along with a few other features. Thanks again for your feedback and reports, and to everyone who helped us test 1.15 early.




I honestly hope I can start using my 3rd sensor again without having to spend an hour and a half trying to "squeeze the trigger", 'Sorry, LOLNOPE you have to move your sensor 1 cm to the left, but start everything again first!', Squeeze the trigger, 'Again NOPEMATE, It's about 1 degrees off. Try moving it so it points 1 degree right of Mekka and try everything again'. Ahhhh, you were almost there but now we can't really find your 3rd sensor. try again!


Try new batteries in your touch. I had this issue with my 4 sensor setup till i swapped out my apparently "full" batteries for new ones


Lolnope, still the same shit. Move this one closer, move that one 1 degrees if the sun is directly above the Queen of England and alligned with both Jupiter AND Pluto. Aiiiiiii I see that Pluto is not a planet, guess you can't play anymore with a full setup man. 

elboffor
Consultant



elboffor said:





Hey everyone –
 
Excited to announce that today we started rolling out the Rift 1.15 software update. For a full look at what you can expect, check out the patch and release notes found here: https://ocul.us/releasenotes Along with bug fixes and various tweaks, you’ll also find improved 360 degree tracking and roomscale support, along with a few other features. Thanks again for your feedback and reports, and to everyone who helped us test 1.15 early.


I honestly hope I can start using my 3rd sensor again without having to spend an hour and a half trying to "squeeze the trigger", 'Sorry, LOLNOPE you have to move your sensor 1 cm to the left, but start everything again first!', Squeeze the trigger, 'Again NOPEMATE, It's about 1 degrees off. Try moving it so it points 1 degree right of Mekka and try everything again'. Ahhhh, you were almost there but now we can't really find your 3rd sensor. try again!


Try new batteries in your touch. I had this issue with my 4 sensor setup till i swapped out my apparently "full" batteries for new ones


Lolnope, still the same shit. Move this one closer, move that one 1 degrees if the sun is directly above the Queen of England and alligned with both Jupiter AND Pluto. Aiiiiiii I see that Pluto is not a planet, guess you can't play anymore with a full setup man. 


you are standing on one leg when you run setup aren't you?
i mean it seems obvious to me and i know everyone else does it but worth a call out.
Also make sure you have less that £2 in change in your pocket cos that can interfere with it too.
and if the neihboard has a dog that more than 3 years old, you can kiss the idea of easy setup goodbye
This is my forum signature.
There are many others like it, but this is mine.

Anonymous
Not applicable

elboffor said:




elboffor said:





Hey everyone –
 
Excited to announce that today we started rolling out the Rift 1.15 software update. For a full look at what you can expect, check out the patch and release notes found here: https://ocul.us/releasenotes Along with bug fixes and various tweaks, you’ll also find improved 360 degree tracking and roomscale support, along with a few other features. Thanks again for your feedback and reports, and to everyone who helped us test 1.15 early.


I honestly hope I can start using my 3rd sensor again without having to spend an hour and a half trying to "squeeze the trigger", 'Sorry, LOLNOPE you have to move your sensor 1 cm to the left, but start everything again first!', Squeeze the trigger, 'Again NOPEMATE, It's about 1 degrees off. Try moving it so it points 1 degree right of Mekka and try everything again'. Ahhhh, you were almost there but now we can't really find your 3rd sensor. try again!


Try new batteries in your touch. I had this issue with my 4 sensor setup till i swapped out my apparently "full" batteries for new ones


Lolnope, still the same shit. Move this one closer, move that one 1 degrees if the sun is directly above the Queen of England and alligned with both Jupiter AND Pluto. Aiiiiiii I see that Pluto is not a planet, guess you can't play anymore with a full setup man. 


you are standing on one leg when you run setup aren't you?
i mean it seems obvious to me and i know everyone else does it but worth a call out.
Also make sure you have less that £2 in change in your pocket cos that can interfere with it too.
and if the neihboard has a dog that more than 3 years old, you can kiss the idea of easy setup goodbye


When I run the sensor setup since 1.15 I get the "Move closer to front sensors" message. If I do the initial pull the trigger when in sight of all sensors when I'm nowhere near the middle of my playspace it shows to adjust the sensors, but if I followed that I'd have no tracking in the back half of my space.
Have you tried just ignoring that and clicking "Proceed"? I do that and haven't noticed any issues in games. Got a ticket logged with support. 
I'm running 3 sensors by the way and never had a problem with the setup until 1.15.