|
It is because your boost is overshooting the requested. Scale the boost factor multiplier or reel in the wgdc base to keep it on target. Timing is connected to boost and you will see a global reduction when boost is significantly overruns the target. Logs look good otherwise. When I experienced this phenomenon the timing reductions didnt show up as corrections (read 0.0). I think timing reverts to the safe table when this occurs.
|