Out of Spec 3 Row EV race - Lucid Gravity driven by Kyle

Perhaps posters in this thread can clarify their experience by including which areas of the US they are trying to utilize the HERE system..
I’m in Northern CA. Issues with Here nav
Have been seen going to east bay and to Sacramento/Davis so far.

And just to clarify, there are many things I like about Lucid’s native navigation. I think the layout is easy to see and use. I really like having full route lists (btw you can’t get that in the CarPlay Air version. Nor can my wife get the route list with the native BMW nav or CarPlay in her M50 - a huge complaint of hers). And overall it’s giving the right info. It could be more responsive. My biggest complaint is the routing in the highway and making you leave the highway unnecessarily. This is not a forgivable error when you are on a roadtrip. There should be a VERY high bar for a nav system to tell you to leave a major freeway and go local roads. But that bar is very low for Here currently and it’s usually completely wrong.
 
Perhaps posters in this thread can clarify their experience by including which areas of the US they are trying to utilize the HERE system..
I’ve used it in CA and have had no issues with it. What people fail to understand is HERE isn’t just maps, it plays a pivotal role in ADAS systems for
  • Lane-level geometry
  • Curvature, slope, elevation
  • Speed limits & sign topology
  • HD maps for ADAS / autonomous systems
This data feeds:
  • Adaptive cruise
  • Lane keep
  • Highway pilot systems
So if Lucid switches to Google so people can find their favorite burger shop out in the middle of nowhere watch them complain in the same sentence that DreamDrive Pro was horrible getting them to the destination.
 
It’s like telling an iOS person to switch to Android or vice versa. They’ll argue to the death of why their product is better and never see anything positive about the other.
And I suppose it's the "never see anything positive" part that just isn't right and should be challenged.
 
I’ve used it in CA and have had no issues with it. What people fail to understand is HERE isn’t just maps, it plays a pivotal role in ADAS systems for
  • Lane-level geometry
  • Curvature, slope, elevation
  • Speed limits & sign topology
  • HD maps for ADAS / autonomous systems
This data feeds:
  • Adaptive cruise
  • Lane keep
  • Highway pilot systems
So if Lucid switches to Google so people can find their favorite burger shop out in the middle of nowhere watch them complain in the same sentence that DreamDrive Pro was horrible getting them to the destination.
All of that is great. But if HERE can’t properly guide a driver to stay on a highway they should stay on, why should we trust it to do all the other stuff you listed? Basic functionality is critical before the more advanced features.

This seems to be a common failure of Lucids - whether it is key fobs or HVAC or navigation - they are trying to add the most advanced features without getting basic functionality right first. It is causing issues for many many customers, and also apparently for high profile reviewers of Gravity, as evidenced by the OutofSpec
Race, which had key, HVAC and navigation issues already.
 
Just a suggestion here, but this thread is about the Eastern Edge ev race, not HERE maps. There's another thread where it's discussed extensively. Also, it will be a moot point once Google Maps is offered to Gravity owners, like current Air owners. However, it's a public forum. Not trying to tell anyone what to say.

I mentioned the section in the ev race and Kyle's comment about the nav system in an earlier post only in response to another member commenting about him ignoring the system. A true statement from the member, but I just offered more comments from Kyle about the nav system for proper perspective.
 
Last edited:
Clearly YMMV.

The HERE maps/navigation on my Gravity has worked fine away from major interstates.
Even when I've misunderstood the navigation, the rerouting has gotten me back on course.
A valid and reliable system for me.

Hope things get better for you.

I think you might both be right - in the Air loaner they gave me when my Gravity was broken, I noticed the nav was several seconds behind real-time, making it difficult to anticipate or judge turns in city street environments. My Gravity does not have this issue.
 
Just a suggestion here, but this thread is about the Eastern Edge ev race, not HERE maps.
I agree, any new posts about HERE maps that are not related to the Eastern Edge race in this thread will be deleted.
 
And yet, at the 52:40 mark, Kyle says "Lucid absolutely nailed this route planner".
More praise of the mapping/nav system through the 53:14 mark.

Just saying ...
Turns out the bad routing issue was in the non-Kyle Gravity. At 2:18:55 you can see it:
Screenshot 2026-01-04 at 9.32.29 PM.webp
 
Route planning is different than navigation of that route.

His praise of the system occurred before the non-optimal off-highway routing.
Isn't it so that in the OoS races, they are mostly (almost exclusively) interstate bound? Also, are the recharging stops determined by the vehicle's routing or augmented by 3rd party tools (e.g., ABRP)?
 
Isn't it so that in the OoS races, they are mostly (almost exclusively) interstate bound? Also, are the recharging stops determined by the vehicle's routing or augmented by 3rd party tools (e.g., ABRP)?
Their rules change from time to time on different races. Here, they can take whichever route they like, as demonstrated in the video by the Escalade taking a different route off I95/I295/I395 corridors thru DC than the Gravity did. Also, they plan their stops using other apps, team knowledge and nav assist. They usually use the built in nav for routing bc it preconditions the battery automatically, but they generally will not route according to what the nav says as it's not designed, for any of EV really, to route for "racing" like the do at OoS.
 
Latest bugs:
• Overheating while charging limits charging speed
• Rolling the driver's window all the way up causes and auto-lowering of the window (Kyle: "Sun's up; Windows are out."
• Kyle editing bug: At abouts 18:30 the screen says "Escalade IQ" but it's from inside the Gravity, lol
• SC Gravity happy with their charging at 36:16 (at position #2). SC's limit them to the second lowest charging speed, btw. Efficiency, battery capacity, and charging in the sweet spot of the SOC curve.
• Both Gravity teams trust the car's predicted charge at arrival, and that seems to work out for them, even at 10MPH over the speed limit
• At 48:45, the Escalade team is surprised they're not doing as well as the Gravitys. I screamed at my screen: "Efficiency matters, dudes!" The Gravity has run the whole trip so far at 2.72 miles/kWh, which is fine but not superb. I think the Escalade was closer to 2.2, though. This at about 1300 miles into the race.
• Gravity runs with a towel over the driver monitoring unit, lol. Makes the car use capacitive steering instead.
• At 53:00, they have trouble turning cruise control on and setting the speed. Then complain about incrementing the speed, which I agree is sometimes hard, but press and hold for a 5mph jump is usually better for me.
• 1:07:00 or so, Gravity gets 400kW from 0-16% then it starts tapering. 384kW at 25%, 350kW at 34%, all still quite good.
• At 43% SOC, though, the car is thermal limited, charge rate is only 152kW.
• 1:09:10 the ID.Buzz team figures out some lock/unlock/charging interactions bugs
• 1:15:00 the entire BP Pulse station goes down, maybe caused by the Gravity. Kyle calls the other teams to let them know.

Posting now, will post another update as I continue to watch.
 
Last edited:
• From 1:15:00 to 1:27:00 multiple cars dealing with heat and switching stalls trying to find ones that put out more. The Model X team even pours cold water on the connector and cable trying to cool them down.
• 1:40:00 - Model X having tire pressure issues (too much due to heat)
• But at this point the order is still: Gravity, SC Gravity, Model X, Escalade IQ, Rivian R1S, Hyundai Ioniq 9, ID Buzz
• 1:44:00 SC Gravity running without climate control to conserve energy. They're baking with all the greenhouse glass.
* 1:47:20 Gravity backup camera still stuck on an image from hours ago
• 1:50:00 Car stopped, so they switched handles and it was fine.
• A few moments later, Gravity overheats and charging rate reduces.
• They shoot water into the front grill trying to cool it down, to no effect. So, they take off looking to cool down while driving and look for another charger.
• Then they lose 5 minutes waiting in traffic to get out of the parking log. Some sketchy maneuvers, not shown, discussed.
• After calling some engineers (Lucid I assume) they're going to go into Sprint mode to get more aggressive battery cooling. Interesting.
• 1:56:00 Gravity team decides to stop at a Tesla SC since that won't overheat things.
• 1:58:00 Gravity teams learns SC Gravity is stopping at the crowded Buckee's charger where Gravity team got stuck in traffic. Hmmm.
• 2:05:00 The Tesla SC the ID.Buzz pulls into goes into temporary closure (ouch!)
• 2:07:30 SC Gravity hits traffic but gets to a V4 SC
• 2:08:20 The Escalade IQ is still playing the charger swapping game, then the Rivian runs into a derated Tesla SC station since all chargers are in use
• 2:11:20 The Model X bribes another car to leave with $20, lol.
• At 2:15:00, Kyle explains that after talking with Lucid engineering, the overheating message isn't battery thermals, but probably charge port temperature. Kyle wonders if the adapter is bad (pins look OK). Data looks noisy to the engineers. Luckily, they won't need the adapters for their next 2 chargers, but thinking they can use the old water trick.
• 2:17:00 the SC Gravity is still in second place.
• The ID.Buzz is 2 hours behind the 6th place vehicle.
• 2:22:20 Gravity is running without climate to its second to last charging stop. Overheating forcing them to cut it close. A few minutes later they plug in and pour a little water (after previously promising Tesla they wouldn't do the wet rag trick), claiming it's the same as raining outside.
• 2:25:50 The Gravity team thinks they have a 40 minute lead! Cooling doesn't work, so they switch stalls. That doesn't help, though.
• 2:28:00 Escalade pulls into an Ionna stall near Daytona Beach, expecting great charging. Gets 345kW
• 2:30:00 Third stall doesn't help the lead Gravity, so they do the brake/2-button reset. And that works, somewhat. Kyle "It's always like that with Lucid. I love them, but the cars are not reliable." They end getting 150kW.
• 2:33:30 The Model X team doesn't think they can catch either Gravity, so they're focused on staying ahead of the Escalade IQ. At about the same time the Hyundai Ioniq passes the Rivian, but after charging they expect to swap positions again.
• 2:35:00 Lead Gravity still doing the plug/unplug thing, but struggling with charging, then changes stalls. And then the backup camera decides to work! And that final swap seems to work as they get 220kW. Then yet another headlight error. They burned 30 minutes, down to 10 minute lead over the SC Gravity
• 2:42:25 The Model X is charging well, but Tesla is reporting a 5 minute wait time for a stall, yet there are over a dozen stalls empty.
* 2:45:05 Model X team is about 35 miles behind SC Gravity, and about 50 miles behind the lead Gravity. Escalade is 40 miles behind, but they have a lot of juice in the tank.
* 2:51:00 ID.Buzz gives up on the SC station, goes to another charging location.
• 2:53:20 The reboot fixed the backup camera. Lead Gravity pulls into last charging stop.
 
• They go to 3 stalls before realizing that they need to pre-authorize in the app before plugging in at the Mercedes chargers. Good to know.
• They hold 400kW through 20%. Sprint mode makes a difference, Kyle thinks. Then 363 at 30%. Then, a charging de-rate. Eventually do yet another reset and get 385kW for a little bit. Then derate and then reset and recharge again.
• That drops them to second place, with the SC Gravity in the lead! With about 200 miles to go.
• BUT, SC Gravity has to stop to charge - and didn't tell the other Gravity team to make them sweat, lol.

I won't post more to not have spoilers.
 
• They go to 3 stalls before realizing that they need to pre-authorize in the app before plugging in at the Mercedes chargers. Good to know.
• They hold 400kW through 20%. Sprint mode makes a difference, Kyle thinks. Then 363 at 30%. Then, a charging de-rate. Eventually do yet another reset and get 385kW for a little bit. Then derate and then reset and recharge again.
• That drops them to second place, with the SC Gravity in the lead! With about 200 miles to go.
• BUT, SC Gravity has to stop to charge - and didn't tell the other Gravity team to make them sweat, lol.

I won't post more to not have spoilers.
Thank you for all of the detailed summary. Super helpful and MUCH better than having to watch and listen myself.
 
so if you add the 5 videos
Pt 1 Getting the EV's to Maine 2:44
Pt 2 Intros of drivers and cars 1:06
Pt 3 Pt 1 of race 3:17
Pt 4 Pt 2 of race 3:35
Pt 5 Finale 4:18

Thats 15 hours

If you were to watch the entire LOTR trilogy extended directors cut you'd spend 12 hours

I mean it depends on what kind of nerd you are I guess
 
Back
Top