01-02-2021, 05:53 PM
Just a follow up to my first post on this -- I went back into my google map in question to examine the route up close and think I found what my issue is.
First off, planning routes in Google Maps is new to me, so it's possible I was a bit heavy handed on laying down the "lock points" along my route (the white dot that locks the route to a certain street or corner so Google doesn't try to re-route the course I'm plotting up a different street). When I compared some of the wonky corners I was experiencing in the ride in VRfit that had me swerving or twisting crazily all over the ride turned up a street to what I had originally plotted in Google maps, these lock points were usually the culprit. I had to zoom in on my map to see the issue, corners looked fine until I zoomed right in for it to show the weird plotting.
It seemed that when I was placing a lock point on my route I had pushed or pulled it with my mouse as I locked the route in place, inevitably causing Google to plot a tight loop or weird stretched point error in an otherwise ok route line. In the VR ride these points would have me suddenly curving/wildly veering into a wall or up a side street before correcting on the rest of the turn. I went back in to Google Maps, zoomed in, and erased some unnecessary lock points to clean up the corners, and shifted a few others that kept a route on the desired street, but by moving them slightly up or down from the corner placement, it immediately smoothed out the problem turns on the map route. When I uploaded the new map in VZfit Explorer all those problem corners were fixed in the ride.
I think this is probably a beginners error on my part as I haven't seen it raised as an issue elsewhere in the forum. I'm writing this follow up just in case someone else ends up running into the same problem with their maps. Just this simple fix made a huge difference in my custom rides. Thanks!
tldr: careful placing your lock points when plotting a route in Google Maps, as they can throw off the continuity of your ride if they've pulled or distorted your intended route, especially on corners.
First off, planning routes in Google Maps is new to me, so it's possible I was a bit heavy handed on laying down the "lock points" along my route (the white dot that locks the route to a certain street or corner so Google doesn't try to re-route the course I'm plotting up a different street). When I compared some of the wonky corners I was experiencing in the ride in VRfit that had me swerving or twisting crazily all over the ride turned up a street to what I had originally plotted in Google maps, these lock points were usually the culprit. I had to zoom in on my map to see the issue, corners looked fine until I zoomed right in for it to show the weird plotting.
It seemed that when I was placing a lock point on my route I had pushed or pulled it with my mouse as I locked the route in place, inevitably causing Google to plot a tight loop or weird stretched point error in an otherwise ok route line. In the VR ride these points would have me suddenly curving/wildly veering into a wall or up a side street before correcting on the rest of the turn. I went back in to Google Maps, zoomed in, and erased some unnecessary lock points to clean up the corners, and shifted a few others that kept a route on the desired street, but by moving them slightly up or down from the corner placement, it immediately smoothed out the problem turns on the map route. When I uploaded the new map in VZfit Explorer all those problem corners were fixed in the ride.
I think this is probably a beginners error on my part as I haven't seen it raised as an issue elsewhere in the forum. I'm writing this follow up just in case someone else ends up running into the same problem with their maps. Just this simple fix made a huge difference in my custom rides. Thanks!
tldr: careful placing your lock points when plotting a route in Google Maps, as they can throw off the continuity of your ride if they've pulled or distorted your intended route, especially on corners.