Adding load columns and RPM rows to maps
Just with the 96530706?
I can't wait for this V7 to come out!
I originally had the 94170008, and changed to 94170015, so I will need to change to 96530706 now? When the V7 comes out to get BIGMAP?
a compelling reason would be you have to make significant changes to get 96530006 to run on your 94170015 car...
at the moment the only thing thats been raised is the revhang stuff, which can be fixed using tables.
at the moment the only thing thats been raised is the revhang stuff, which can be fixed using tables.
Ugh, I should never post when I'm tired, I screw up things like "word definitions" and "sentence structure". 
The table lookup itself is fixed-cost, ie. O(1), but each axis lookup is a search over the width or height of the table, so a maximum of O(n), but no worse. You had it right. 
The table lookup itself is fixed-cost, ie. O(1), but each axis lookup is a search over the width or height of the table, so a maximum of O(n), but no worse. You had it right. . With what Ceddy says seems its moot 
so it is ok to change the 11k value at the end of the RPM stack right? I had posted a while back and it seemed fine but i find it odd it is like that. Not sure if there is a specific reason.
I see no reason why it couldn't be changed. Once the RPM exceeds the last known RPM value on the list, it just holds the last known settings in the map, which would be the last row of data.
The ECU doesn't cut spark above the rev limiter. It's likely mapped out that high just so it has a known value should the motor be beyond the rev limit. Otherwise, it would have to extrapolate, which is never a good thing. There is no need for that on fuel since it cuts fuel above the limiter.
That would be my guess.
That would be my guess.