[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] Should GLfloat and GLclampf be typedefs for "unrestricted float"?

I mean that unless you have color buffer half float, ES is clamping 0-1 all the way. texture float as a rendertarget is currently not clamped in WebGL desktop (but it shouldn't even be available to attach as target without color buffer float). A lot of demos rely on texture float RTT and non-clamping behavior. Those demos will have to be updated to also acquire the color buffer float extension. If either clamping is observed for a float RTT with a texture float but without a color buffer float or the target for a float RTT is throwing invalid FBO then a lot of demos will suddenly break.

On Tue, Nov 20, 2012 at 2:43 AM, Mark Callow <callow.mark@artspark.co.jp> wrote:

On 2012/11/19 23:07, Florian Bösch wrote:
    • desktop
      • IS: clamped [CORRECT]
      • IS: OES texture float: not clamped [WRONG], if fixed, will break a lot of apps, perhaps issue a warning
This is not relevant to Boris's question but in view of my color_buffer{_half}_float proposals...

Are you referring to app's using OES_texture_float and doing float rendering which would break if the current spec. was actually being followed? My proposal is that implementations that currently support float rendering under OES_texture_float would be required to implicitly enable the WEBGL_color_buffer_float extension, when OES_texture_float is enabled, and follow its rules. I expect that if implementations update their OES_texture_float support at all, it will be to follow the proposed extensions. Therefore the situation of clamping when drawing to an FP buffer should not arise.

Am I missing some circumstance?



注意:この電子メールには、株式会社エイチアイの機密情報が含まれている場合が有ります。正式なメール受信者では無い場合はメール複製、 再配信または情報の使用を固く禁じております。エラー、手違いでこのメールを受け取られましたら削除を行い配信者にご連絡をお願いいたし ます.

NOTE: This electronic mail message may contain confidential and privileged information from HI Corporation. If you are not the intended recipient, any disclosure, photocopying, distribution or use of the contents of the received information is prohibited. If you have received this e-mail in error, please notify the sender immediately and permanently delete this message and all related copies.