nroberts changed the topic of #videocore to: Raspberry Pi Mesa drivers discussion - Logs http://freenode.irclog.whitequark.org/videocore
jcea has quit [Ping timeout: 250 seconds]
gpoo has quit [Remote host closed the connection]
itoral has joined #videocore
abergmeier has quit [Quit: Idle for 30+ days]
itoral has quit [Quit: Leaving]
jcea has joined #videocore
<turol> so I've found a bug in the Vulkan driver
<turol> the TL;DR is that https://github.com/turol/smaaDemo renders SMAA effect incorrectly when it works everywhere else
<turol> what kind of things do you want in the bug report?
<turol> screen shots? trace of some kind? the shaders (really complicated)?
txenoo has joined #videocore
<chema[m]> turol: If you can fill as much as possible from the Bug Report template it would be nice. Include v3dv at the beginning of the tittle to make it easy to identify. https://gitlab.freedesktop.org/mesa/mesa/-/issues/new
<chema[m]> Screenshots, apitrace dump or shaders would be welcome.
<chema[m]> Sowing the expected and correct screenshot will help too.
<chema[m]> s/correct/wrong/
<turol> does apitrace do vulkan traces?
<turol> i could do renderdoc
<turol> i might also be able to use gfxreconstruct but that requires compiling
<turol> just compiling the latest validation layer was an adventure
<turol> and apparently just looking at the new bug page (and the template) requires a login
<turol> have to make one of those first...
gpoo has joined #videocore
<apinheiro[m]> somewhat late to the chat but
<apinheiro[m]> turol: in my experience building renderdoc or gfxreconstruct needed the same effort
<apinheiro[m]> having said so, any of them would be welcome, so just use the one easier for you