Post #1547371

So, something from my car's buildlog made it into Google's AI summary (yes, it links my buildlog as the source and and only source for this)... Problem for me isn't that Google uses it (that debate can go on for ages, not worth my time), the problem is that this "fix", isn't actually a fix. It was a band-aid fix to make something work "alright-ish" for me to get certain usable data but isn't actually a proper fix. It's incorrect information that has *dangerous* consequences. Doing it this way gives the ABS module the wrong information (it'll think it's going significantly faster than it really is) which causes it to no longer function as it should (and trust me, unless you know what you're doing, you do not want to drive without properly functional ABS - and even if you do, you probably don't want to). Google's AI is unaware of this because I never mentioned this in the buildlog. To demonstrate, Image 2 shows my RPM from a log I've captured last year with my roadspeed but my car can not do 253km/h at just 3600RPM (5th gear doing 100km/h already does 3.2K and my car can't even go above 220km/h before being torque limited). Just goes to show how blindly trusting Google's AI summary can have dangerous (potentially lethal) effects... Yes, I am still working on a proper fix for this data but it's not expected anytime soon because it's not really a priority for me.