From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 25871] nearest neighbour samples wrong texel (precision/rounding problem) Date: Wed, 16 Apr 2014 08:13:54 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1767855263==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 54C736E356 for ; Wed, 16 Apr 2014 01:13:54 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1767855263== Content-Type: multipart/alternative; boundary="1397636034.2E0a32810.2556"; charset="us-ascii" --1397636034.2E0a32810.2556 Date: Wed, 16 Apr 2014 08:13:54 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=25871 --- Comment #15 from Erik Faye-Lund --- (In reply to comment #14) > Thanks for the feedback. So it is a precision issue after all. If fglrx > exhibits the same behavior, there is nothing I can do. I don't know of any > hardware state which controls precision of texture addressing. AMD's Windows drivers at least seemingly consistently performs nearest-filtering with round-off-point off by a 512th of a texel. So I think this is somehow intended (even if really unfortunate for some non-trivial usecases). -- You are receiving this mail because: You are the assignee for the bug. --1397636034.2E0a32810.2556 Date: Wed, 16 Apr 2014 08:13:54 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 15 on bug 25871 from 
(In reply to comment #14)
> Thanks for the feedback. So it is a precision issue after all. If fglrx
> exhibits the same behavior, there is nothing I can do. I don't know of any
> hardware state which controls precision of texture addressing.

AMD's Windows drivers at least seemingly consistently performs
nearest-filtering with round-off-point off by a 512th of a texel. So I think
this is somehow intended (even if really unfortunate for some non-trivial
usecases).

You are receiving this mail because:
  • You are the assignee for the bug.
--1397636034.2E0a32810.2556-- --===============1767855263== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1767855263==--