There is - thats the 'shared' possibility that sinbad talked about. I was talking about the 'result' RTT of these passes. If we have 10 objects that use this material, that means that 10 copies of the result RTT will have to coexist. Not necessarily a bad thing, as the objects that will use this will probably be the very-high quality objects, and not too many of them will coexist in the first place.tuan kuranes wrote:That has to be specified somehow by the user, as some pass resulting may be just intermediate, and can be reused in other "single effect material". In the skin example, the first diffuse pass RTT is to be reused, where the second pass RTT (blurred diffuse) has to be kept until material applied.compositor textures will have to exist once per object
Isn't there something like that in current Compositor ? Intermediate RTT reuse ?
Hm, yea good point. That's part of the reason i did decide to "think out loud" in this topic. The way I see the design I'm going towards right now will make these ideas much easier. Its important to remember that we can't remove features, as Ogre does have users that use its features. The migration path is probably something like declaring the 'old' version (shadow_texture and such) deprecated for a stable version and internally implementing it using the new system, and then after a while (unlike MS who do it every tuesday with DX) - maybe a complete stable cycle (Ogre 2.0?) remove it.It's probably a better idea to have this conversation at the end of the SoC if the project gets selected.
I still think we have to make sure that gsoc design will be at least compliant, if not designed to ease that future work.
Thinking all along the wrok how/where shadow framework could be replaced/shared seems a good thing to me.
Specifically, the "shadow material" current "linking" inside material could be shared/replace/enhanced by some way to fit both compositors and shadow framework ?
The conversation is healthy for this SoC project and for Ogre, and I think its causing me to believe more in the steps that I'm describing. I think my design in its original form actually fits with these ideas very well. I will have to make sure that it stays the case when I get down to the finer details of the implementation, but I do vision it all connecting together quite nicely when the post-SoC work will be done.