From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 58131] New: r300g: Corruption in Half Life 2 unless gl_ClipVertex is written
Date: Tue, 11 Dec 2012 11:27:13 +0000 [thread overview]
Message-ID: <bug-58131-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1173 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=58131
Priority: medium
Bug ID: 58131
Assignee: dri-devel@lists.freedesktop.org
Summary: r300g: Corruption in Half Life 2 unless gl_ClipVertex
is written
Severity: normal
Classification: Unclassified
OS: All
Reporter: stefandoesinger@gmx.at
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/r300
Product: Mesa
Created attachment 71330
--> https://bugs.freedesktop.org/attachment.cgi?id=71330&action=edit
Screenshot of the static main menu
Half-Life 2 (running in Wine) has a random vertex corruption. This corruption
can be seen in the static main menu(start it with -console) and in-game. The
corruption goes away if I modify Wine to always write gl_ClipVertex even if
clipping is disabled.
This is interesting particularly because r300g does not support clipping with
vertex shaders. It says so on the command line, and in-game rendering and the
Wine tests confirm this.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2632 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
next reply other threads:[~2012-12-11 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 11:27 bugzilla-daemon [this message]
2012-12-11 11:28 ` [Bug 58131] r300g: Corruption in Half Life 2 unless gl_ClipVertex is written bugzilla-daemon
2019-09-18 18:51 ` 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-58131-502@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox