From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201345] New: Micro stuttering in RocketLeague
Date: Mon, 08 Oct 2018 14:35:38 +0000 [thread overview]
Message-ID: <bug-201345-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=201345
Bug ID: 201345
Summary: Micro stuttering in RocketLeague
Product: Drivers
Version: 2.5
Kernel Version: 4.19.0-rc6
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: mh@familie-heinz.name
Regression: No
Created attachment 278951
--> https://bugzilla.kernel.org/attachment.cgi?id=278951&action=edit
Shader clock and fps directly after a boot
Hi,
everytime I start RocketLeague the first time after a boot I have some kind of
micro stuttering. This happens with my RX550 and on a Vega 56.
A workaround is to set power_dpm_force_performance_level to "high".
Setting it back to "auto" on the RX550 makes the stuttering return. Doing the
same thing on the Vega 56 not and the stuttering is gone until the next boot.
I'll attach three screenshots that display the shader clock and fps via gallium
hud. One directly after a boot, one with performance_level set to "high" and
one after resetting it to "auto". All screenshots were made with the Vega 56
and Mesa 18.2.0.
Best regards
Matthias
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-10-08 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 14:35 bugzilla-daemon [this message]
2018-10-08 14:36 ` [Bug 201345] Micro stuttering in RocketLeague bugzilla-daemon
2018-10-08 14:37 ` 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-201345-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.