momo3605
Active Member
So who's going to be the first to start a whole new thread for 10.69.1.1Not a Tesla App says it's 10.69.1.1
Maybe fixing some bugs caused from the merge to 2022.20.x?
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.
So who's going to be the first to start a whole new thread for 10.69.1.1Not a Tesla App says it's 10.69.1.1
Maybe fixing some bugs caused from the merge to 2022.20.x?
Nice, I'm always wondering if 10.12.2 will run into one of those today since they're not rendered and the red line on screen is typically drawn at the curb.I'm surprised how far away the occupancy network is able to see these outdoor dining areas (estimate about 300 feet). The location predictions are also very stable, doesn't jump around like cones do:
Gosh that’s a lot of the flame. I’ll need to keep an extinguisher in the frunk.So is 10.69.1 going to be (note the extra flame)?
Even if the FSD was trained to move ahead if the other car stops for you it could be a problem with two FSD cars. Both cars stop -- see the other car is stopped so they both move ahead -- see the other car is moving so both cars stop --- see the other is stopped so they both move ahead. Hmmm.The car acts like it interprets a narrow unmarked road as being one-lane and acts as if an approaching car was on a collision course. So, it takes the best evasive action it can without actually running off the road. Coming to a full stop seems unwarranted. If the other car were a Tesla using FSD beta, I guess the two cars would sit there indefinitely!
This is curious since there are plenty of videos showing Teslas squeezing through very tight traffic.
While not exactly the same thing, we know the car in general MUST be able to see at least 400 feet to do what it is doing with unprotected lefts safely (5-7 seconds at 50mph). Stationary objects might be more difficult, but at 150m straight on there is not a lot of movement in a vehicle either.I'm having trouble believing how far and accurately the occupancy network can see. I measured 400 feet from the ego car to the left-most dining area.
No idea how their occupancy network and other methods of detection are all merged together. I don’t really know much about any of those technical details. All we know is how far it must be able to see at a minimum. Reliably? Who knows…
Hopefully it can see a lot further! Seems like 700-800 feet would be even better, though to some extent resolution limits can be compensated for by faster maneuvers.
AKA, “no Jump tonite!”
interesting. I haven't gotten it this updated build that is theoretically going out. Then again, I am not exactly an employeeAKA, “no Jump tonite!”
Im currently on 2022.20.8 with my MX which was delivered two months ago when I traded in my M3 with fsd beta. My current safety score is 94.
I’m hopeful that the 10.69 software build number might mean I get fsdb next week, once it’s released widely.
Hopeful but definitely not optimistic knowing how long this process typically takes.
Are you in the YT celebrity group?interesting. I haven't gotten it this updated build that is theoretically going out. Then again, I am not exactly an employee
I don’t think they are that incompetent. As you also noted, it may be an issue with latency delay. Although, I don’t understand exactly why it appears to take nearly 2 seconds of delay before they apply the brake aggressively. I have noticed a similar braking delay in other contexts such as cross traffic appearing just after my car begins moving into an intersection. That kind of latency may be tolerable in some contexts but for urgent braking due to a pending potential collision that is totally unacceptable. It takes people only a few dozen milliseconds to apply the brakes in similar circumstances. Either the car lacks sufficient cpu or they need to build in a fast path for urgent braking.I think it is because the AP team was unable to figure out a working control algorithm that did not respond to jitter in the speed of the lead vehicle (some people are terrible at keeping a consistent speed), while smoothly following at a reasonable distance.
Well obviously a human would not have to cross double yellow in this particular situation if they were planning on waiting for the car to pass. You stated that it couldn’t see the parked cars behind the parked car which if true is an issue with the camera placement.This is my final post on this lol. Alan said no human would poke out, but there's a whole list of reasons to slightly poke out:
Looks like the software crashed, ran on backup stack while the FSD stack restarted.Keep an eye on the FSD visualization at the timecode in this video - wonder if this has anything to do with the need for a bug fix build or if its more due to a driving characteristic fix.
Notice how he reduces the speed? Zero takeovers right?? Classic Omar!