Crowdsourced AV incident reporting & mapping for FSD issues

Some more FSD 14.2 experiences & thoughts from my ~200 mile drive/test yesterday in my @Cybertruck Positives: FSD 14.2 continues to be smooth, confident and comfortable most of the time in how it drives and operates on the highway, on rural roads in dense city traffic, handling construction & most driving situations. Dry wiper wipes seemed greatly reduced, which is appreciated! Vast majority of the drive was uneventful and well done … really helped driving in and around Austin & smaller cities between Austin and San Antonio as I was showing my family visiting from out of state around. Observations/Challenges: FSD 14.2 showed a disappointing regression back to FSD 11.X levels of speed selection errors, specifically on a stretch of Interstate 35 in San Marcos, Texas where it read frontage road speed limit signs (55 mph) and reacted on the Interstate, immediately slowing from the ~80 mph traffic flow down to 55 mph abruptly, causing a safety issue. What compounded this was the inability of any speed profile to drive above 55 mph, prompting multiple disconnects and manual driving to drive at the correct speed. This persisted for about 7 miles of Interstate driving until the speed limit detection corrected the selected speed and then FSD was re-engaged. I also saw some strange speed behaviors on frontage roads, where FSD drove significantly slower than the actual speed limit … this happened in areas the previous FSD 11.X versions also exhibited this behavior, but FSD 12.X and 13.X corrected. I wonder if this indicates some internal changes were attempted to correct the speeding issues noted on FSD 14.1.7, but now introduced past bad behaviors? FSD 14.2 struggled to park correctly at a Supercharger, parking with part of the @cybertruck well into the adjacent spot (see image) and too far for the Supercharger cable to reach. This continues parking challenges even in non-angled spots. Navigation databases mismatches to real life continued to be an issue that lets FSD 14.2 down. On one occasion, the wrong parking driveway entrance (just about 10 meters from the correct entrance) was chosen for a restaurant. This made parking impossible and a disconnect was needed. I did get a sudden “Take Over Immediately” Red Hands display while stopped at a red light. The car had been stopped for about 15 seconds waiting with no other compounding issues or scenarios that i could determine when the alert came up. Interestingly, resetting FSD worked immediately and reacted normally from that point, but the rear HVAC and fan turned off and my passengers had to restart the rear HVAC controls manually (I don’t know if this is directly related or not, but was coincident) Overall, I do see progress and I know the @Tesla_AI team is working hard to dial in how FSD 14.2 is behaving and I very much appreciate what they are doing. It is working quite well and the vast majority of my drive yesterday was uneventful and well accomplished. My goal in pointing out these issues is to help the team isolate the areas needing more attention and improving even more so we can get to unsupervised status as soon as reliably possible.

@JoeTegtmeyer @cybertruck Sometimes the speed limit data or selection is so bad it makes me think Tesla has a rouge employee that is intentionally screwing with us in the programming