Feature request: `Object3D.inFrustum`

Description of the problem

The idea is to cache camera frustum checks on objects (a) to avoid recalculation and (b) to offer a simple interface.

As pointed out in https://stackoverflow.com/a/29424745, when .frustumCulled is enabled, .inFrustum could be populated as part of the frustum culling.

I would be happy to put up a PR if there is interest in the feature.

[Mugen87]

Well, yeah this could be a problem. Against this backdrop, inFrustum is indeed better. Especially since we already have Object3D.frustumCulled. So I think we can expect that users at a certain level of experience are familiar with the term “frustum”^^.

[Mugen87]

I don’t think a feature of the library needs to cover all eventualities. The project often introduced enhancements (e.g. like Material.onBeforeCompile()) which provide benefits for a lot of basic use cases. Like I said before, topics are often made too complicated. I see no reason why we should not start with something simple which can later be replaced with something more sophisticated.

An aside but when do you consider it correct to introduce a new member function for a callback instead of an EventDispatcher callback like dispatchEvent({ type: ‘becameVisible’ })?

This is a personal preference.