Good question. Explorer needs a consistent 3 Mbps connection to be able to download and display new 360 images at a pace around 1 per second. We're not allowed to cache images ahead of time, but we try to buffer ahead as far as the white dots go. We also accommodate lower bandwidths or moving faster by not loading the image for a white dot if we predict it won't be ready by the time you get there.
But that doesn't account for network inconsistency, which Netflix might handle better than us because they can buffer further ahead and can pause if they need to rebuffer. When creating rides, at least, we can't predict every route you might take ahead at intersections, and pausing you without warning in VR wouldn't feel good.
We're now working on a new loading scheme for precreated rides that could buffer further ahead to avoid your blue screens and artifacts due to traveling too far on past dot images. Until then my suggestion would be to follow precreated rides and crank up your difficulty (over the HUD) to travel slower for the same pedaling speed.
But that doesn't account for network inconsistency, which Netflix might handle better than us because they can buffer further ahead and can pause if they need to rebuffer. When creating rides, at least, we can't predict every route you might take ahead at intersections, and pausing you without warning in VR wouldn't feel good.
We're now working on a new loading scheme for precreated rides that could buffer further ahead to avoid your blue screens and artifacts due to traveling too far on past dot images. Until then my suggestion would be to follow precreated rides and crank up your difficulty (over the HUD) to travel slower for the same pedaling speed.