Who is the target audience of this video? None of their customers (and certainly no Jackal customers) are actually going to understand anything they said. Why use the binaries where there will now be constant accusations of theft rather than just using logs, which present a more accurate picture of what's actually going on?

The file they were looking at just looks like a typical file service file with a bunch of needless limiters removed to make things easy for training wheels tuners plus all of the usual hackery and fudging used to bypass the pre-Simos18 airmass variables capping out, combined with typical low-effort hack job tuning like only changing the last row and relying on interpolation rather than rescaling axes to get resolution back. Certainly it is junk but not any kind of abnormal junk.

I think that they wanted to show off and flex about having an ASW patch to deal with the airmass variable saturation issue and perhaps the other torque reporting issues, but they didn't want to "give it away" by actually saying what they do. So instead they danced around by BSing a bunch of random and somewhat irrelevant stuff. None of their actual explanations were really well thought out, and they never actually showed anything (like logs!) to back up their assertions. For example, they showed a bunch of fudged airmass maps (this is the normal hack way to do things on pre-Simos18 Continental ECUs without an ASW patch) but didn't show the actual resulting torque reporting in an actual driving situation.

I don't think they're wrong about Jackal tunes being low-effort file service grade junk, but their method of "proving" it and their resulting video seemed wildly off base to me. If I were them I would have done some pulls in a Jackal car and done a detailed second-by-second log analysis with a clear explanation to the potential customer about how the Jackal tune wasn't performing correctly, rather than going into a bunch of irrelevant calibration ranting.

I did get a good "nut swingers and trolls" meme clip video out of it though so I'm happy.

Logs would have been a good idea, that would have been obvious proof of the torque reporting problem. I take for granted my knowledge of the torque reporting and dsg operation correlation because of what i learned about it. Majority of people who watch the video don't understand what they are looking at so I think it misses the mark a little bit. Pretty clear in B8 groups its become a tribal issue now.

So they bought a tune file and map pack from an ols supplier and made it "better" by giving it the ff treatment. Neat.