All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 50135] Unigine Heaven black stripes and weird shaders
Date: Sun, 20 May 2012 06:28:13 +0000	[thread overview]
Message-ID: <bug-50135-502-MTBNGThdRm@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-50135-502@http.bugs.freedesktop.org/>

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

--- Comment #4 from Vadim Girlin <ptpzz@yandex.ru> 2012-05-19 23:28:13 PDT ---
Created attachment 61874
  --> https://bugs.freedesktop.org/attachment.cgi?id=61874
[PATCH] st/mesa: expose "force_glsl_extensions_warn" option

I think attached patch might help. It allows to use less strict extension
handling to workaround some unigine problems. You'll also need to set
"force_glsl_extensions_warn" environment variable to "1" or "true" before
running the app:

force_glsl_extensions_warn=1 ./heaven

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2012-05-20  6:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-19 21:16 [Bug 50135] New: Unigine Heaven black stripes and weird shaders bugzilla-daemon
2012-05-19 21:17 ` [Bug 50135] " bugzilla-daemon
2012-05-19 21:19 ` bugzilla-daemon
2012-05-20  4:18 ` bugzilla-daemon
2012-05-20  6:28 ` bugzilla-daemon [this message]
2012-05-20 13:02 ` bugzilla-daemon
2012-05-21  0:08 ` bugzilla-daemon
2012-09-10 12:12 ` bugzilla-daemon
2012-09-10 12:44 ` bugzilla-daemon
2013-02-27 18:54 ` bugzilla-daemon
2013-06-03 13:55 ` bugzilla-daemon
2013-06-03 13:59 ` bugzilla-daemon
2013-06-03 14:01 ` bugzilla-daemon
2013-06-03 14:07 ` bugzilla-daemon
2014-08-11  6:20 ` bugzilla-daemon
2014-08-11  8:48 ` bugzilla-daemon
2014-10-20 22:22 ` bugzilla-daemon
2014-10-20 23:18 ` bugzilla-daemon
2019-09-18 19:00 ` 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-50135-502-MTBNGThdRm@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.