WOT tuning work flow question

Back in the day when tuning with HPTuners on GM vehicles I would use Mega Log Viewer to build a table that would be the % difference of target lambda to actual (using an external sensor and a USB logger). The axes matched the VE table, so I could simply copy the table and then multiply it by the VE table for my new VE table. If I recall I did that all in excel. A couple rounds of that and it was really close with mostly smoothing and extrapolation to corner cases.

Up untill now on my M150 I have only used quick lambda. But I have some need now to possible tune an engine while not being there via the log. Other than carefully going through the log and making manual changes, is there a way to do something similar to what have done in the past directly with i2/M1 tune? Would be nice to pick a piece of the log (WOT for example) and do a quick lambda for all sites in that section of the log

Using Tune 1.5 and i2 Pro it is possible to have the main data selection in i2 present as the telemetry data in M1 Tune.

If you log the correct channels this would allow you to use log data to tune the efficiency table using the Q function as if you were online with the ECU.

Thanks Scott. Ive been lumbering away with 1.4. Originally when 1.5 came out I was on a really high resolution laptop and it didn't play nice with it. I need to revisit this.

I'm using a 4K monitor 16:10 laptop with the scaling set to 175% and it's working as expected. What resolution and scaling are you using?

2560 x 1600, but high pixel density (13" display). It was also touch, obviously unrelated to display directly. Fortunately (unfortunately) that is in the past. The laptop went for a short ride on the roof of a race car, and I am now on a 14" 1440 display by a difference vendor. Going to download 1.5 and play with it.

I am sure my issues could have been resolved, but I was at the track staring at the laptop trying to sort out that glitch, plus try to remember the 1.5 training. easier to revert back at that point!