2010 Lexus Is 250 on 2040-cars

Auto blog

Lexus boots up early NX configurator

Lexus is ramping up to launch its NX luxury compact crossover. Its international website just launched a teaser page for the CUV that shows off the available models and some nifty new photos of the upcoming vehicle on location. The site also includes an early configurator to allow potential customers to imagine their future NX.
Unfortunately, the configurator is quite bare bones at the moment. It only allows users to choose from 4 trims, 10 colors and 3 wheel designs. You can't do anything to the interior, and there are no options. Pricing is still a mystery as well.
We do know that in the US the NX is offered with either the company's new 2.0-liter four-cylinder, turbocharged engine with a six-speed automatic or a 2.5-liter four-cylinder hybrid powertrain. The F Sport package is also available with either engine for a dash more sport in your crossover.

Lincoln MKC crossover adopts the Continental's grille

The last vestiges of the controversial split Lincoln grille are slowly being removed as the company revamps its lineup. It started with the MKZ and Continental, with the most recent rhinoplasty recipient being the Navigator. Now, based on spy shots, it looks like the MKC crossover will be the fourth to get the new corporate grille. Under the heavy vinyl coverings, we can clearly see the proud Continental-inspired grille. We can also see that it will feature the same chrome mesh with Lincoln badge-shaped openings found on other cars with the grille design. We can also assume that the headlights will receive a substantial refresh, but the lower bumper doesn't look particularly different. The rest of this prototype MKC looks the same as the existing model. The back is covered, which indicates that the taillights may be updated. We wouldn't expect a radically different look, since the MKC already has a full-width taillight treatment. We also noticed that the wheels appear to be inspired by the cool turbine wheels of the Navigator. Whatever the other changes are, we'll probably see them soon. This is clearly just a refresh, and so there's a good chance we'll see the production model revealed by the end of the year, or early next year at the latest. Related Video:

Google shares more details on self-driving car accidents

Google has pledged to release monthly reports on the status of its self-driving car program, and says these updates will include information on accidents involving the vehicles. But the company won't release the actual accident reports, a sore point for activists who recently have clamored for the company to be more transparent in the way it tests this promising technology on public roads. "Google is dribbling out bits of information in the hope to silence legitimate calls for full transparency," said John Simpson, privacy director for Consumer Watchdog, a nonprofit that has asked Google to release reports from the 12 accidents the company says it has been involved in over the past six years. "They are testing on public roads, and the public has a right to know exactly what happened when something goes wrong." Under California law, the accident reports are not considered public records. Google has attributed all accidents to human error, and says drivers of the other cars involved caused 11 of the 12 accidents. In eight of those, the Google cars were rear-ended, and the autonomous vehicles were sideswiped in two other crashes. One of the accidents occurred at an intersection when a human driver failed to yield at a stop sign, and in one incident, a Google driver accidentally rear-ended another car while manually driving. Google had previously provided those details. The first monthly report installment sheds new light on which types of self-driving vehicles were involved, directions of travel, locations, and whether the cars were operating in autonomous or manual mode. Update: Google says this information comes directly from the OL 316 forms used to report accidents involving autonomous cars in California, though it has "edited the summaries lightly to protect other drivers' information." But Google still will not release the original OL 316 forms, nor the "traffic collision report" forms used in California to report accidents. Another company that has been involved in a single self-driving car accident, Delphi Automotive, has released this information, which verified its car was not at fault. Regarding Google, Simpson said, "We now know a few more details of what happened. The problem is that it's Google's version and they want us to take their word for it." The Google self-report adds information that goes beyond accidents, with further details on the company's overall program.