|
From: Richard H. <rj...@za...> - 2019-03-07 15:29:52
|
On 3/7/2019 9:02 AM, Tim Moore wrote: > Do you think it's practical to get to a point where both the legacy > and compositor CameraGroup classes can co-exist at runtime? I'd always imagined that we would replace the legacy rendering with compositor; this will then allow us to clean up a lot of the hardcoded stuff that sets up the pipeline, remove the Rembrandt code and generally have a good tidy up. There is a new scheme that Fernando is currently working on whereby we have a definition of the effects/shaders within the pipeline keep them within the pipeline folder structure; together with defining what the shader does (if applicable) so it can be controlled by a future UI. There is a very rough draft design doc for this available here http://www.zaretto.com/sites/zaretto.com/files/compositor-effects-registry.pdf ----------------- [1] although most of the Rembrandt code in the core is actually concerned with setting up a pipeline much like compositor and mainly Rembrandt rendering is in the pipeline definition and the effects/shaders) |