SteamVR

SteamVR

SteamVR > Bug Reports > Topic Details
Reproducable SteamVR beta 1.4.2 crash given bad chaperone_info.vrchap
I'll end the post with specifics, but in brief I've encountered a bug where I can reliably get SteamVR to encounter a critical error 306. OpenVR Advanced Settings 3.0.1 may have had a bug in its floor fix, because it gave bounds including what I'm guessing is a Y component of 126872477696, where a working set of bounds have something closer to 2.43 in that position. Similarly wonky is the seated Y component of -1.4382514918091517e+28; the working bounds lack a seated section.

Worth noting that 1.4.2's behavior seems preferable to 1.3.23's, which hangs with a suggestion to "Enable fullscreen mode" that doesn't appear to do anything when clicked. 1.4.2 made it very clear that something was fundamentally wrong, even if I wasn't able to fix it from within the UI.

Here are screenshots[imgur.com].

Here's a system report[drive.google.com] too.

The bounds that floor fix broke:
{ "jsonid" : "chaperone_info", "universes" : [ { "collision_bounds" : [ [ [ -1.7467094659805298, 0, -1.5930696725845337 ], [ -1.7467094659805298, 126872477696, -1.5930696725845337 ], [ -1.7473469972610474, 126872477696, 1.6217774152755737 ], [ -1.7473469972610474, 0, 1.6217774152755737 ] ], [ [ -1.7473469972610474, 0, 1.6217774152755737 ], [ -1.7473469972610474, 126872477696, 1.6217774152755737 ], [ 1.6506407260894775, 126872477696, 1.5628371238708496 ], [ 1.6506407260894775, 0, 1.5628371238708496 ] ], [ [ 1.6506407260894775, 0, 1.5628371238708496 ], [ 1.6506407260894775, 126872477696, 1.5628371238708496 ], [ 1.6740760803222656, 126872477696, -1.6372628211975098 ], [ 1.6740760803222656, 0, -1.6372628211975098 ] ], [ [ 1.6740760803222656, 0, -1.6372628211975098 ], [ 1.6740760803222656, 126872477696, -1.6372628211975098 ], [ -1.7467094659805298, 126872477696, -1.5930696725845337 ], [ -1.7467094659805298, 0, -1.5930696725845337 ] ] ], "play_area" : [ 0, 0 ], "seated" : { "translation" : [ 0, -1.4382514918091517e+28, 0 ], "yaw" : -1.5707964897155762 }, "standing" : { "translation" : [ -4.2038953929744512e-45, -3.4898007020468461e-39, 0 ], "yaw" : 0 }, "time" : "Sat Apr 20 21:07:50 2019", "universeID" : "1529698876" } ], "version" : 5 }

Here are working bounds from after I tried deleting chaperone_info.vrchap and running the room setup again; I wasn't able to complete re-doing the room setup while the broken bounds were in use:
{ "jsonid" : "chaperone_info", "universes" : [ { "collision_bounds" : [ [ [ -1.6595523357391357, 0, -1.6003862619400024 ], [ -1.6595523357391357, 2.4300000667572021, -1.6003862619400024 ], [ -1.743119478225708, 2.4300000667572021, 1.5920004844665527 ], [ -1.743119478225708, 0, 1.5920004844665527 ] ], [ [ -1.743119478225708, 0, 1.5920004844665527 ], [ -1.743119478225708, 2.4300000667572021, 1.5920004844665527 ], [ 1.6846464872360229, 2.4300000667572021, 1.5689765214920044 ], [ 1.6846464872360229, 0, 1.5689765214920044 ] ], [ [ 1.6846464872360229, 0, 1.5689765214920044 ], [ 1.6846464872360229, 2.4300000667572021, 1.5689765214920044 ], [ 1.6542285680770874, 2.4300000667572021, -1.5924340486526489 ], [ 1.6542285680770874, 0, -1.5924340486526489 ] ], [ [ 1.6542285680770874, 0, -1.5924340486526489 ], [ 1.6542285680770874, 2.4300000667572021, -1.5924340486526489 ], [ -1.6595523357391357, 2.4300000667572021, -1.6003862619400024 ], [ -1.6595523357391357, 0, -1.6003862619400024 ] ] ], "play_area" : [ 3.2999992370605469, 3.0999994277954102 ], "standing" : { "translation" : [ 0.55604588985443115, 2.3698310852050781, 3.3801004886627197 ], "yaw" : 0.69813203811645508 }, "time" : "Sun Apr 21 11:47:20 2019", "universeID" : "1529698876" } ], "version" : 5 }
< >
Showing 1-3 of 3 comments
A Valve employee has indicated that this post answers the original topic.
Kung Apr 26 @ 6:36am 
@Thynix Advanced Settings 3.0.0 had a bug with the undo function of the floor fix, so that has been disabled since 3.0.1. Was it something other than the undo function causing it for you? Are you able to test with the updated version (3.1.0) to see if you're able reproduce the Advanced Settings issue? If you still can in 3.1.0 please visit the github and make an issue: https://github.com/OpenVR-Advanced-Settings/OpenVR-AdvancedSettings/issues
Thynix Apr 27 @ 6:14am 
I haven't been able to reproduce the problem so far, but if I find a way to I'll definitely file a bug. I don't recall undo being involved; I don't think it could have been because I only recall pressing the one fix floor button in the space fix section.
Last edited by Thynix; Apr 27 @ 6:15am
< >
Showing 1-3 of 3 comments
Per page: 15 30 50

SteamVR > Bug Reports > Topic Details