Also, can someone assist with the correct tunerpro screenshots to add the table KFLAMKR?    That still seems to be missing.  Julex can you get screenshots of the actual KFLAMKR table values you are using?  I know you already posted your KFLBTS and KFLAMKRL, as well as telling us that you are using LAMFA set to all 1.0.

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

S4 M-box KFLAMKR for your viewing pleasures is attached.