Removed RaytracingRenderer

[mrdoob]

No description provided.

[EliasHasle]

Presumably to focus the scope of the library? Will the RaytracingRenderer migrate to somewhere else?

[Mugen87]

It seems it's better to implement such a renderer on top of three.js in a separate project e.g.

https://github.com/erichlof/THREE.js-PathTracing-Renderer

[donmccurdy]

See issues like #18277, too... the raytracing and deferred renderers were incomplete or proof-of-concept-ish in ways that made them impractical for real use, IMO. It's hard to communicate that expectation to users — many things in the examples/* folder are production-ready, and some (loaders, controls) are practically indispensable for many projects. And maintaining multiple production-ready renderers would be a huge undertaking. So I think removing them probably helps to steer users to the more reliable workflows.