You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
Did you know that, at slow speed, you can engage the opposite direction while still moving.Does anyone else have the problem of requiring two pushes to get into drive or reverse modes?
The problem is not alway there as sometimes it works correctly.
When you press the brake and "turn on" the car there is a one second or so delay before the car will actually go into gear. Once the majority of the "Dash lights" finish their diagnosis flash and turn off you can then select a gear.
So to be clear, you would prefer if the vehicle acknowledged the gear selection and them implemented the change after it’s ready?
I’m aware the car does this, so I step on the pedal while entering the car. After seated and buckled, I grab a gear. Otherwise I find myself shifting into gear a few times before the car moves.
By saying "there is a one second or so delay before the car will actually go into gear" I thought it would be obvious that the car is ignoring the user input during that time. From my admittedly limited UI/UX experience having a delay where the car goes into gear would be significantly worse than ignoring the input. It either should react immediately or ignore the input in almost all cases as critical as changing direction of travel. Think along the lines of if you press the park button while going 50kmph, it will ignore your input and display an error message. If it waited until you hit a slow speed, then put the car into park, this would be a bad idea. Generally queuing up input like this is a bad idea for something as important as driving.Correction.
After you press the brake, there is a one second or so delay before the car will listen to the gear selector.
It wouldn't be as annoying if it was just a delay getting in gear and remembered that you selected a gear, but the request goes into the bit bucket until it's ready to listen.
It seems to be the first time after the car has been sitting a bit. If you parked after moving and did it again, there is no delay, which kind of trains you into thinking you can do any gear select quickly all the time. When you get in, the car partially already feels "on" (HVAC is the loudest feedback that the car is sort of on) and you're just hitting the brake for safety interlock, not to "start it" and wait and then select. I'm not saying the brake does not start it. But your muscle memory forgets that it is starting it and needs to wait, with very little feedback that it's not ready then ready unless you watch the lights. And it behaves slightly different when it's sat longer.
And as the Video shows you don't even have to come to a full stop to reverse direction. It's not quite as consistent as it could be. I can change direction before it stops with gear selector but I can't put in drive while it's stopped, to get going.
This reminds me of when I used to remote start my Jeep. I'd get in with engine running. My muscle memory is telling me the car is ready to go because it hears the engine. I got to put my foot on brake and then put it in gear and it won't go. Because for security I still have to "Start it". This stumped my brain every single time. It's a similar thing. The car feels on. Step on brake and go into gear in one fluid motion. Bzzzt, not yet buddy. But Tesla will later and will when reversing gear.
My long argument here is it's not an impatience thing. It's like driving a stick. It's all unconscious muscle memory at work. And the Tesla is slightly inconsistent. I make the mistake almost every day even though I know I need to wait. This is by no means a big deal. But don't blame folks for being impatient that run into this. It could be a tone when you hit brake to start and a different tone start up is complete. Watching dash lights is not enough.
By saying "there is a one second or so delay before the car will actually go into gear" I thought it would be obvious that the car is ignoring the user input during that time. From my admittedly limited UI/UX experience having a delay where the car goes into gear would be significantly worse than ignoring the input. It either should react immediately or ignore the input in almost all cases as critical as changing direction of travel. Think along the lines of if you press the park button while going 50kmph, it will ignore your input and display an error message. If it waited until you hit a slow speed, then put the car into park, this would be a bad idea. Generally queuing up input like this is a bad idea for something as important as driving.
I'm going out on a limb here and assuming the delay is not by design, but is required by the car while it does a brief start up cycle. Like you said, it's pretty unintuitive and counters muscle memory. Perhaps having an error message pop up when you try to shift too early would help allow people to train for this odd design. I've gotten used to it now, but I'll admit it took me a month or so to do so. Another annoying thing I had to get used to was NOT pressing the brake as soon as I get in, lest the seatbelt chime drive me crazy. That design choice really annoys me, why does the car have to warn you about the seatbelt being off before the car is even in gear, nevermind moving? Perhaps it's some safety regulation or something.
I like the idea of a startup noise, anything but those annoying beeps that happen when you "start" the car before putting your seatbelt on. A nice spaceship whoosh sound would do for me, haha.I think it could be done safely through feed back, that it's "in progress". Like a big 3 Beep, 2 Beep, 1 Beep... Drive. It just has to give you feed back that it's working on it. It's annoying the way it is, lots of safe ways to deal with it, if the delay is required. And no I think an error message would be just as annoying. The natural instinctive operation should not tell the user, they did it wrong. And I forget at the moment but I think you get a beep or something some where along the way (when it does not go in gear). Maybe when you step on throttle and it's not in gear. I forget.
The way the rest of car operates it leads you down a path that it should work. And I like I said earlier. It's not consistent either.
Maybe an Engine Startup Noise My Volt does that. Not a Engine noise but a space ship launch noise. Maybe it's functional and is unconsciously telling me "I'm Booting" and leads me to not touch the gear selector until it's done. Not sure.
BTW I noticed recently quite a bit of lag lately that after it is in gear, it doesn't want to go right away. Especially when flipping R to D or D to R which was never an issue before. But that doesn't feel that bad or annoying where it just does nothing. An no more "dangerous" then remembering I asked for D. It remembers R to D, or D to R and does not respond immediately, but eventually does. If it was too long it probably would be dangerous. The lag is probably 1 second or 2.
Still not sure if it's a bug, or only when regen is limited or by design. But it worked perfect for a short while.
I like the idea of a startup noise, anything but those annoying beeps that happen when you "start" the car before putting your seatbelt on. A nice spaceship whoosh sound would do for me, haha.
Correction.
After you press the brake, there is a one second or so delay before the car will listen to the gear selector.
It wouldn't be as annoying if it was just a delay getting in gear and remembered that you selected a gear, but the request goes into the bit bucket until it's ready to listen.
It seems to be the first time after the car has been sitting a bit. If you parked after moving and did it again, there is no delay, which kind of trains you into thinking you can do any gear select quickly all the time. When you get in, the car partially already feels "on" (HVAC is the loudest feedback that the car is sort of on) and you're just hitting the brake for safety interlock, not to "start it" and wait and then select. I'm not saying the brake does not start it. But your muscle memory forgets that it is starting it and needs to wait, with very little feedback that it's not ready then ready unless you watch the lights. And it behaves slightly different when it's sat longer.
And as the Video shows you don't even have to come to a full stop to reverse direction. It's not quite as consistent as it could be. I can change direction before it stops with gear selector but I can't put in drive while it's stopped, to get going.
This reminds me of when I used to remote start my Jeep. I'd get in with engine running. My muscle memory is telling me the car is ready to go because it hears the engine. I got to put my foot on brake and then put it in gear and it won't go. Because for security I still have to "Start it". This stumped my brain every single time. It's a similar thing. The car feels on. Step on brake and go into gear in one fluid motion. Bzzzt, not yet buddy. But Tesla will later and will when reversing gear.
My long argument here is it's not an impatience thing. It's like driving a stick. It's all unconscious muscle memory at work. And the Tesla is slightly inconsistent. I make the mistake almost every day even though I know I need to wait. This is by no means a big deal. But don't blame folks for being impatient that run into this. It could be a tone when you hit brake to start and a different tone start up is complete. Watching dash lights is not enough.