Re: [Public WebGL] WEBGL_dynamic_texture extension proposal

[Gregg Tavares (社用) <gman@google.com>]

I don't expect most libraries will handle it automatically. Most will require the user to specify upfront what they want.

but yes, if they want to support dynamic textures I do expect them to handle it. Only they know when is the appropriate time to compile and when to fail. On top of that they have to call dynamicTextureAcquireFrame to use these textures so it's not like they can magically do nothing and have it just work.

Those libraries that do want to type handle it automatically are already most likely handling it dynamically. They generate shaders based on number of lights and other material parameters. The can just as easily add dynamic textures as an option to their generator.

On Thu, Jul 5, 2012 at 10:09 AM, Florian Bösch <pyalot@gmail.com> wrote:

So in essence, while claiming dynamic recompilation is too complex to do for WebGL, you fully expect any framework/utility/library to do that now? Despite that they have the exact same problem, they don't know beforehand what flavor of texture will be present, and when they find out, they'll have to recompile.

Yeah, 16 samplers that can either be a texture2D or a dynamic texture sure seems like a messy usecase, I'm sure it gets *much* better by having to compile 65536^shaders upon "loading". Are you quite stark mad?