R2 Launch Mode demo by Wassym -- 0-60 in 3.45s. Coming to R2 in next OTA update

[savethemanual]

Looks like minimal torque steer compared to R1S too, fun times!

Sponsored

 

[Zathras]

So much entitlement. There are no doubt scores of reasons why some things come out early and some things come out later. Unless you're an automotive engineer, or a software developer, the reasons are going to be above your pay grade.

As for the question about holding shipping vehicles for an update, that is clearly not going to be the case. These cars are software-based, and Rivian is constantly talking about how software updates are going to come throughout the life of the car. So there is zero reason to hold up shipping for pet mode, Launch Mode, quieter turn signals, garage door openers or anything else. Now that the vehicle is shipping, holding back for updates is not going to happen. (Unless some massive bug is found.)

So why are shipments not up to some people's expectations? We have no idea. But one thing I'm pretty sure is the case, there are a lot of people who are getting cars who are not posting VINs here or anywhere else. The number of people who have ordered and reported their progress here is a teeny tiny slice of the number of people who are in fact getting vehicles.

 

[Dark-Fx]

What is the point of this and that whole animated UI? Is it just for racing?

Personally I’d rather see them spending more time on more useful software features like text integration with iOS, adding more apps to Connect+ or knocking items off their Coming Soon checklist:

“The following features are expected soon via a subsequent OTA update”

• Rivian Assistant
• Gear Guard suite
• Vehicle hotspot
• Garage door opener

Hope you're cool with them implementing this because those other things are already done.

 

[DuoRivians]

What is the point of this and that whole animated UI? Is it just for racing?

Personally I’d rather see them spending more time on more useful software features like text integration with iOS, adding more apps to Connect+ or knocking items off their Coming Soon checklist:

“The following features are expected soon via a subsequent OTA update”

• Rivian Assistant
• Gear Guard suite
• Vehicle hotspot
• Garage door opener

Speed sells, and Rivian is trying to tap into the speed market as much as possible

 

[rodhx]

Hope you're cool with them implementing this because those other things are already done.

Are they? Those are all still missing in R2 at the moment, right? That’s why my take is the OS 2.0 feels like my R1T OS circa 2022 but with new GUI. I can’t fathom why features that we added over the past four years are missing in the initial 2.0 release. Especially something like the garage door opener.

 

[emroch]

Are they? Those are all still missing in R2 at the moment, right? That’s why my take is the OS 2.0 feels like my R1T OS circa 2022 but with new GUI. I can’t fathom why features that we added over the past four years are missing in the initial 2.0 release. Especially something like the garage door opener.

This has been discussed ad nauseam in other threads... software is hard, and validating new software in a 2.5 ton metal death machine takes time. The product must ship on time, and safety critical components cannot be delayed, so non-critical stuff ends up getting pushed out.

As for whether these are done already, keep in mind that there is probably a deployment pipeline so once the individual engineers are done writing the code for a feature, it still takes time for it to go through testing/validation and get packaged up with other updates for the OTA release. During that time the engineers can be writing the code for the next feature, even though the first hasn't made it to customers yet.

 

[rodhx]

Software is hard, that is why not having the solutions for problems already solved is weird. Especially basic functions that us OG early adopters saw implemented over time and now have to wait to be implemented again. The logical baseline is OS 2.0 would include features from its predecessor, per the usual in software development.

 

[bnolan]

So much entitlement. There are no doubt scores of reasons why some things come out early and some things come out later. Unless you're an automotive engineer, or a software developer, the reasons are going to be above your pay grade.

Ha ha., I am a software engineer
By and large, you prioritize development of features that are either low hanging fruit, that are going to help drive sales or give you a competitive advantage. Sometimes you let the engineers do stuff they find fun to keep them happy.

I’m sure Rivian has their reasons for developing this. Just seems odd given the lack of parity with R1 and other more mainstream features. Maybe this was someone’s fun side project. Who knows.

Just seems odd when this is supposedly your make or break vehicle to be dedicating resources to such a niche feature like this which likely only appeals to maybe 1% of drivers (and probably even less will ever use it more than a handful of times).

Unlikely it will lead to any meaningful increase in sales over getting feature parity with the R1 and/or competitors.

Or increasing the value of your paid Connect+ offerings to make that subscription more enticing to customers.

Maybe it’s just me, but these seem like development money better spent.

 

[godfodder0901]

Software is hard, that is why not having the solutions for problems already solved is weird. Especially basic functions that us OG early adopters saw implemented over time and now have to wait to be implemented again. The logical baseline is OS 2.0 would include features from its predecessor, per the usual in software development.

Not when you have a completely different platform baseline. There is very little hardware shared between R1 and R2, and all of that integration that made it so hard to deploy on R1 has to be done all over again on R2.

 

[Electron]

If this is without rollout, then its about the same as the MYP. Great job Rivian.

The new MYPs are pretty quick pulling low 3s. The new 3/Y pull a lot harder than the previous gen as well. These two would be a great head to head race to see.

I haven't followed the R2 too closely. Is the max speed limited to 130?

I remember early R1 Quad videos showed a higher top speed, but we didn't get it due to limitations (113mph or something). And I also don't remember if with the new launch mode in R1, does it allow you to temporarily go faster than 113?

Wonder if the R2 will also be limited.

Gen 2 R1s with launch mode does 130MPH.

Hopefully, launch mode will be less harsh on the R2’s half shafts

I wonder if they're 16mm like in the Gen2 R1s? (Gen1 had 14mm iirc)

What is the point of this and that whole animated UI? Is it just for racing?

Personally I’d rather see them spending more time on more useful software features like text integration with iOS, adding more apps to Connect+ or knocking items off their Coming Soon checklist:

“The following features are expected soon via a subsequent OTA update”

• Rivian Assistant
• Gear Guard suite
• Vehicle hotspot
• Garage door opener

I agree. Like pet mode at launch.

Never been a fan of the launch modes. Don't see the point. Just give us the full juice when we are sitting at a light on autohold. We should see the max potential 0-60 just flooring it at a light. Launch mode is just dumb unless you have adjustable suspension that can get you max traction.

I'm with you. If it's in Sports mode just give us the full juice. In the R1s with air suspension, a Launch mode button to quickly drop the car would be more than sufficient.

I've dusted many loud for nothing cars at the stop light. Before I roll up I change it to Sport and set it to the lowest suspension. If this was just one button that'd be nice.

 

[emroch]

Software is hard, that is why not having the solutions for problems already solved is weird. Especially basic functions that us OG early adopters saw implemented over time and now have to wait to be implemented again. The logical baseline is OS 2.0 would include features from its predecessor, per the usual in software development.

An architecture change means the previously implemented features or "already solved" problems need to be rewritten or at least adapted for the new system. The reason you often see software ship with feature parity is because they simply didn't ship until it was ready. R2 is make or break for Rivian - missing the shipping date was not an option. Whether they were not at feature parity on time because of unforeseen troubles, staffing shortages, or just aggressive deadlines, it doesn't really matter. They had to prioritize finishing the critical components by the ship date and let the non-critical things get pushed back, even if they were relatively simple.

For all we know, the garage door opener and vehicle hotspot could be identical to OS 1, save for any UI differences. The fact they are delayed doesn't necessarily indicate that they required more effort to reimplement, but simply that whatever effort they did require (perhaps as little as simply verifying the previous implementation still works) was de-prioritized until after the car shipped.

 

[SANZC02]

Seems like a moot point arguing about these delayed features. They will be in the vehicle long before the majority of people have the R2 in their driveway.

 

[mdpa]

0-60 in 3.45s

100mph in 6.99 & 1/4 mile in 11.33

It was great to see this posted on X. 11.33 in the quarter mile is very impressive and the first time I’ve seen actual performance specs beyond 0-60.

 

[mdpa]

Is the top speed the same for both tire options on the Launch Edition?

 

[emroch]

Is the top speed the same for both tire options on the Launch Edition?

Both tires have the same V speed rating (149mph), so I doubt they'd have different top speed settings. I'm not sure why they chose 130mph - there could be another component rated only for 130mph, or the 19"/20" AS tires have a lower speed rating, or they just wanted to leave some buffer.

Sponsored