Throwing a remote driver into a dangerous situation with no context sounds like a terrible solution to me. See also: Cpt Dubois from AF447. Doing that deliberately and repeatedly just multiplies the chances of catastrophic error.
And the VR driver job would be so stressful that there may not be many takers. Who would take responsibility if they made a bad call and caused a crash?
I can possibly see an On-Star-like backup VR driver role at some point when there's full self-driving and there needs to be some sort of backup of last resort when a car with no human in it freaks out. (Or if there's just a child, etc.)
But there has to be an assumption that this is a rare event and that it takes place in a context where a VR driver has time to establish some situational awareness. (Oh, and in a lot of situations, there is no "just pull over option." I've gotten into some bad weather situations but there are often only sub-optimal options at that point. Pulling over can also be dangerous or may not even be an option.
The solution would need some massive breakthroughs in reducing latency...and time travel. "We need a decision within 6 seconds...4...2...hey human, watch the inevitable crash!" (This already happened btw)
> Throwing a remote driver into a dangerous situation with no context sounds like a terrible solution to me.
We might be thinking of different situations. I'm mostly imagining a car or truck that does great on the freeway but poorly on surface streets or poorly on particular KINDS of surface streets or even particular KINDS of weather...and we KNOW this and can recognize those situations. The remote driver typically jumps in BEFORE the part that is actually dangerous.
This isn't a new problem - consider a big ship that delegates harbor navigation decisions to a harbormaster and/or tugboat, or a big plane that delegates final runway approach decisions or parking at the gate decisions to a control tower and/or local guy driving a tow vehicle or waving directional flags. You could slice the world up into "regions we can reliably navigate without help" versus "regions where we still need a little help", with the latter group shrinking over time as technology advances and maps get better and edge cases are better handled.
The initial product offering might be for long-haul truckers - the truck drives itself for hours on separated freeways and then throws to a handler when it needs to navigate unfamiliar local surface streets for a delivery. But once you've GOT that sort of infrastructure - basically a map with geofenced areas where remote drivers step in - it's a logical next step to make the help areas dynamic and mark slowdowns or detours due to an accident or a landslide or a cow on the road for similar handling.
95% of that job would not be stressful. I'd be more worried about it being boring...but then, so is normal in-person driving.
Throwing a remote driver into a dangerous situation with no context sounds like a terrible solution to me. See also: Cpt Dubois from AF447. Doing that deliberately and repeatedly just multiplies the chances of catastrophic error.
And the VR driver job would be so stressful that there may not be many takers. Who would take responsibility if they made a bad call and caused a crash?