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.
What’s the word for seeing stopped cars way in the distance on local roads? Still won’t stop or is that better?
Much better, it sees the stopped car and brakes gracefully but firmly.
Random comment without a reference are you referring to braking in AP.Up to about 45mph. Used to be 30 or 35mph. Still about 15% failure rate but I've only had a day to test.
This is a game changer for local driving. Can’t wait to try it out myselfMuch better, it sees the stopped car and brakes gracefully but firmly.
Hmmm, I thought AP1 was sent down directly by God and an example of Platonic perfection, and knew all things past, present, and future? Are you telling me that someone actually thinks AP1 could possibly be improved, or that an AP1 user might be a little envious?Does anyone know if 2018.10.4 improved AP1's capabilities too? Or is it just AP2?
Yeah, but AP1 would toast bread and butter it for you, too—just the way you like it. And it had wings, too, and could fly. AP2 will never reach parity with the mythical AP1! And kids have no respect like they used to, either. Ahh, the good ol' days...
If the page is teslainventory.com it tells me "webpage is not available". 2018.10.4. and 2017 MCU.Can someone running software 2018.10.4 try to load Dærik's inventory page in the cars browser (running with the old MCU)?
According to Dæriks video the car with new MCU can load this page... So if someone is running on the lates 2018.10.4 and old MCU can open this page we can assume the browsers on new MCU and old MCU are the same....
For those on 2018.6.1 the page will not load. The car Dærik tested were running 2018.6.50...
Also, can someone actually make a comparison showing UI between the 2018.6.1 vs 2018.10.4?
If the page is teslainventory.com it tells me "webpage is not available". 2018.10.4. and 2017 MCU.
UI and web browser are both perhaps twice or more snappier than they used to be.
New audio eq setting limits beat me. I guess they are related to MCU update. Now my aftermarket setup has too much bass even with -8dB. I needed to take it to DSP tuning anyway, so quite lucky I did not do it before this update.
e we can assume the browsers on new MCU and old MCU are the same....
Mozilla/5.0 (X11; Linux) Apple WebKit/534.34 (KHTML, like Gecko) QtCarBrowser Safari/534.34
Mozilla/5.0 (X11; Linux x86_64) Apple WebKit/534.34 (KHTML, like Gecko) QtCarBrowser Safari/534.34
Up to about 45mph. Used to be 30 or 35mph. Still about 15% failure rate but I've only had a day to test.
I had a couple instances yesterday on 18.10.4 when approaching stopped vehicles about 55mph it waits too long and applies the brakes abrupt and harsh......this still needs work
Anything 45mph or less seems fairly polished
I had a couple instances yesterday on 18.10.4 when approaching stopped vehicles about 55mph it waits too long and applies the brakes abrupt and harsh......this still needs work
Anything 45mph or less seems fairly polished
Based on my driving on local roads it even stops for completely stopped vehicles like trucks parked and clogging the lane, this is a major improvement as with previous versions it was like playing a game of chicken. It seems like the NN changes have allowed the AP to rely much more on the cameras with the ability to classify cars and trucks more like the MobileEye platform could.
Can't wait for iterations on this build and to get the side repeater cameras active!