<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - r600_shader_from_tgsi - GPR limit exceeded - shader requires 360 registers" href="https://bugs.freedesktop.org/show_bug.cgi?id=105371#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - r600_shader_from_tgsi - GPR limit exceeded - shader requires 360 registers" href="https://bugs.freedesktop.org/show_bug.cgi?id=105371">bug 105371</a> from <a class="email" href="mailto:gw.fossdev@gmail.com" title="Gert Wollny <gw.fossdev@gmail.com>"> Gert Wollny</a> <pre>I had a look at VSM versus ESM, and I see a difference that would indicate an error in the ESM shader (be it in blender or the drivers), but there is no specific output (like given in this bug) that would indicate where the problem lies. If you have an example that gives this output like given above, then please add the steps to reproduce this view in blender. For all other failures please add such comments to the other bug report: <a class="bz_bug_link bz_status_NEW " title="NEW - BLENDER 2.8 principled BSDF shader and shadow are broken in EEVEE on mesa gallium r600g gpu" href="show_bug.cgi?id=107454">https://bugs.freedesktop.org/show_bug.cgi?id=107454</a> You can also try to create a rendering trace by using apitrace: <a href="https://github.com/apitrace/apitrace">https://github.com/apitrace/apitrace</a> run "apitrace trace blender"), get to the point where things go wrong in blender, and after it has made visible you can just close blender and then try to attach the resulting blender.trace file to the bug. It is best to open a new bug for each issue. Best, Gert</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>