From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108270] [proton] Wolfenstein: The New Order (frame rate issue)
Date: Mon, 08 Oct 2018 02:01:39 +0000 [thread overview]
Message-ID: <bug-108270-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1282 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108270
Bug ID: 108270
Summary: [proton] Wolfenstein: The New Order (frame rate issue)
Product: Mesa
Version: 18.2
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: lejimster@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
In the first bunker the frame rate drops heavily and stutters in spots, the
frame rate is perfect 60fps before and after this area. I tested the same area
on Windows 10 and also Ubuntu with proprietary drivers and they don't suffer
from this issue.
Tested using Proton 3.7-6 as the game needs a patched wine to run. Hopefully
the trace is long enough to see the issue as the frame rate drop doesn't always
happen immediately.
Apitrace:
https://drive.google.com/file/d/1LWRVhJMeXo0h8IbUFBwj8vyTyyml6R5k/view?usp=sharing
Video showing the issue:
https://youtu.be/WheSQWf09yM
-Arch Linux
-RX Vega 56/Ryzen 1700
-mesa 18.3-git
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2801 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:[~2018-10-08 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 2:01 bugzilla-daemon [this message]
2018-11-12 14:06 ` [Bug 108270] [proton] Wolfenstein: The New Order (frame rate issue) bugzilla-daemon
2019-09-25 18:10 ` 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-108270-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