Cool. Streetview metadata quality is variable so it's worth trying different rides. City Mode is a less dependent on that metadata, but it's not really appropriate for country rides. Our "suggested rides" were picked for being relatively good for Country Mode, as are many user-shared rides. We've also seen that Google can update that metadata, for better or worse, so we're looking into an automated tool to evaluate their changes, or possibly preserve image lookups to their ride creation date.
Also, the Quest would be a bit more comparable to Rift than a Go. On a Quest our apps run at a higher framerate, and the default steering mode is your leaning (detected from head position tracking) rather than head tilt. It uses forward/back leaning to dive faster in Play's flying games (Go users can press the B button). It offers monoscopic rendering as an option, rather than force it like the Go. It draws City Mode out a bit further, with less foveated rendering. And of course Quest's position tracking means that leaning changes your perspective, which feels more natural with respect to your avatar.
Also, the Quest would be a bit more comparable to Rift than a Go. On a Quest our apps run at a higher framerate, and the default steering mode is your leaning (detected from head position tracking) rather than head tilt. It uses forward/back leaning to dive faster in Play's flying games (Go users can press the B button). It offers monoscopic rendering as an option, rather than force it like the Go. It draws City Mode out a bit further, with less foveated rendering. And of course Quest's position tracking means that leaning changes your perspective, which feels more natural with respect to your avatar.