OTA 1.2.19

[borski]

Yeah exactly!

Lucid created this software mess themselves and we're now approaching the 1 year mark so I think people have been patient enough. Features, can come whenever but for speed and stability issues I think people have given Lucid ample time to address. The communication on this from Lucid has been appalling also, it's basically non-existent with only an unofficial comment made on Twitter etc. recently.

Lucid also created this amazing car themselves

It takes time to fix a mistake when that mistake is the entire software stack’s architecture. Rushing it is not going to make you happier in the end.

 

[hydbob]

Yeah exactly!

Lucid created this software mess themselves and we're now approaching the 1 year mark so I think people have been patient enough. Features, can come whenever but for speed and stability issues I think people have given Lucid ample time to address. The communication on this from Lucid has been appalling also, it's basically non-existent with only an unofficial comment made on Twitter etc. recently.

Imagine an army of of Muskites on Twitter saying after every software update how can anyone buy a car from a company with so many software updates. Let the updates speak for themselves imo!

 

[Sam6062]

I just installed .185 also . Glad to see the cameras and lidar are getting updates. I was driving on the expressway last night with the ACC and was uncomfortable with the braking when traffic slowed/stopped. The car's reaction time was not optimal. It doesn't seem like the lidar looks far enough out front, it only reacts within around 50 yards and I have the setting on 4 bars for the maximum follow distance.

Most likely this LiDar is the basic garden variety available today and probably not too effective. Also it is only supposed to provide point cloud data that says Drivable/Not Drivable then the Nvidia stack/ domain controller has to decide what to do therefore it looks like that piece needs to be corrected via software updates.

Glad we are bringing out all these issues out to have the knowledge and a workaround but should definitely be reporting it all to Service so that it is all on record. Without that, they may not have any incentive to provide a fix sooner than their next software update. Not rushing them etc notwithstanding.

Thanks for sharing.

 

[HC_79]

Lucid also created this amazing car themselves

It takes time to fix a mistake when that mistake is the entire software stack’s architecture. Rushing it is not going to make you happier in the end.

Well if they understood the software stack and architecture in the first place then this would’ve been a non-issue.

I’m not willing to give Lucid a blanket “free pass” on every issue because they’re a “new” company. Yes, issues are to be expected but constantly defending them for poor behavior I don’t agree with.

People have been very patient to wait this long for a software that is very unstable and all I can say is thank god for OTA in this scenario. It’s great to see updates coming out regularly, probably 20 or so now but it’s certainly something Lucid shouldn’t be proud of. That number of updates in such a short space of time shows how flawed the system actually was/is

 

[hydbob]

Well if they understood the software stack and architecture in the first place then this would’ve been a non-issue.

I’m not willing to give Lucid a blanket “free pass” on every issue because they’re a “new” company. Yes, issues are to be expected but constantly defending them for poor behavior I don’t agree with.

People have been very patient to wait this long for a software that is very unstable and all I can say is thank god for OTA in this scenario. It’s great to see updates coming out regularly, probably 20 or so now but it’s certainly something Lucid shouldn’t be proud of. That number of updates in such a short space of time shows how flawed the system actually was/is

But they've admitted it, publicly, that the software was lacking. They get a longer runway, from me, for at least trying to fix it with OTAs.

 

[borski]

Well if they understood the software stack and architecture in the first place then this would’ve been a non-issue.

I’m not willing to give Lucid a blanket “free pass” on every issue because they’re a “new” company. Yes, issues are to be expected but constantly defending them for poor behavior I don’t agree with.

People have been very patient to wait this long for a software that is very unstable and all I can say is thank god for OTA in this scenario. It’s great to see updates coming out regularly, probably 20 or so now but it’s certainly something Lucid shouldn’t be proud of. That number of updates in such a short space of time shows how flawed the system actually was/is

I’m not excusing it; they made a mistake. I’m just also not crucifying then or raking them over the coals for it. They fucked up. They’re working on fixing it. Isn’t that exactly what you want?

 

[hmp10]

When I began the steps for downloading 1.2.185 I got a message reading, "Before beginning this update, make sure your vehicle is not plugged in".

As I moved through the next steps, I arrived at a message instructing that, if I needed the car to resume charging upon completion of the download, I should be sure the car is plugged in to the charger before starting the download.

On some earlier updates, I got the warning to unplug the car but did not get the later message to keep the car plugged in if I wanted charging to resume.

I left my car plugged in for 1.2.185, and the download was successful. What was the point of the first warning that the vehicle should not be plugged in? And why does it vary from one update to another?

 

[hydbob]

When I began the steps for downloading 1.2.185 I got a message reading, "Before beginning this update, make sure your vehicle is not plugged in".

As I moved through the next steps, I arrived at a message instructing that, if I needed the car to resume charging upon completion of the download, I should be sure the car is plugged in to the charger before starting the download.

On some earlier updates, I got the warning to unplug the car but did not get the later message to keep the car plugged in if I wanted charging to resume.

I left my car plugged in for 1.2.185, and the download was successful. What was the point of the first warning that the vehicle should not be plugged in? And why does it vary from one update to another?

1.2.19 will be the same lol.

BTW, how is your car now @hmp10

 

[Sam6062]

Just completed the update to 1.2.185 now I am ready for those dreams…. Did not take the 12 minutes it said it could take.

One of the items is to fix that AC not working while driving. Anyone who was still having that issue and has updated to 1.2.185 have any feedback yet?

I have not driven mine yet after the update. Will see if there is any noticeable change.

 

[hmp10]

BTW, how is your car now @hmp10

There seem to be less software glitches since the last service shop visit: no screen seizures or system shutdowns. Today I ran some in-and-out errands after downloading 1.2.185 last evening. Everything seemed okay except that upon returning to the car on one occasion it was very slow to recognize the key fob and unlock. I actually had time to read a short text message. Also, at the same stop I waited for the backup camera to appear before backing out of the parking space. Everything looked clear, but I got a cross-traffic alert and stopped to look. Over my left shoulder I saw a pickup truck that still wasn't showing on the camera screen. After a couple more seconds, I got a blurred jerky image that then resolved into the image of the truck, which by then had already passed behind the car. This laggard camera response has happened a few times recently.

 

[rlhyde]

I just got 1.2.185. Now when I charge (at home) I see how long it will take to finish the charge. They didn't used to have that, did they?

 

[Sam6062]

There seem to be less software glitches since the last service shop visit: no screen seizures or system shutdowns. Today I ran some in-and-out errands after downloading 1.2.185 last evening. Everything seemed okay except that upon returning to the car on one occasion it was very slow to recognize the key fob and unlock. I actually had time to read a short text message. Also, at the same stop I waited for the backup camera to appear before backing out of the parking space. Everything looked clear, but I got a cross-traffic alert and stopped to look. Over my left shoulder I saw a pickup truck that still wasn't showing on the camera screen. After a couple more seconds, I got a blurred jerky image that then resolved into the image of the truck, which by then had already passed behind the car. This laggard camera response has happened a few times recently.

Yeah, it looks like the timing on the backup cameras still needs work. This has been an ongoing issue for me ever since 1.2.16. As I said earlier have not driven the car yet after 1.2.185

 

[Adnillien]

I just got 1.2.185. Now when I charge (at home) I see how long it will take to finish the charge. They didn't used to have that, did they?

That is not new, it has always been there.

 

[tkhan456]

All I want is faster boot and Apple CarPlay. Everything else is gravy

 

[hydbob]

All I want is faster boot and Apple CarPlay. Everything else is gravy

Soon...

 

[abbas2099]

I dont believe there is mistakes. I think they made a car with tons of sensors/radars/.... and they just need to figure out how to tie all the 'gadgetries' in together and not cause issues.

For me, I have said it before and will say it again.. I can live with most things not working as long as the car drives and the RADIO is functional. I am still waiting on the radio fix

 

[amoroso6]

I dont believe there is mistakes. I think they made a car with tons of sensors/radars/.... and they just need to figure out how to tie all the 'gadgetries' in together and not cause issues.

For me, I have said it before and will say it again.. I can live with most things not working as long as the car drives and the RADIO is functional. I am still waiting on the radio fix

Agreed, I was told by someone who knows, the car has 90 chips and 70 of them are programmable. They have a few test cars the staff are driving with many updates and they don’t want to get out of them. By year end we will all be in much different cars.

 

[amoroso6]

Has anyone gotten and driven the car with this latest update. Seems to be much larger than previous ones.

 

[abbas2099]

I will say it is nice to see 'auto-update' working with 1.2.19. Not sure why it didnt happen with the rest of my updates. Hopefully going forward it will.

 

[joec]

I will say it is nice to see 'auto-update' working with 1.2.19. Not sure why it didnt happen with the rest of my updates. Hopefully going forward it will.

Maybe some under the hood changes in one of these recent updates has resolved this issue for folks who had it?

I imagine they want to be sure when 2.0 does get released, all cars in the fleet can get it without too much trouble.