Hi @wakecarter, looks like the input to setPos() is taken through toNumerical() for sanity checking. That the latter is throwing means it is working as expected I believe. I would need to look closer to determine why ypos comes up NaN in the first place, but for now you should be able to use Number.isNaN() instead of the auto-translated ypos === NaN to check if ypos is usable or not, x
2 Likes