From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66967] Dota 2 crashes with r600g when starting the tutorial
Date: Wed, 21 Aug 2013 07:08:42 +0000 [thread overview]
Message-ID: <bug-66967-502-5FgziuXevm@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-66967-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 770 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=66967
--- Comment #4 from Tilman Sauerbeck <tilman@code-monkey.de> ---
(In reply to comment #3)
> I'm not sure if I and others experience the same problem as you, but when I
> try to start the first tutorial mission in DotA 2 (or change the resolution
> in the options menu), the game crashes.
I can change the resolution just fine.
> It seems to boil down to a general shader issue with Mesa, as users with
> Intel & R600 drivers are having the problems. When one delete certain shader
> files the game will start.
Nope, deleting/renaming the fxc subdirectory doesn't help on my system.
Looks like I'm seeing a different problem than you are.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1672 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:[~2013-08-21 7:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 16:06 [Bug 66967] New: Dota 2 crashes with r600g when starting the tutorial bugzilla-daemon
2013-07-17 15:43 ` [Bug 66967] " bugzilla-daemon
2013-07-31 15:18 ` bugzilla-daemon
2013-08-07 10:52 ` bugzilla-daemon
2013-08-21 7:08 ` bugzilla-daemon [this message]
2014-01-05 15:53 ` 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-66967-502-5FgziuXevm@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