From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 88408] Black screen in Nuclear Dawn
Date: Tue, 20 Jan 2015 20:23:14 +0000 [thread overview]
Message-ID: <bug-88408-502-44nKGFP7TY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-88408-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 961 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=88408
--- Comment #12 from Iwo <igi31@wp.pl> ---
(In reply to commiethebeastie from comment #11)
> Can you run another source based game?
Yes... without a problem. This game is the only one from source based games to
have such issues. In the past before mesa 10.2 there was some problems with
counter strike global offensive. Sometimes guns was black or some objects. But
it is hard to tell if this was a game problem or mesa problems. I remember that
the problems was solved when i have updated the game via steam, but in the same
time there waa already an update for mesa too. Do you think that may be a
problem with the game itself? I'd like to mention that wargame european
escalation have similar problems with rendering but only when you set for
example water detail to high. In medium and low detail terrain is rendered
correctly.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1739 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-01-20 20:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 16:35 [Bug 88408] Black screen in Nuclear Dawn bugzilla-daemon
2015-01-14 16:40 ` bugzilla-daemon
2015-01-15 1:35 ` bugzilla-daemon
2015-01-15 22:25 ` bugzilla-daemon
2015-01-16 1:47 ` bugzilla-daemon
2015-01-16 14:45 ` bugzilla-daemon
2015-01-18 21:52 ` bugzilla-daemon
2015-01-19 3:56 ` bugzilla-daemon
2015-01-19 7:52 ` bugzilla-daemon
2015-01-19 19:38 ` bugzilla-daemon
2015-01-20 15:15 ` bugzilla-daemon
2015-01-20 20:14 ` bugzilla-daemon
2015-01-20 20:23 ` bugzilla-daemon [this message]
2015-01-20 20:34 ` bugzilla-daemon
2015-01-21 10:27 ` bugzilla-daemon
2015-01-21 10:28 ` bugzilla-daemon
2015-01-21 10:30 ` bugzilla-daemon
2015-01-24 10:22 ` bugzilla-daemon
2015-01-26 23:26 ` bugzilla-daemon
2015-01-27 14:44 ` bugzilla-daemon
2015-01-27 14:46 ` bugzilla-daemon
2015-01-28 10:28 ` bugzilla-daemon
2015-03-14 14:39 ` bugzilla-daemon
2015-03-14 17:07 ` 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-88408-502-44nKGFP7TY@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 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.