All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 57875] Second Life viewer bad rendering with git-ec83535
Date: Tue, 16 Jul 2013 12:43:35 +0000	[thread overview]
Message-ID: <bug-57875-502-kDAeEHyE9T@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-57875-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1122 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=57875

--- Comment #30 from Christoph Bumiller <e0425955@student.tuwien.ac.at> ---
How does it depend on the depth test, and why does it seem "off" to make
something that is originally a shader property in D3D a shader property in
OpenGL as well ?
Not using shaders isn't allowed (at least not in gallium), so you have to use a
pass-through shader anyway, so this limits state inter-dependency.

The qualifier "layout(windowspace)/layout(pretransformed) out vec4 gl_Position"
is supposed to disable clipping and the viewport transformation (so glViewport
settings will be ignored).

The only open question is how depth values should be treated, which can be
either clipped or clamped, and there is actually a D3DCAPS9 bit to tell the
user what will happen.
On r600, you cannot disable xy clipping without disabling z clipping, so it
will have to advertise clamping. On NV cards you have more fine-grained
control, and I'd actually prefer depth clipping there unless GL_DEPTH_CLAMP is
enabled as well.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1952 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2013-07-16 12:43 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-04 13:04 [Bug 57875] New: Second Life viewer bad rendering with git-ec83535 bugzilla-daemon
2012-12-04 13:08 ` [Bug 57875] " bugzilla-daemon
2012-12-04 13:11 ` bugzilla-daemon
2012-12-04 13:53 ` bugzilla-daemon
2012-12-06 15:55 ` bugzilla-daemon
2012-12-06 16:54 ` bugzilla-daemon
2012-12-06 17:04 ` bugzilla-daemon
2012-12-06 17:09 ` bugzilla-daemon
2012-12-06 18:20 ` bugzilla-daemon
2012-12-06 18:34 ` bugzilla-daemon
2012-12-06 18:52 ` bugzilla-daemon
2012-12-06 18:55 ` bugzilla-daemon
2012-12-06 20:49 ` bugzilla-daemon
2012-12-06 22:03 ` bugzilla-daemon
2012-12-06 23:43 ` bugzilla-daemon
2012-12-09 21:59 ` bugzilla-daemon
2012-12-10 15:20 ` bugzilla-daemon
2012-12-12 20:29 ` bugzilla-daemon
2012-12-27 10:25 ` bugzilla-daemon
2013-01-07 15:43 ` bugzilla-daemon
2013-01-07 16:12 ` bugzilla-daemon
2013-01-21 19:07 ` bugzilla-daemon
2013-01-21 22:16 ` bugzilla-daemon
2013-01-22 10:25 ` bugzilla-daemon
2013-01-22 10:39 ` bugzilla-daemon
2013-01-25 11:27 ` bugzilla-daemon
2013-03-13 13:30 ` bugzilla-daemon
2013-03-13 21:20 ` bugzilla-daemon
2013-06-30 16:07 ` bugzilla-daemon
2013-07-01 15:15 ` bugzilla-daemon
2013-07-16 12:43 ` bugzilla-daemon [this message]
2013-07-16 13:40 ` bugzilla-daemon
2013-07-16 17:09 ` bugzilla-daemon
2013-07-30 21:12 ` 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-57875-502-kDAeEHyE9T@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /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.