Moving raycast off main thread

[JRuiseco]

I have some absolutely massive meshes and need to find the intersection of rays on the surface nearly continuously.

I did some testing of the existing system with octree, which is pretty quick, but absolutely demolishes my main thread.

Does anyone have anything I could read on the subject? I’ve thought about moving the raycast into a rust process, but want to leave that as the worst case.

[sebavan]

Is it possible to create a kind of avatar mesh invisible way more tesselated that you would use instead ?

[JRuiseco]

Thats a great idea.

I may be able to do that for on the fly measurements, and cast to the denser one once the user stops moving.

This is for an engineering design tool, so the precision of measurement is important.

[tlaukkan]

Hi, also need intersections for large meshes and been considering writing implementation with golang, rust or c++. Did you start anything and do you want to collaborate on this?

Some discussion here:

Octrees to find ray intersections in large static meshes

I am not sure if this is already implemented under the hood but I decided to ask away anyway. My use case is large environments and camera & AI agent collision detection. Doing ray intersects on large mesh is quite slow and perhaps applying octree on triangle level could give one or two orders of magnitude performance boost. This would work by placing mesh triangles in octree and find matching triangles by ray bounding box in mesh local coordinates. Then you could still move the mesh around fr…

Kind regards,
Tommi