Garrett Johnson

> It would be great to be able to start the examples directly from the downloaded repo. The setup and run instructions are listed at [the bottom of the README](https://github.com/gkjohnson/three-mesh-bvh?tab=readme-ov-file#running-examples-locally)...

Sounds great @Spiri0! Thanks for taking a look at this. Looking forward to having this in the project.

> This is due to the paths. I adjusted them for a few examples, and they then work again. Lets create a first PR with r178 and this new example...

@TheBlek struct, functions, and an example for compute shader raycasting has been added in #756 and will be available in the next release compatible with three.js r179 next month. The...

Just got back home and tested it with a mouse - as you allude to in https://github.com/NASA-AMMOS/3DTilesRendererJS/issues/788, I'm seeing that the drag point shifts as you move the mouse around....

Closing this for now - happy to get a version merged if we can get one going that doesn't break some of the existing zoom behavior.

> I was wondering if the error message shouldn't be factorize in function ? > validateInstanceId(instanceId, drawRanges) > validateGeometryId(geometryId, drawRanges) I think this is okay to do - it should...

Thanks! Would you like to make a PR with the change?

Hey @TheBlek - thanks for the contribution and sorry for being slow on the response here. I've been preoccupied on other projects but I'll try to be more attentive here....

I don't recall exactly where the current algorithm is from - but for the most part it was made with a focus on speed of execution. Though of course, at...