Created attachment 66810 [details] Incorrect rendering example The problem is that perspective correct mapping is not being done at all. I've tried to do some basic analysis to help as much as I could, so: Quick facts: - the problem doesn't happen with i915g - it doesn't happen with the 'reflect' mesa demo (no GLSL -> correct rendering) - affects mesa as old as 7.11 from Fedora 16 and as new as mesa 9.0-devel (git-a96119c) (8.0.4 too, haven't checked other versions) I think (hope) that the interesting thing to note here is that - as I've seen with INTEL_DEBUG=wm - the 'reflect' demo results in TEXLDP instruction being used, while any WebGL (effectively GLSL) demos only show TEXLD. I know that throwing WebGL implementation at the i915 might not be the best test case, but I couldn't get any native GLSL demo running. WebGL demos mostly work fine though and are easy to run: http://learningwebgl.com/lessons/lesson06/index.html https://developer.mozilla.org/samples/webgl/sample6/index.html The shaders are also extremely simple. The attached screenshot shows the demo from the second link with a different texture. Chromium/Mozilla - doesn't matter. Also (mis)reported elsewhere: "WebGL w. MESA driver results in affine texture mapping" <http://code.google.com/p/chromium/issues/detail?id=135332>
Hello Krzysztof, is this still valid with latest SW? Otherwise closing soon. Thank you.
(In reply to Elizabeth from comment #1) > Hello Krzysztof, is this still valid with latest SW? Otherwise closing soon. > Thank you. Hi, please postpone closing this at least for a few weeks. I'm putting this on my TODO, which is way too long right now. Nevertheless, I'm happy to provide feedback.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/717.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.