Sent this to Ryan with my revision: I may have conceded you too soon. I found and exposed an inverse torque load clip and it was exactly what was active holding the car back in my last test. I then learned that it’s already exposed and I was always in BASIC view.

but I’m exposing definitions perfectly.
I see you set it to 3.0 load. Maybe previously wondering why the car was holding back? I think it’s an excellent safety limiter so I ramped mine up to 2.0 load around 3,750 rpm then it’s all 2.1. In case it wants to overshoot it’ll get clipped. To me that’s perfect.
My Driver demand max 500 request is going to make about 1.8 load bc it should end up about 560-580 on IT and 1.8 range on inverse. Your explanation was too simplified there’s no log or file that supports a max driver demand request cutely landing on IT and inverse load.
I also completed my training for advanced parameters and have reset the dead system DTC’s in the new file DMJKB52. As well as disabled my annoying TPMS light in Forscan.
I’ll be testing what my Driver Demand can really do on the next test. Again my OSS is smoothed to give my cautious foot near max and as I press it more it’ll just be the max and never exceed my max with my earlier multiplier. So we will see if you were accurate. Does my 500 DD land at 1.6 load or 1.8? Only one way to find out