All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 88408] Black screen in Nuclear Dawn
Date: Mon, 26 Jan 2015 23:26:44 +0000	[thread overview]
Message-ID: <bug-88408-502-eE7uJ4sfwr@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-88408-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 860 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=88408

--- Comment #18 from Iwo <igi31@wp.pl> ---
(In reply to commiethebeastie from comment #17)
> Perhaps the problem in llvm-3.5.
> 
> Try to upgrade to mesa builded with llvm-3.6.
> 
> For ubuntu to install oibaf or paulo-miguel-dias ppa.

I need more time to compile llvm, but i have tested nuclear dawn on mesa
10.4.3.
When i switched anti-aliasing to off and set shaders to low (or very low, the
lowest setting), the game launches and even in the menu i see everything.
Previoulsy was only buttons visible. The game itself is totaly playable, so i
think that shaders and antialiasing is bugy on open source driver. I need to
set antialiasing to off and shaders to lowest possible detail. Is everyone else
got this kind of problems?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1650 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

  parent reply	other threads:[~2015-01-26 23:26 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
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 [this message]
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-eE7uJ4sfwr@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.