<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Unigine Valley & Heaven "error: syntax error, unexpected EXTENSION, expecting $end" IVB HD4000"
href="https://bugs.freedesktop.org/show_bug.cgi?id=75664#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Unigine Valley & Heaven "error: syntax error, unexpected EXTENSION, expecting $end" IVB HD4000"
href="https://bugs.freedesktop.org/show_bug.cgi?id=75664">bug 75664</a>
from <span class="vcard"><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> <span class="fn">Eero Tamminen</span></a>
</span></b>
<pre>In the meanwhile, maybe appropriate workarounds could be added to Mesa drirc
also for Valley?
As to other issues with these demos, If I enable MSAA, I get a lot of these
warnings from Heaven & Valley:
----------
GLFrameBuffer::enable(): incomplete attachment
GLFrameBuffer::enable(): incomplete attachment
GLFrameBuffer::enable(): incomplete attachment
GLFrameBuffer::enable(): incomplete attachment
GLFrameBuffer::enable(): incomplete attachment
OpenGL error: invalid framebuffer operation
----------
And once:
UserArray::push(): bad array index 4
On quick look, I don't see a visual problem in the demos though.
Whereas enabling MSAA for Tropics or Sanctuary demo completely breaks them with
Mesa. I get lots of these errors:
-------------
0:165(89): error: bit-wise operations are forbidden in GLSL 1.10 (GLSL 1.30 or
GLSL ES 3.00 required)
GLShader::loadFragment(): error in
"core/shaders/meshes/fragment_leaf_ambient.shader" file
-------------
Trying to force indicated GLSL version or disabling bit encoding with Mesa
environment variables to work around the issue doesn't have any effect on it.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>