<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - Fix Mesa bugs for running Unreal Engine 4.1 Cave effects demo compiled for Linux"
href="https://bugs.freedesktop.org/show_bug.cgi?id=78716#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - Fix Mesa bugs for running Unreal Engine 4.1 Cave effects demo compiled for Linux"
href="https://bugs.freedesktop.org/show_bug.cgi?id=78716">bug 78716</a>
from <span class="vcard"><a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=78716#c5">comment #5</a>)
<span class="quote">> sad to see this bug closed hope still you reopen bug for reasons said below..</span >
If you hit an actual bug in Mesa, file a report describing that bug with all
the necessary information. This kind of vague 'any bugs which might happen with
some app, if it did run' is not very useful.
<span class="quote">> perhaps they forgot to omit this queries in GL3 path..</span >
That would be fine, if they didn't then crash with an assertion failure if the
OpenGL implementation doesn't know anything about the values queried. That
makes it a non-starter right now.
<span class="quote">> If you don't reopen this bug can I reopen other with a apitrace trace of the
> demo avoiding this queries?</span >
If the apitrace demonstrates a specific bug in Mesa, it would be a good
addition for a bug report as described above.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>