From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 88758] Low FPS in settings on Dota2
Date: Fri, 23 Jan 2015 17:34:50 +0000 [thread overview]
Message-ID: <bug-88758-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1464 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=88758
Bug ID: 88758
Summary: Low FPS in settings on Dota2
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: minor
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: lorenz.bona@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 112734
--> https://bugs.freedesktop.org/attachment.cgi?id=112734&action=edit
LIBGL_DEBUG=verbose steam
It's more then a week that I've faced a new issue with steam.
I haven't played since November so I don't know if it's a known bug or a dumb
configuration.
In Dota2 settings I get only 10 (or less) FPS but as soon as I start a game I
have almost 30 FPS. The GPU is an R7-265 with an FX-8320@4.4GHz.
I'm sure that back in November I can run Dota settings at about 50+ FPS. What's
going on? I can't see any warning in dmesg.
Is this a common behaviour or it's a configuration problem?
I'm running kernel from agd5f git repo, drm-fixes-3.19 branch.
I've tried also with mesa in Debian Sid branch or with llvm3.6. No changes at
all.
I've run:
$ LIBGL_DEBUG=verbose steam > dota2.txt
I hope this can help.
PS: I build mesa on a separate 32bit chroot.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2934 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-01-23 17:34 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 17:34 bugzilla-daemon [this message]
2015-01-23 17:35 ` [Bug 88758] Low FPS in settings on Dota2 bugzilla-daemon
2015-01-26 8:19 ` bugzilla-daemon
2015-01-26 8:28 ` bugzilla-daemon
2015-01-26 9:41 ` bugzilla-daemon
2015-01-28 7:04 ` bugzilla-daemon
2015-01-28 10:26 ` bugzilla-daemon
2015-01-28 13:41 ` bugzilla-daemon
2015-01-28 13:42 ` bugzilla-daemon
2015-01-28 14:16 ` bugzilla-daemon
2015-01-28 14:17 ` bugzilla-daemon
2015-01-29 11:24 ` bugzilla-daemon
2015-01-29 11:25 ` bugzilla-daemon
2015-01-29 13:55 ` bugzilla-daemon
2015-01-29 14:02 ` bugzilla-daemon
2015-01-29 14:38 ` bugzilla-daemon
2015-01-29 15:04 ` bugzilla-daemon
2015-01-29 15:58 ` bugzilla-daemon
2015-01-29 16:44 ` bugzilla-daemon
2015-01-29 17:14 ` bugzilla-daemon
2015-01-29 17:15 ` bugzilla-daemon
2015-01-29 18:10 ` bugzilla-daemon
2015-01-30 3:17 ` bugzilla-daemon
2015-01-30 8:41 ` bugzilla-daemon
2015-01-30 11:56 ` bugzilla-daemon
2015-01-30 11:57 ` bugzilla-daemon
2015-01-30 11:58 ` bugzilla-daemon
2015-01-30 11:59 ` bugzilla-daemon
2015-01-31 17:45 ` bugzilla-daemon
2015-01-31 17:46 ` bugzilla-daemon
2015-01-31 17:46 ` bugzilla-daemon
2015-01-31 17:50 ` bugzilla-daemon
2015-02-03 5:54 ` bugzilla-daemon
2015-02-03 6:54 ` bugzilla-daemon
2015-02-03 6:55 ` bugzilla-daemon
2015-02-03 6:55 ` bugzilla-daemon
2015-02-03 7:06 ` 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-88758-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