<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [All bisected] Render error when running Unigine-Heave_v4.0"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91916#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [All bisected] Render error when running Unigine-Heave_v4.0"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91916">bug 91916</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 reply to Matt Turner from <a href="show_bug.cgi?id=91916#c8">comment #8</a>)
<span class="quote">> Well, the report says they are using 4.0. Maybe some of the workarounds were
> actually applicable to 4.0?</span >
Looking at info in QA wiki, Heaven v4 is run with;
export force_glsl_extensions_warn=true
export MESA_EXTENSION_OVERRIDE="-GL_ARB_sample_shading"
./bin/heaven_x64 ... -extern_define PHORONIX,RELEASE
And this is what's removed from the drirc by the commit:
- <option name="force_glsl_extensions_warn" value="true" />
- <option name="disable_blend_func_extended" value="true" />
- <option name="force_glsl_version" value="130" />
- <option name="disable_shader_bit_encoding" value="true" />
As the commit mentions tessalation, and I've always run Heaven with:
-extern_define
,BENCHMARK,RELEASE,LANGUAGE_EN,QUALITY_HIGH,TESSELLATION_DISABLED
I wonder would TESSALATION_DISABLED option for Heaven change anything?</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>