From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98996] Counter Strike: Global Offensive performance on Radeon Polaris
Date: Tue, 25 Jun 2019 01:04:05 +0000 [thread overview]
Message-ID: <bug-98996-502-WZeo7TNLsg@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98996-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 772 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98996
Timothy Arceri <t_arceri@yahoo.com.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #4 from Timothy Arceri <t_arceri@yahoo.com.au> ---
There have been many performance improvements to the drivers since this was
reported, and nobody else has since complained of performance issue with this
game. I'm going to close this for now. Feel free to reopen with updated
information if this is still an issue.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2330 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-06-25 1:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 11:04 [Bug 98996] Counter Strike: Global Offensive performance bugzilla-daemon
2016-12-05 11:22 ` bugzilla-daemon
2017-03-22 16:57 ` [Bug 98996] Counter Strike: Global Offensive performance on Radeon Polaris bugzilla-daemon
2017-04-11 18:05 ` bugzilla-daemon
2017-04-12 1:43 ` bugzilla-daemon
2019-06-25 1:04 ` bugzilla-daemon [this message]
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-98996-502-WZeo7TNLsg@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).