julex: i'm working on implementing a heatmap grapher for x,y,z data that might help.

it wont be 3d, because heatmaps are easier to generate

Accuracy? Not likely since now I am using only one map with arguably lower resolution (KFLF). Maybe using KFKHFM would give more resolution but adjusting that map also directly affects load ECU is seeing.
Simplified? Hell yeah. You see how the fueling behaves by looking just at one map instead of going back and forth between two maps.
Does it work? Yes, very well. Just like on RS4.

Previously you could not just follow KFKHFM or KFLF and assume that if a given cell dips in value, the multiplicative product does the same as frequently a corresponding cell in the other map would go up and vice versa.

You have to keep in mind my special circumstances though. I am not running stock intake. I am not even running original Hitachi MAF. I am running custom intake comprising of AEM cone filter embedded in daringtaked stock S4 air box, 3.5" aluminum tubing for mustang 90mm MAF and HPX MAF element. From there it becomes "stock" RS4 accordion hose and then normal allroad/S4 intake to K04s and rest is pretty much stock.

You have to keep one thing in mind though. Audi felt that it is ok to not use KFKHFM table for RS4 equipped with "just" 82mm (or whatever it is) bosch maf and regulate any irregularities of engine fueling exclusively via KFLF map.

So is this thread going to pioneer the integration of a WBO2 sensor now as well? 

I saw some Audi TT CB box maps where KFLBTS is all 1. So how is this box providing enrichment at higher loads other than through kfdlbts and kffdlbts (which i guess is active only when the engine knocks).KFLAMKRL and  KFLAMKR also is all 1. So what if there is no knocking.
Also supposing my FBSTABGM = 0.5, kflbts = 0.7 , kffdlbts = 0.6, Kfdlbts = -0.64 ,how will I calculate my LAMBTS.
Thanks

Lot's of people seem to be not understanding this very crucial piece of info. . This is what makes fueling via KR viable as main fueling path.

dunno about that. The fact is that you can only shift from higher to lower load in an instant. The other way around takes time. However, even if true, you're assuming ECU is somehow lagging in its load calculations which if true, would ruin your engine many times over to date.

The ECU calculates load out of mainly MAF flow and then does some modeling as to how all that air behaves before it even reaches our cylinder. Injection time is also a real time calculation affair which is calculated by looking at air flow and tons of other variables including all the lambda paths. Simply there is no such thing like fueling "lag" which you're trying to use as an excuse to employ LAMFA.

I used LAMFA only for couple of days and not as main focus of fueling effort (only to pre-fuel the engine when testing KR feling), like you are trying to, and I believe that I could not really use it properly as that map seemed to fall victim of multi-point interpolation where I wasn't getting as low of a Lambda as I wanted in my table but something higher slowly falling with time spent at the driver's requested load level. Many maps don't use absolute values at a given point of table but are interpolated and mean weighted with the adjacent points so if your LAMFA falls to say 0.75 at 100%, it won't immediately dump 0.75 value into Lambda path once you hit 100% driver load  but will actually lag and gradually approach the 0.75 you want. But it might take a while.

Again, that was my observation, I believe, but maybe I am all wrong about LAMFA after all. It just has no use anymore with "0.00" knock path in KR lambda

The question is why do you want to go rich BEFORE load ramps up uncontrollably at that (because you will set the fueling blindly without any knowledge of actual fueling conditions) and not DURING the load ramp up... All you need is DURING - hopefully controlled so that you get as close to 12.6 as you can where you get best torque out of cylinder.

But to each their own. I like the KR because it allows some degree of flexibility for ECU to choose the highest AFR, table allowing, not just bringing everything to lowest denominator of "worst case scenario (lowest) AFR I feel safe with" as other ways of fueling usually are set up.