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

Re: [Public WebGL] Proposal: remove TIMESTAMP_EXT functionality from WebGL's EXT_disjoint_timer_query wrapper



Well, as I've written on webgl-dev-list, the fact that Chromium won't support TIMESTAMP_EXT renders it pretty much useless. There is little to no sense to write one code for platforms that have timestamps and another one for ones that don't. Especially considering absence of a way to feature-detect noop timestamps.
 
If implementers don't want to support TIMESTAMP_EXT due to technical difficulties we should drop it from the extension spec.
 
08.06.2016, 04:16, "Kenneth Russell" <kbr@google.com>:
WebGL community, 
 
In this discussion on webgl-dev-list:
https://groups.google.com/d/topic/webgl-dev-list/Q5tYioJqBmw/discussion
 
Developers have started using WebGL's wrapper for the EXT_disjoint_timer_query extension and have found that the TIMESTAMP_EXT queries aren't working well. Specifically, they're not implementable on either Windows or Mac OS X. Consequently, in Chrome, they return 0 on all platforms, and Chrome reports 0 bits for the QUERY_COUNTER_BITS_EXT query against timestamps.
 
Elapsed time queries are portable, and are the recommended way to gather timing information on the GPU.
 
It was suggested to simply remove support for timestamp queries. In concrete terms, this would mean:
 
 - Removing the TIMESTAMP_EXT enum, and its effects on getParameter() and getQueryEXT().
 - Removing the queryCounterEXT method.
 
Any thoughts on this proposal? This extension was only introduced recently and is probably not widely used yet, so the risk of breaking content is low.
 
Thanks,
 
-Ken
 
 
 
--
Kirill Dmitrenko
Yandex Maps Team