I know this is kinda old, but here I go anyway!
Quote:
I also think that the 3d view shouldn't be a series of blocks so to speak, it should be like traditional 3d views found in other tuning applications.
+1 I opened RR at 5am the night before last after a very long day and poked around and this was possibly the weakest point?
qoncept wrote:
Ok, what about color scaling? Currently the entire table is read and scaling is figured between the highest and lowest values actually found in the table.
I hate this, though I can see why some like it. So it likely needs to stay with either a per table override option or a global preference or both.
Quote:
Does it make any more or less sense to skip reading the whole table and scale colors from the highest to lowest possible value?
YES! Absolutely

One reason is that when you open, for example, an ignition timing table, at a glance you can see if the whole thing is retarded, advanced, which bits are extreme, or not. When it's auto coloured there is NOTHING that you can tell at a glance except relative shape. Even that is useless, though as the colour range would be the same for the same relative scalings if it were 1 - 1.1 or 1 - 1000. See above re making this globally preferred and per table override-able.
Also, as you stated, you don't have to iterate through the entire table looking at all values to determine the colour scaling on EVERY edit, this way, so there is a huge performance increase, even if it's not noticeable on faster machines doing slower edits.
I have another suggestion that seemed to be lacking, too. Perhaps I'm just not seeing it, though. Or perhaps OEM tune setups don't have much of this. What about groups of single parameters. It would be nice if you didn't get a table view for things that are not a table. If you could have a category type of "single config items" then you could group related settings together and view them more sensibly as a key/value list or similar. If I'm blind, please help

Perhaps some of that is useful!
Fred.