Lag in Driving Visualization & Adaptive Cruise Control Response

[spacefugitive]

Hi everyone,
I’m a new 2024 Lucid Air Touring owner, and I’ve been experiencing something with the Driving Visualization on the Glass Cockpit while using ACC that I’d like to understand better.

When ACC is engaged, the Driving Visualization seems to lag behind real‑world traffic behavior. Specifically:
- When a vehicle ahead of me slows down and then changes lanes, the visualization continues to show that vehicle in my lane for roughly half a second before it moves over the other lane.
- Because ACC still “thinks” the vehicle is in front of me during that delay, the car briefly slows down even though the lane is already clear.
- I’ve also noticed a similar delay when approaching stopped or slowing vehicles (e.g., at a red light). The system recognizes them later than expected, which leads to more abrupt braking than feels necessary.
- I haven’t tested how the system reacts when a vehicle overtakes me and cuts into my lane, because I usually take over manually to avoid creating a risky situation for myself or drivers behind me.

This happens 2–3 times during my commute, so it’s very repeatable. I can record a video if that would help others see exactly what’s happening.

My questions for 2024 AT owners:
- Is this normal behavior for the current software version? I am on the latest version (2.8.30)
- Does your Driving Visualization also lag slightly behind real‑world vehicle movement?
- Have you noticed ACC reacting late or braking more aggressively than expected?
- If this isn’t normal, are there any troubleshooting steps or settings I should check before contacting Service?

I’m still learning the car, so I’m not sure whether this is expected system behavior, a calibration issue, or something that needs attention. Any insight from more experienced Lucid owners would be greatly appreciated.

 

[tmichael]

Gravity owner here, so not familiar with Air or CCV vs CCV2. Is this a glitch or is this something the upgrade to CCV2 would correct? OP, do you have the gen 1 CCV or the newer CCV2?

 

[spacefugitive]

My AT was built in April 2024. So I am assuming it has the gen1 CCV. Is there a way to check this?

 

[tmichael]

My AT was built in April 2024. So I am assuming it has the gen1 CCV. Is there a way to check this?

Owners on LucidOwners report this method as the easiest way to verify CCCv2 without tools.

1. Put the car in a safe parked state.
2. On a phone/tablet, open Wi‑Fi and look for the Lucid‑broadcasted hotspot (only appears in certain service/engineering modes or when prompted by service, so you may need a service visit to see it).
3. Check the SSID name:
   
   • If it starts with “Android AP…”, you have CCCv1.
   • If it starts with “Lucid AP…”, you have CCCv2.

 

[Eagleye]

That behavior broadly matches what I see on my ‘24 AT.
I gather your main concern is whether your car is broken or needs something recalibrated, to which I’d say “no, they all do that.”
Only advice I can give is to lower your expectations of DDPro. I think it’s (now, finally) a pretty good ADAS system, but it’s not perfect.

 

[Buffalo Bob]

That behavior broadly matches what I see on my ‘24 AT.
I gather your main concern is whether your car is broken or needs something recalibrated, to which I’d say “no, they all do that.”
Only advice I can give is to lower your expectations of DDPro. I think it’s (now, finally) a pretty good ADAS system, but it’s not perfect.

I may be wrong, but isn't it possible that the OP does not even have DDPro, in which case the vehicle would not have the full sensor suite, or that the vehicle does have DDPro and Drive Assist is not engaged? The OP's questions are about Adaptive Cruise Control. Seems to me that, even with the visual lag, the OP might want to increase the vehicle's following distance by a notch. Overall though, it sounds to me like the system is operating out of an abundance of caution, which I would prefer to the alternative.

 

[spacefugitive]

I do have DDPro, and I use HFDA every day on my commute (for DFW folks, I drive 114 daily). That’s exactly where I’ve been noticing this behavior.

While I agree with the idea of using an “abundance of caution,” what I’m seeing doesn’t feel natural. The excessive slowing and abrupt braking might help avoid a front‑end collision, but it also increases the risk of being rear‑ended. With the current lag in the Driving Visualization and ACC response, DDPro ends up feeling more like a novelty unless you’re on a wide‑open interstate.

I’ll try to record a video on one of my drives. It should help illustrate the issue much more clearly.

 

[restonmaster]

What you’re describing sounds like normal processing latency between sensor detection and the visualization layer. The car may already be reacting based on radar or camera data before the display updates. However, the braking behaviour you mentioned is worth monitoring, and it might be helpful to check for software updates or calibration improvements.

 

[Buffalo Bob]

I do have DDPro, and I use HFDA every day on my commute (for DFW folks, I drive 114 daily). That’s exactly where I’ve been noticing this behavior.

While I agree with the idea of using an “abundance of caution,” what I’m seeing doesn’t feel natural. The excessive slowing and abrupt braking might help avoid a front‑end collision, but it also increases the risk of being rear‑ended. With the current lag in the Driving Visualization and ACC response, DDPro ends up feeling more like a novelty unless you’re on a wide‑open interstate.

I’ll try to record a video on one of my drives. It should help illustrate the issue much more clearly.

Thanks for the clarification. I figured that you might very well have been talking about Drive Assist, whether hands-free or not, but was confused when you called it Adaptive Cruise Control, which I imagine will perform differently on Airs with vs. without the DDP sensor suite. The terminology difference is important to any root cause discussion.

 

[spacefugitive]

I get what you’re saying, but this behavior shows up for me in both standard ACC and DDPro features like DA/HFDA. That’s why I’m leaning toward the root cause being in ACC itself. DA and HFDA are essentially layers built on top of ACC, so if the underlying system is lagging, the higher‑level features will naturally inherit that behavior.

 

[Buffalo Bob]

I get what you’re saying, but this behavior shows up for me in both standard ACC and DDPro features like DA/HFDA. That’s why I’m leaning toward the root cause being in ACC itself. DA and HFDA are essentially layers built on top of ACC, so if the underlying system is lagging, the higher‑level features will naturally inherit that behavior.

I really don't mean to belabor the point, but I imagine it is possible that ACC relies on all or part the DDP sensor suite, when available, so what you experience using ACC may differ, for better or worse, from how ACC will perform on a non-DDP-equipped vehicle. Just sayin...

 

[spacefugitive]

Yes, I’m not questioning your logic at all. But I do have the full suite of sensors — my car is equipped with DDPro. I have the paperwork to confirm it, the API logs, and Service has verified it as well.

I actually called Service a few minutes ago, and they suggested doing a deep reset. I’m going to try that and then take the car out for a drive to see if anything changes.

 

[socktucker]

My 26 has a laggy backup camera that can make it dicey to use. It could be hardware or software or they just don’t care, who knows.

 

[borski]

Owners on LucidOwners report this method as the easiest way to verify CCCv2 without tools.

1. Put the car in a safe parked state.
2. On a phone/tablet, open Wi‑Fi and look for the Lucid‑broadcasted hotspot (only appears in certain service/engineering modes or when prompted by service, so you may need a service visit to see it).
3. Check the SSID name:
   • If it starts with “Android AP…”, you have CCCv1.
   • If it starts with “Lucid AP…”, you have CCCv2.

That’s for which TCU you have (v1 vs v2).

I believe it may have been me that said it was CCC, and if it was I misspoke, sorry.

 

[borski]

My 26 has a laggy backup camera that can make it dicey to use. It could be hardware or software or they just don’t care, who knows.

I wish you’d stop ending every message with “or they don’t care.” It doesn’t add anything useful, and they clearly care. But up to you

 

[socktucker]

I wish you’d stop ending every message with “or they don’t care.” It doesn’t add anything useful, and they clearly care. But up to you

off topic, and if you say it fast, "hardware, software, or dontcare", made a funny alliteration lol I'm sure they care to a point. Doesn't mean they can fix it though. They can't even test mobile keys how are they ever going to fix a mobile key issues?

 

[borski]

off topic, and if you say it fast, "hardware, software, or dontcare", made a funny alliteration lol I'm sure they care to a point. Doesn't mean they can fix it though. They can't even test mobile keys how are they ever going to fix a mobile key issues?

They can and do test mobile key, they just do it on fleet cars, not customer cars. Also, they have diagnostics they can use; I know because they have helped diagnose mine and a friend’s before.

But to specifically test if something is wrong with your account, yes, they don’t have an impersonation feature (yet, perhaps).