I reproduced the issue using generate measurement from predicted using smoothed measurements, it has been fixed for the next build.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.