4.17 to 4.18 migration broke auto lod distances

As said in title, after migration from 4.17 to 4.18 auto-lod distances are corrupted (engine stays on LOD2 until you approach really close to the mesh) and get fixed only after ticking “Auto Compute LOD Distance” again.
To reproduce this issue download the official kite demo and open it in 4.18.

I have experienced the same problem, thanks for the “Auto Compute LOD Distance” work around. Petty you have to do it for so many assets.
Thanks again.