The current E60 allows you to switch from AM to FM or whatever via the steering wheel programmable buttons.
[/quote]
Yes, E65 is the same. That doesn't really address the problem.

 

The current E60 allows you to switch from AM to FM or whatever via the steering wheel programmable buttons.
[/quote]

Right - it's lightning quick too - I can hit the button rapidly 3 or 4 times and it cycles through the inputs with no lag at all.

 

iDrive ...

Concept = good.

Execution = not so good.

 

i like the i-drive. The computer system is where the problems happen, not necessary the GUI. It's just the code is very faulty. Not enough beta testing. They're on version 18 already, that's not including all the .1 and .2s

 

I don't know - it's remarkably good considering the scope of features it needs to contend with. Also, again... are we talking about gripes in iDrive or software bugs in other systems?

 

I think a few more keys would be nice. The whole debate of using a mouse instead of a touchscreen applies here. Most other manufacturers are going the route of a touchscreen. I think it is a better user interface than the knob, but that's me. Computer screens to aceess the many functions cars have are here to stay. The knob (Idrive) is still debatable. I think a touchscreen is much better suited to consumer products. Try to input your password into your voicemail while driving using Idrive. It is a PITA absolutely...

 

The CIP software packages are not just for E60 but all models. Some versions contain nothing new for E60. So the fact they're up to 18.x doesn't imply lots of bug fixes. A lot of code is is just fine but translates to odd behavior in real world. That's not necessarily a bug but points to fine tuning needed. What they really need is for programmers to see immediate impact of code changes. Of course, that's kind of difficult with a car.

 

Red's contention about speed of response is spot on. If u added buttons for some direct switch to another function, but it came at the same speed we have now u would have the same problem. All of us on Windows products experience that "not sure it recognized my input request" and so hit it again and again, the net result it tries to respond to each request. If we could get near immediate response to changes even through the iDrive knob it would be a huge breakthrough. Whether this takes processing power, bus speed inprovements, memory increase or any combination I don't know or care.

 

My non-Nav car has the response you are asking for, but I suppose the speed differences are already known between Nav and non-Nav implementations.


As for implementing a touchscreen - I feel this would introduce a placement compromise. I like the location of the iDrive screen, but it would be impossible to reach and touch easily while driving. It would have to be moved if it was an input device as well, which would likely draw the driver's eyes from the road.


I've posted before that I think the knob should be replaced with a small input pad that responds to programmable gestures. It would require a very high level of driver savvy to master, but would ultimately prove the most flexible and functional. This company makes keyboards and input pads that do what I'm describing.


http://www.fingerworks.com/

One of my friends has the keyboard. You can program it to respond to chords (multiple finger presses in a certain position), gestures (sweeping motions starting in a giving position and ending in a given postion), and other types of tapping. This allows for almost an infinite number of unique inputs from a faceless, flat surface that could permit direct access to any number of dedicated functions.

An article that helps clarify some of what I'm talking about:


http://wired.com/news/gizmos/0,1452,58978,00.html

 

I drive is just the user interface. without it we would still have all the computers and computer related problems that ever high end car is prone too. in the last 6 years, I drive has come a long way, I expect it to continue to be refinded with each release