Відео

That’s awesome! I can definitely see the value in subscribing to FSD before a longer road trip. I hope they don’t remove the subscription pricing model. How’s the LR? I kind of regret not going with the long range myself.

@@DriveElectricToday We love it. I had a NEMA 14-50 plug run to the garage and we use the mobile connector for home charging. Keep it plugged in at 55-60% SOC for most days and then use up to 95% for trips out of town. It predicts trip usage so well, we don't have range worries anymore after several multi-day work trips.

Unfortunately, I missed the window in which you can send a recording back to Tesla. In the moment I was too stunned to send that back. I wish I had though. Perhaps if this video gets enough engagement, it might catch Tesla’s attention and they could retroactively pull the logs. Just my guess though.

Hardware 4 - M3 2024

Yup, this is what I thought too when reviewing this incident. It’s almost as if a human driver wanted to reroute themselves and they made a knee jerk reaction on the road. This situation at 22:22 definitely resembles human like behavior.

Agreed, prob my top most critical disengagement. Though I was modifying the trip which caused that to happen. And many other comments are saying that there should be a buffer period before FSD makes any route changes after the maps are updated. Which makes a lot of sense.

Tesla should have hard rules that the car can't make a right turn from a left lane that's just common sense. First switch lanes and then turn, if there's no room to switch lanes just miss the turn.

I was also reviewing it back quite a few times now. I noticed that too. Surely not a test I want to put myself through. I am wondering, though, if I reroute again in this same area, will it do that same exact thing or will it learn not to?

@ Hmm, I don’t think FSD updates on the fly for any interventions. Possibly the next training run it will be updated for disengagements. Not sure if that would be a point releases but more likely it wouldn’t be updated based on engagements until the next major version (i.e. version 14). Also, the Tesla AI team could make manual adjustments, in which case it could easily be fixed in the next point release.

Agreed - I really wish there was a better feedback loop for these types of situations. Hopefully it’s something we’ll see evolve as time goes on.

I think so as well. We’ll see how the unsupervised testing goes, but I am thinking next year is more in line too.

That’s a good idea. I’ll absolutely do this in one of my upcoming videos. It’ll be interesting to spot any differences.

That would be awesome! Definitely open to that idea. How is your MY holding up in the winter here?

I think the latest versions of super tiny updates. Haven’t heard anything notable on the release notes either. I’m patiently waiting for those to pop up on my app though.

Awesome man! Glad to hear you’re enjoying the new Y! You definitely racked up those miles quick haha

Yes! Some sort of buffer period. Once adjusted continue down the path, then adjust accordingly 15-30 seconds afterwards. Couldn’t agree more here.

Super uncomfortable, but that is what you call a preroll. FSD was not going to turn into the other car. If you slow this video down and go frame by frame, 2 frames after the driver turns the steering wheel, the other car can already be seen in the front windshield.

I do know that they give you the ability to send a voice note at the time of disengagement. But hopefully some level of data gets sent to the team. This was good data to have.

@DriveElectricToday Agreed...there have been times I have missed a voice record send also and have thought, "they have to be receiving data still regardless of the voice memo."

Agreed, after all FSD is trained on human behavior which is pretty apparent in this situation

Agreed…. Must’ve been pretty close though the driver seem to be shaken for the rest of the video don’t blame him Yes reader should probably be only done during a stop don’t know but you got Remote the human factor agreed

Yup, as mentioned in my voiceover in the very beginning of the video - I was actively modifying the trip in the GPS to have FSD reroute in real time during that incident.

Also make rerouting easier

shouldnt need to stop, but doesnt need to react so quick in that situation.

Here is what I noticed from the video. After the driver changed the destination, FSD started breaking and it did identify the car on the right ahead of time. I can't tell if FSD actually accelerated before the driver took over but it did identify that there was a car there. It's possible that it was still breaking and it was just going to wait for the car to pass. It's possible that even though it had already identified the oncoming car it was still going to turn because it wasn't done calculating so it just didn't react fast enough. Good corner case. I would suggest not routing in the middle of the road with cars close by.

Yup, it should absolutely be taking the right lane to make that turn. Which is another reason I would have preferred it to continue straight then reroute later.

Couldn’t agree more here. It is, at the end of the day, trained in human behavior. This is a classic human decision that I’m sure we have all seen many times. Surely not a test I want to observe with FSD though.

100% - It’s funny because I’m amazed, shocked, disappointed and upset with FSD all within a 30 minute window lol

Absolutely great point here. This is what I have been pondering about as well. Though, I do wonder how unsupervised vehicles will handle GPS rerouting such as this.

@@DriveElectricToday i dont think they would make it able to use rerouting, its just for A to B. that's how it's supposed to be used. if you think about it, even with any GPS if you reroute in ANY gps nav it takes a second to figure it out. same with a tesla. it shut down and restarted while that car was already coming fast. it was your fault not FSD.

Yes that is a great point. Navigation really should be used from point A to point B. So I do agree that forcefully rerouting is tinkering with the navigation. What are your thoughts on unexpected road closures in terms of GPS rerouting such? I wonder how it would handle those types of situations?

@@DriveElectricToday actually had a situation with my tesla for this EXACT thing, i had to take over because even with the stop sign guy it didnt register it. so that has to be worked out. i drive a 2024 model 3 on 13.2.2

Very irresponsible rerouting in mid trip and not waiting for a safe area, a red light, or something like that. Even with that, I see a red warning in the camera view when the car is about to turn, can't tell, but even if the guy hadn't touched the wheel I think it was stopping because it detected the car coming. Again, very irresponsible way of rerouting, probably the best fix is not allowing a manual reroute unless you are in a safe situation

Nope, I’ve got two cameras rolling concurrently and then switch between them while I edit. I don’t cut anything out from the drive. I can see how that can be interpreted differently though. I will incorporate one camera view more often in future videos. Though I may continue using the FPV camera for unprotected turns where the main camera can’t see left and right. Thoughts on that?

Good point here. At the end of the day, these FSD training models are mirrored on human drivers. This is certainly something a human would do. I have seen many people try and turn at the very last second, spot a car in the neighboring land, then stop. Not sure if FSD was going to stop or not. Surely not a test I want to determine.

A part of me wonders if FSD would have indeed waited for that minivan to pass before turning or if it had no intention on waiting. A test, surely, I do not want to determine.

@ it seemed to brake fast to let the car go and then do the turn at a VERY close margin. im sure it calculated the speed of the car but i'm not gonna ask you to put your life on the line on my assumption.

Yes that is the most bizarre part. A certain component/stack of the system visualized and displayed the white minivan but still proceeded to make its, potentially faulty, decision.

Yes, I have absolutely observed this type of behavior with FSD many times. It’s almost as if when a sudden or unusual incident occurs, FSD doesn’t have a great “buffer” period to assess the situation properly. In the context of this situation with the white minivan and the GPS rerouting, FSD should have continued straight and deprioritize a faster route, and instead prioritize safety.

if there are different threads as you describe wouldn't engineering have the sense to make the visible rendering on the screen the last priority? what am i missing.

Agree - I, too, have noticed the abrupt decisions FSD makes upon enabling it in the middle of a drive. I must say the “start from park” function does not act like that. It takes its time to get its bearings first. It makes sense why FSD would need to adapt quickly when enabled in the middle of the drive. But it would be great to have some sort of “buffer” period to allow for the onboard cameras to get its bearings first before making a jerky, possibly dangerous, move. Thanks for your comment. This is a really interesting point you bring up in terms of enabling FSD and the abrupt nature it displays. I may use this as a talking point in my next video.

@@DriveElectricToday I've come close to 4 vehicles on the latest update. I allow FSD quite a bit of freedom for the sake of my curious nature and experimentation. lol On 3 of those occasions, I was holding on to the wheel and ready to intervene once it became absolutely necessary, but one of them happened so fast that I didn't have time to reach for the wheel. After watching your situation a couple more times, I'm sure I would have reacted similarly. My examples were a bit different, but my Y did make the correction at the very last moment of all 4 of these various close calls.

lol same!

I was hoping the settings I enabled made it better, but sounds like it’s not any better 😞 Thank you for the feedback. I will look into either changing the settings again, maybe trying out a new camera, or omit the POV camera entirely. I apologize, thank you for the feedback. I’ll look into it further.

@@DriveElectricToday thank you for kind reply, but i think when FSD going for a unprotect turn, the FPV shot is very helpful to check left and right, it is only unnecessary when it was going smoothly and straight. just doesn't to use it too frequently.

@@BerlinBK2662 Yes that makes sense. Will follow that guidance on my next video. I like to capture people’s attention with it in the very beginning of the video as well. Thank you for the feedback. Stay tuned for my next video.

Definitely don’t use two cameras. It makes viewers think you are doing it so you can edit out important events in post production.

@RaisingAwesome Ah yes, I can see that happening. Thank you all for the great feedback. I will take this seriously and implement it in my future posts.

Absolutely agreed. After this situation, it definitely seems like the blind spot monitoring attached to the side mirrors is decoupled from FSD’s visibility. I’m glad you mentioned that FSD has the capability to reroute. I was a bit unsure if the software can accommodate for that. And I started wondering if I just pushed it outside of its limits. But it really should be able to reroute in real time without issue. This was, by far, the most serious disengagement I have had to perform.

Agree. I've never seen a maneuver like that in 13.2.2

Ah yes I haven’t even noticed that the blind spot monitor light was red. Good callout, and it makes the situation even more confusing.

Totally agree! I see a lot of room for improvement when it comes to city driving with FSD. Many many flaws with downtown/city areas even today.

Yup, great correction here! In their pilot program this year, they'll be launching it on Model 3's and Model Y's. Thanks for the correction here!

Great to hear from you! Glad you enjoy the content!

@@Julian-1111 Yup, I really like the squared up hatch. To your point, that will surely help with cargo access. I’m excited to see it in person. Don’t think my Tesla dealership has a showcase yet. Have you seen it in person yet?

@ I haven’t seen it in person yet, they have one in the showroom a few miles away, several YTubers have made 4K walkarounds that are way more impressive than static images, they all comment that it looks better in real life. I have ordered one (on day one) and don’t think I’ll be disappointed.

@Julian-1111 That’s awesome! I definitely agree that the final product will look better than static images. I can’t wait to see it. I hope you enjoy it! Do you know when you can expect delivery?

@ April maybe.

Warmer weather sounds great right about now! lol Great to hear from you! Yes I was right in those neighborhoods testing FSD!

Yes I couldn’t agree more. It’s good to bring visibility into the issues. These issues are definitely not something to look past.

Hey man! Great to hear from you! I’m so glad the delivery for your new Model Y went well. That’s unbelievable that they issued a strike even when stopped. That is surely not justified. Typically, in my experience, I can look at my phone or scroll the Tesla screen without issue while stopped. Crazy to hear that. Heading over to Jungle Jim’s must have been awesome. It’s on our bucket list of places to visit soon too. So what are your thoughts almost a week into your new Model Y? You enjoying the car?

@ loving it. I’m also on v13.2.2 so there’s newer releases that hopefully will help with it not being so touchy

@johnlawler3353 Yup! Nice dude, looking forward to hearing more about your experiences!