[Ubuntu-x-swat] [Bug 676183] Re: Basic shaders produce incorrect output

2011-04-28 Thread Stéphan Kochen
Neither the Chromium 13 nightly nor Firefox 4 in Natty enable WebGL for my card, though Firefox 4 does let me bypass its blacklist with an envvar MOZ_GLX_IGNORE_BLACKLIST. With that enabled, the page now displays correctly for me. Feel free to close this bug. -- You received this bug notificatio

[Ubuntu-x-swat] [Bug 676183] [NEW] Basic shaders produce incorrect output

2010-11-16 Thread Stéphan Kochen
Public bug reported: Trying to build something on WebGL technology, I noticed that basic shaders were producing incorrect output. The problem occurs on both Firefox 4 and Chrome 7. I'm on Intel GM965 hardware, but strangely also see the exact same problem when I install `libgl1-mesa-swrast` or try

[Ubuntu-x-swat] [Bug 676183] Re: Basic shaders produce incorrect output

2010-11-16 Thread Stéphan Kochen
-- Basic shaders produce incorrect output https://bugs.launchpad.net/bugs/676183 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Pos

[Ubuntu-x-swat] [Bug 676183] Re: Basic shaders produce incorrect output

2010-11-16 Thread Stéphan Kochen
Here's the example page as an attachment, for archiving. Perhaps useful to add, some other things I've tried: * Drawing interpolated color shades using a varying variable works. * Functions like `dot` and `max` produce valid float output. For example, using these two, I can implement just the

[Ubuntu-x-swat] [Bug 676183] Re: Basic shaders produce incorrect output

2010-11-18 Thread Stéphan Kochen
After some more experimentation, it looks like it's specifically a problem with float literals, which are floored / truncated. Things work when I simply replace them with uniforms and set their value in JavaScript. -- Basic shaders produce incorrect output https://bugs.launchpad.net/bugs/676183 Y