`wp.mesh_query_point` throws access violation

[cadop]

I think there are some nuances to this issue and this is my best guess.

As the title stands, I could see an argument for saying its not a bug. However, there should be a better error. Or instead, when creating the mesh, find a way to check if it is invalid upon creation.

even though I turn on debug mode and breakpoints in vscode, the only thing I can see is access violoation on the original launch. it was by trial and error and commenting out things until I got to where it seems to happen.

[cadop]

The issue was that the positions of the mesh were not on the same device as the kernel (or the point being referenced).