In this particular case, the user that shared the logs mentioned that at around 19:31 local time, the screen froze. Then he waited, as I instructed 2-3 minutes, before shutting down the game.
This can be seen around line 429. Nothing happens at that time, and at 19:33:09 (line 425), he chooses to shut down the game.
Another user, who was streaming/recording at the time, actually captured this on video.
While this shake frame is happening, the main thread is continuing to run. While the visuals don't update, the user poses are being sent to the opponent, and voip is continuing, and physics is operating (the opponent can hit a ball at your paddle...you can drop the ball on the paddle and feel it)
If I could venture a guess, it's it looks like a it might be reprojecting between two frames, and some part of the algorithm is kicking back 1 whole frame time by accident...or I could be completely wrong. - either way, it's not promising that there are no signs of any error anywhere.
This only happens on the quest. Many users have reported it, and it doesn't appear to have any noticeable pattern.
line 429 adb log.txt
In this particular case, the user that shared the logs mentioned that at around 19:31 local time, the screen froze. Then he waited, as I instructed 2-3 minutes, before shutting down the game. This can be seen around line 429. Nothing happens at that time, and at 19:33:09 (line 425), he chooses to shut down the game.
Another user, who was streaming/recording at the time, actually captured this on video. While this shake frame is happening, the main thread is continuing to run. While the visuals don't update, the user poses are being sent to the opponent, and voip is continuing, and physics is operating (the opponent can hit a ball at your paddle...you can drop the ball on the paddle and feel it)
https://youtu.be/5d8cl1NUrxo
If I could venture a guess, it's it looks like a it might be reprojecting between two frames, and some part of the algorithm is kicking back 1 whole frame time by accident...or I could be completely wrong. - either way, it's not promising that there are no signs of any error anywhere.