[Public WebGL] dev-tools 60fps limiter toggle

John Davis [email protected]
Thu Nov 27 02:54:43 PST 2014


Wow, not cool.

On Thu, Nov 27, 2014 at 5:50 AM, Florian Bösch <[email protected]> wrote:

> Really? Like, really?
> https://code.google.com/p/chromium/issues/detail?id=437172#c5
>
> Whatever, stay classy google, real quality ticket support worker material
> you're hiring.
>
> On Thu, Nov 27, 2014 at 8:42 AM, Florian Bösch <[email protected]> wrote:
>
>> https://bugs.webkit.org/show_bug.cgi?id=139072
>>
>> https://code.google.com/p/chromium/issues/detail?id=437172
>>
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1105633
>>
>> On Thu, Nov 27, 2014 at 2:53 AM, Kenneth Russell <[email protected]> wrote:
>>
>>> Sounds reasonable. Please file bugs / feature requests against the
>>> various WebGL implementations -- links are under the "implementations"
>>> section of https://www.khronos.org/webgl/wiki/Main_Page . Please feel
>>> free to post them here so they aren't lost.
>>>
>>> I don't know how easy it'll be to dynamically turn this value on and
>>> off in browsers' code.
>>>
>>>
>>> On Wed, Nov 26, 2014 at 2:50 PM, Jukka Jylänki <[email protected]> wrote:
>>> > Seconded. I've often also found it very inconvenient to not have this
>>> > options. Often times it is difficult or outright impossible to scale
>>> the
>>> > workload so that benchmarking or profiling while being capped to vsync
>>> would
>>> > make sense.
>>> >
>>> >    Jukka
>>> >
>>> > 2014-11-27 0:33 GMT+02:00 Patrick Cozzi <[email protected]>:
>>> >>
>>> >> The Cesium team and my students would also love this for profiling.
>>> >>
>>> >> Patrick
>>> >>
>>> >> On Wed, Nov 26, 2014 at 2:30 PM, Thibaut Despoulain
>>> >> <[email protected]> wrote:
>>> >>>
>>> >>> This would be amazing. I highly support this suggestion!
>>> >>>
>>> >>> On Nov 26, 2014 11:16 AM, "Florian Bösch" <[email protected]> wrote:
>>> >>>>
>>> >>>> Well, you'd want to quickly change it for development. Not as a
>>> >>>> standard, more like, a quick way to do it just for one page (the
>>> one you've
>>> >>>> got the dev tools open), without all other tabs going haywire.
>>> >>>>
>>> >>>> On Wed, Nov 26, 2014 at 7:58 PM, Kenneth Russell <[email protected]>
>>> wrote:
>>> >>>>>
>>> >>>>> This can be done in Chrome by launching it with the command line
>>> >>>>> argument --disable-gpu-vsync. Is it worth standardizing this?
>>> >>>>>
>>> >>>>>
>>> >>>>> On Wed, Nov 26, 2014 at 9:49 AM, Florian Bösch <[email protected]>
>>> >>>>> wrote:
>>> >>>>> > It occurred to me that it'd be useful to have a way to disable
>>> the
>>> >>>>> > 60fps
>>> >>>>> > limit like you would disable network caching or stuff like that
>>> in
>>> >>>>> > the dev
>>> >>>>> > tools per checkbox.
>>> >>>>> >
>>> >>>>> > Would this at all be feasible for browser vendors?
>>> >>>>
>>> >>>>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> twitter.com/pjcozzi
>>> >
>>> >
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://khronos.org/pipermail/public_webgl_khronos.org/attachments/20141127/53f93bd1/attachment.html>


More information about the public_webgl mailing list