VE analyze writes to wrong table?

[lutorm]

I'm attempting to use MLVHD to do a separate VE analyze for both my cylinder banks, since I'm using the "dual table" option (this is MS2 3.4). Each bank has a separate wideband sensor, logged as Lambda and Lambda2.

In VE analyze, I pick veTable1 and AFR, run the analysis, and it calculates what looks to be a correct VE table 1. Then I repeat this with veTable2 and an "AFR2" that I calculated as Lambda2*14.7, and it looks like it calculates a correct VE table 2. However, when I click on "save tune" and open it in TunerStudio, what I have is a veTable1 that is the 9 lowest load rows from VE table 1 and the 7 higher load rows are the 7 lowest load row from veTable 2. VE table 2 is unchanged.

Is what I'm attempting to do not possible? It looks correct in MLV. I've attached the resulting msq, but the tune file is too big.

Also, is there a way to get VE analyze to use lambda instead of AFR? I find it jarring to suddenly look at AFR values when Tunerstudio is set to work in lambda.

Thanks,

/Patrik J.

[LT401Vette]

Something seems broken here. I have reproduced the problem with your msq.

[lutorm]

Something seems broken here. I have reproduced the problem with your msq.

Ok, cool. I can work around it by exporting the tables and importing them in TS, but it would be nice if it worked.

[LT401Vette]

This is fixed for next release.