I'm on the same boat with lacilaci, plus I need to be able to trade realism for speed, not just fake things, so I need a lot of flexibility. But as the voting shows, very few people need these flexibilityDade wrote: ↑Tue Oct 08, 2019 5:51 pmThe problem is not that I don't want to fake, it is that we trace light in both directions (i.e. backward and forward, from eye and lights) plus we have very often MIS (i.e. we trace the same path in different ways).lacilaci wrote: ↑Tue Oct 08, 2019 4:28 pmJust yesterday I had some werid crazy request on removing some shadows and reflections, it's a lot of work "photoshopping" it out but in cycles(also corona vray etc..) I just enable/disable some object flags or rayswitch to modify those features and I'm done...
I know the community around luxcore somehow seeks ultimate realism, but in reality clients want fancy looking shit, not simulation (my case).
This mean that any asymmetrical light behavior (eye Vs light) can easily lead to some inconsistent/messed rendering. Cycles can do some stuff because it traces rays in a very specific way. Some aspect of the general "ray switch" concept can not be generalized. This "shadow rays transparency" it is however a step in that direction.
Is it possible to only support these features in some very specific render engine, like PATHCPU and PATHGPU only, also some forbidden "feature combination"? When one of the faking features are enabled, you can do some very strict checking and refuse to render, instead of giving inconsistent/messed renderings.