From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89203] Mesa 10.4.3 and up causes stuttering and frame drops in a particular game
Date: Thu, 19 Feb 2015 06:43:49 +0000 [thread overview]
Message-ID: <bug-89203-502-NGya4k1mEJ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89203-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 688 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=89203
--- Comment #7 from smoki <smoki00790@gmail.com> ---
The best is if you can bisect mesa, if 10.3 worked fine it should be easy :)
Or try various settings in game, might be only one which trigger slow case.
Or if someone other want to reproduce it, apitrace trace will be usefull,
etc...
Otherwise more info is needed, like:
Which version of Minecraft?
Java or openjdk used?
Did you use optifine?
You might post your options.txt file, because as i said it might only happen
with exact settings and also optionsof.txt in case you use optifine, etc...
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1495 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 prev parent reply other threads:[~2015-02-19 6:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-89203-502@http.bugs.freedesktop.org/>
2015-02-18 14:29 ` [Bug 89203] Mesa 10.4.3 and up causes stuttering and frame drops in a particular game bugzilla-daemon
2015-02-18 14:49 ` bugzilla-daemon
2015-02-19 2:48 ` bugzilla-daemon
2015-02-19 3:22 ` bugzilla-daemon
2015-02-19 3:24 ` bugzilla-daemon
2015-02-19 6:43 ` bugzilla-daemon [this message]
2015-02-19 20:37 ` bugzilla-daemon
2015-05-06 21:43 ` bugzilla-daemon
2015-05-07 3:02 ` 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-89203-502-NGya4k1mEJ@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