All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 25871] New: nearest neighbour samples wrong texel (precision/rounding problem)
Date: Sun,  3 Jan 2010 05:01:35 -0800 (PST)	[thread overview]
Message-ID: <bug-25871-502@http.bugs.freedesktop.org/> (raw)

http://bugs.freedesktop.org/show_bug.cgi?id=25871

           Summary: nearest neighbour samples wrong texel
                    (precision/rounding problem)
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/R600
        AssignedTo: dri-devel@lists.sourceforge.net
        ReportedBy: pierre-bugzilla@ossman.eu


The following fragment program does the wrong thing on r600/r700 hardware:

TEX result.color, 0.498046860099, texture[0], 2D;

(the texture coord is as far as I got before I got bored. I'm not sure the
precision goes much further anyway)

The circumstances is that I have a 4x4 texture with nearest neighbour
interpolation. The above code should be sampling texel 1,1 but is instead
sampling texel 2,2. This causes problems for fragment programs that try to do
things based on texel coords (like bicubic interpolation).

This seems to be a hw bug as I've tried it with fglrx (albeit with a slightly
different card) and it exhibits the same bug. As such, I'm not sure it can be
solved but hopefully there is a workaround.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
--

             reply	other threads:[~2010-01-03 13:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-03 13:01 bugzilla-daemon [this message]
2010-01-04 21:48 ` [Bug 25871] nearest neighbour samples wrong texel (precision/rounding problem) bugzilla-daemon
2010-01-04 21:49 ` bugzilla-daemon
2011-03-01  2:27 ` bugzilla-daemon
2011-03-01  2:56 ` bugzilla-daemon
2012-09-11 11:32 ` bugzilla-daemon
2012-09-11 13:51 ` bugzilla-daemon
2012-09-11 17:12 ` bugzilla-daemon
2012-09-11 17:23 ` bugzilla-daemon
2012-09-12 12:34 ` bugzilla-daemon
2012-09-12 13:03 ` bugzilla-daemon
2012-09-12 13:56 ` bugzilla-daemon
2014-04-13 10:46 ` bugzilla-daemon
2014-04-13 20:40 ` bugzilla-daemon
2014-04-13 22:39 ` bugzilla-daemon
2014-04-16  8:13 ` bugzilla-daemon
2014-04-16 15:15 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-25871-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.