From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110760] Low FPS in Quake Champions with Vega20
Date: Sat, 25 May 2019 07:20:31 +0000 [thread overview]
Message-ID: <bug-110760-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1282 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110760
Bug ID: 110760
Summary: Low FPS in Quake Champions with Vega20
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
I'm not sure if I should report it here or against DXVK. I've just installed
Radeon VII card on my Ryzen 7 1700 system, and FPS in Quake Champions
(Steam/Proton) is twice as lower as it was with RX480.
I've tried other applications like Unigine Superposition, Rise of Tomb Raider,
and Witcher 3 (proton), and they seem to perform as expected (much faster than
with RX480)
I've tried purging DXVK and Mesa caches, this does not seem to help. Also,
tried different DXVK versions.
HW spec:
Ryzen 1700
ASUS Prime X370 Pro
32 GiB ram
Sapphire Radeon VII
SW spec:
openSUSE 15.1
linux kernel 5.1.4
Mesa git 9fe1a925e2a4093cd88152a52ad48677d02f6ba5
llvm 9 rev 361414
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2645 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
next reply other threads:[~2019-05-25 7:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-25 7:20 bugzilla-daemon [this message]
2019-05-27 5:10 ` [Bug 110760] Low FPS in Quake Champions with Vega20 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-110760-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 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.