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

Re: [Public WebGL] Anti-aliasing issues on Minefield and Webkit



I'm thinking it isn't implemented in Minefield. If that's the case, I don't have much
choice other than waiting for a patch. If I don't see a fix on Webkit, I'll just
have to leave it enabled.

Thanks,
  Andor

----- Original Message -----
From: "Mo, Zhenyao" <zhenyao@gmail.com>
Date: Friday, April 16, 2010 6:36 am
Subject: Re: [Public WebGL] Anti-aliasing issues on Minefield and Webkit
To: Andor Salga <asalga@learn.senecac.on.ca>
Cc: public webgl <public_webgl@khronos.org>, Al MacDonald <al@bocoup.com>, David Humphrey <David.Humphrey@senecac.on.ca>, Corban Brook <corbanbrook@gmail.com>

> Sorry I misunderstood your original email.
>
> antialias is implemented in webkit and chrome, but I am not sure about
> firefox/minefield.
>
> The flicking is wierd.  I would assume with anti-alias on,
> it would be
> more buggy, not the other way around.
>
> On Thu, Apr 15, 2010 at 10:08 PM, Andor Salga
> <asalga@learn.senecac.on.ca> wrote:
> > Hi Zhenyao,
> > Sorry I wasn't clear. WebGL anti-aliasing is working fine in
> Webkit, but the
> > problem occurs when I try to disable it. Then the canvas
> flickers and my
> > frame rate drops. I know for sure my card supports it, the
> question is if
> > Minefield does.
> >
> > I ran your code anyway:
> >
> > var attribs = ctx.getContextAttributes();
> > alert(attribs.antialias);
> >
> > and found yet more interesting results. Webkit alerts true,
> but Minefield
> > throws an exception. "TypeError:
> curContext.getContextAttributes is not a
> > function"
> >
> > My system: Macbook Pro (10.5.8)
> > NVIDIA GeForce 8600M GT
> > Minefield: Gecko/20100415 Minefield/3.7a5pre
> > Webkit: Version 4.0.4 (5531.21.10, r57408)
> >
> > Thanks,
> >  Andor
> >
> > ----- Original Message -----
> > From: "Mo, Zhenyao" <zhenyao@gmail.com>
> > Date: Friday, April 16, 2010 12:37 am
> > Subject: Re: [Public WebGL] Anti-aliasing issues on Minefield
> and Webkit
> > To: Andor Salga <asalga@learn.senecac.on.ca>
> > Cc: public webgl <public_webgl@khronos.org>, Al MacDonald
> <al@bocoup.com>,> David Humphrey
> <David.Humphrey@senecac.on.ca>, Corban Brook
> > <corbanbrook@gmail.com>
> >
> >> Hi Andor,
> >>
> >> Antialiasing IS implemented in WebGL, but your driver may not be
> >> stable enough to support it.  When you request antialias to true,
> >> whether it's honored or not really depends on your graphics
> >> card.  To
> >> be sure, you can do something like
> >>
> >>   var ctx = canvas.getContext("experimental-webgl");
> >> // By default
> >> antialias is on
> >>   var attribs = ctx.getContextAttributes();
> >>   alert(attribs.antialias);
> >>
> >> Please let me know what the result is and also your graphics
> >> card / os
> >> / browser, so we could look into the flicker issue.
> >>
> >> Mo
> >>
> >> On Thu, Apr 15, 2010 at 5:42 PM, Andor Salga
> >> <asalga@learn.senecac.on.ca> wrote:
> >> > Hi,
> >> >  Has anyone had any luck trying to enable anti-aliasing in
> >> Minefield? I'm
> >> > trying this:
> >> >
> >> >
> >> > var ctx = canvas.getContext("experimental-webgl",
> {antialias:true});>> >
> >> >
> >> >   It doesn't seem to do anything at all. I'm guessing it's
> >> just not
> >> > implemented.
> >> > Webkit properly defaults anti-aliasing to true, but when I try
> >> to explicitly
> >> > turn it off:
> >> >
> >> >
> >> >
> >> > var ctx = canvas.getContext("experimental-webgl",
> >> {antialias:false});>
> >> >
> >> > my rendered frames flicker at about 1 FPS. Has anyone else
> >> seen these
> >> > issues?
> >> >
> >> >
> >> > Thanks,
> >> >   Andor
>
> -----------------------------------------------------------
> You are currently subscribe to public_webgl@khronos.org.
> To unsubscribe, send an email to majordomo@khronos.org with
> the following command in the body of your email:
>