From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100239] Incorrect rendering in CS:GO
Date: Thu, 16 Mar 2017 20:35:30 +0000 [thread overview]
Message-ID: <bug-100239-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1068 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100239
Bug ID: 100239
Summary: Incorrect rendering in CS:GO
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: network723@rkmail.ru
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 130271
--> https://bugs.freedesktop.org/attachment.cgi?id=130271&action=edit
Broken AUG scope
In windows, when you're aiming with AUG the screen around the scope is blurred.
On Mesa we have strange black pattern. The pattern changes on each cs:go
restart.
I can reproduce it on Mesa 17.1-git + llvm 5.0 + RX480 and on stock Ubuntu
16.04.2 (Mesa 13.0, I believe) + R7 240
Note: green rectangles are not the bug, it's me hiding my steam name.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2545 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-03-16 20:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 20:35 bugzilla-daemon [this message]
2017-03-16 21:05 ` [Bug 100239] Incorrect rendering in CS:GO bugzilla-daemon
2017-03-22 16:54 ` bugzilla-daemon
2017-03-22 18:56 ` bugzilla-daemon
2017-04-27 19:39 ` bugzilla-daemon
2017-04-29 8:52 ` bugzilla-daemon
2017-04-29 12:22 ` bugzilla-daemon
2017-05-01 3:44 ` bugzilla-daemon
2017-05-01 12:16 ` bugzilla-daemon
2017-05-06 14:59 ` bugzilla-daemon
2017-05-10 23:44 ` bugzilla-daemon
2017-05-13 8:32 ` bugzilla-daemon
2017-12-16 16:04 ` bugzilla-daemon
2018-04-02 11:02 ` bugzilla-daemon
2018-07-07 21:11 ` bugzilla-daemon
2018-07-07 21:12 ` bugzilla-daemon
2018-07-08 9:30 ` bugzilla-daemon
2018-07-08 10:27 ` bugzilla-daemon
2018-11-25 9:52 ` bugzilla-daemon
2019-01-10 9:44 ` bugzilla-daemon
2019-05-03 1:20 ` bugzilla-daemon
2019-05-03 6:08 ` bugzilla-daemon
2019-05-06 4:31 ` bugzilla-daemon
2019-05-06 23:43 ` bugzilla-daemon
2019-08-08 20:53 ` bugzilla-daemon
2019-08-08 20:59 ` bugzilla-daemon
2019-08-09 8:40 ` bugzilla-daemon
2019-09-14 12:45 ` bugzilla-daemon
2019-09-17 2:09 ` bugzilla-daemon
2019-09-25 17:58 ` 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-100239-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;
as well as URLs for NNTP newsgroup(s).