Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register
This site may earn commission on affiliate links.
Do people think the demo visualizing the blue path was coming from the new end-to-end control network? It does seem to behave differently at least at roundabouts. This DirtyTesla 11.4.2 video shows highlighting other vehicle in blue and whole path is faded indicating it's waiting for the other vehicle to fully pass. Whereas V12 seems to show no blue path when waiting/stopped and begins to extend as the other vehicle is passing for smoother initiation showing intent before switching to "full speed" blue path.

v11.4.2 vs v12 enter roundabout.jpg
 
Do people think the demo visualizing the blue path was coming from the new end-to-end control network? It does seem to behave differently at least at roundabouts. This DirtyTesla 11.4.2 video shows highlighting other vehicle in blue and whole path is faded indicating it's waiting for the other vehicle to fully pass. Whereas V12 seems to show no blue path when waiting/stopped and begins to extend as the other vehicle is passing for smoother initiation showing intent before switching to "full speed" blue path.

View attachment 969583
Elon said that V12 nav wouldn't be exactly what the NN is intending to do. Might lead to some exciting moments..
 
  • Informative
Reactions: APotatoGod
Elon said that V12 nav wouldn't be exactly what the NN is intending to do
Was this from the demo or some other discussion? I believe the demo discussion included the possibility to drive without maps as it would be useful in navigating to destination pins / GPS points / "go there" such as in large parking lots. He also gave caveats of it might end up at dead ends and need to reverse, so presumably making use of map data when available will still help. Tesla's experience with FSD Beta so far in relying on sometimes inaccurate / incorrect map data should mean "deep lane guidance" to visually predict more accurate Lanes will stick around even with end-to-end.

So indeed the blue navigation line on the map probably won't necessarily match up especially in situations like unmapped parking lots, and the blue path of the visualization would still likely represent what FSD / neural network for V12 is about to do.
 
Do people think the demo visualizing the blue path was coming from the new end-to-end control network? It does seem to behave differently at least at roundabouts. This DirtyTesla 11.4.2 video shows highlighting other vehicle in blue and whole path is faded indicating it's waiting for the other vehicle to fully pass. Whereas V12 seems to show no blue path when waiting/stopped and begins to extend as the other vehicle is passing for smoother initiation showing intent before switching to "full speed" blue path.

View attachment 969583

At around 19:37 during the livestream, you can see they're running the V11 perception stack at a much lower frame rate. They're probably also disabling certain perception features / objects:

 
Was this from the demo or some other discussion? I believe the demo discussion included the possibility to drive without maps as it would be useful in navigating to destination pins / GPS points / "go there" such as in large parking lots. He also gave caveats of it might end up at dead ends and need to reverse, so presumably making use of map data when available will still help. Tesla's experience with FSD Beta so far in relying on sometimes inaccurate / incorrect map data should mean "deep lane guidance" to visually predict more accurate Lanes will stick around even with end-to-end.

So indeed the blue navigation line on the map probably won't necessarily match up especially in situations like unmapped parking lots, and the blue path of the visualization would still likely represent what FSD / neural network for V12 is about to do.
13 mins here:
 
Not sure about this.

It needs to get trained on others running red-lights to know when to anticipate others may run a red light (given the paucity of such data, training that may be difficult - but a different problem). Then, it may be able to avoid hitting the redlight running vehicle.

Ofcourse, they shouldn't train on ego runing redlights. But Elon's car ran a redlight ... so may be they did ;)
Running red lights is a subset of 'watch out for other cars'. If collision avoidance is implemented, then the only additional step might be reduced speed or increased vehicle spacing in higher risk areas (crossing intersections).

Are you referring to when ego wanted to proceed on the left turn arrow red to green transition, or a different event?
 
  • Like
Reactions: willow_hiller
Does anything think Tesla will release V12 within the next 5 years?
And what makes you think that V12 won't be released much, much earlier?

Sheesh. The negativity around here. The main financial thread thought that the autonomous driving area had been invaded by TeslaQ; given the comments and data-free speculation, they might have a point.
 
I would think this means it would have to be greater than L2
Why?

So confused by that statement. Elon certainly wants L4/L5 and has said explicitly so recently. But what he wants and what will be delivered…never the twain shall meet. So no reason to expect anything other than L2 on HW3 or HW4.

Maybe L3? Maybe. Seems like a big lift though.
 
  • Funny
Reactions: APotatoGod
No. Nags don't make it Beta, but even without wheel nags it can and will still be level 2.
I feel like the NHTSA will have a field day with non-beta full self driving software that can’t full self drive. It can hide behind the beta tag now, but removing that tag is asking for trouble in my opinion as it means it’s finished software working as promised.
 
  • Funny
Reactions: AlanSubie4Life
Sheesh. The negativity around here. The main financial thread thought that the autonomous driving area had been invaded by TeslaQ; given the comments and data-free speculation, they might have a point.
There are a baffling number of users on this site who engage on a daily basis despite having an overwhelmingly negative opinion of everything to do with Tesla. I think some of them (particularly the ones that pop up from nowhere and try and stoke up discussion on some long-dead anti-EV talking point) could be attempts and manipulating stock prices - since Tesla stock has been heavily gamed/shorted etc numerous times it's probably more likely than not that this happens sometimes.

There are other posters that don't really seem to have an agenda other than just to winge. The psychology that would lead someone to deliberately wallow in something they dislike on a daily basis is perplexing. There are plenty of users here who aren't like that, but eventually you lose interest in arguing and just read passively.
 
The far more relevant question is does anyone think V12 will offer >L2 operation on HW3- and I'm pretty firmly in the no camp on that one.
How does the software even become >L2, in practice? I don't mean its technical capabilities, I'm talking regulation.

Let's say Tesla suddenly decide it's ready and they'd be prepared to take liability for any accidents that happen while the software is engaged. For that to happen there'd have to be modifications to the legal framework - which will currently be written such that the meat in the seat is always in charge of the vehicle and accountable for its actions - and presumably there needs to be some sort of certification process that some regulatory authority would need to go through, much like how Cruise/Waymo etc keep renegotiating the parameters of their permission in SF.

Is there anywhere where the roadmap for this to happen is actually agreed yet? Presumably it would be on a state by state basis in the US, potentially with different criteria in each state?
 
  • Informative
Reactions: APotatoGod
Is there anywhere where the roadmap for this to happen is actually agreed yet? Presumably it would be on a state by state basis in the US, potentially with different criteria in each state?

Yes, it would be on a State by State basis since each State has their own AV regulations. See map:

chart.png