ChanServ changed the topic of #zink to: official development channel for the mesa3d zink driver || https://docs.mesa3d.org/drivers/zink.html
alyssa has left #zink [#zink]
Soroush_ has joined #zink
Soroush has quit [Ping timeout: 480 seconds]
justsid has joined #zink
<xperia64> I cannot for the life of me get wglgears working
<zmike> I think you just copy the files to the app directory and set GALLIUM_DRIVER=zink
eukara_ has joined #zink
eukara has quit [Ping timeout: 480 seconds]
justsid has quit [Ping timeout: 480 seconds]
xroumegue has quit [Ping timeout: 480 seconds]
xroumegue has joined #zink
justsid has joined #zink
eukara has joined #zink
eukara_ has quit [Read error: Connection reset by peer]
justsid has quit [Ping timeout: 480 seconds]
hch12907 has quit [Ping timeout: 480 seconds]
hch12907 has joined #zink
justsid has joined #zink
<xperia64> is there a proper build of mesa-zink/wglgears I should be using? the only gallium driver I've compiled is zink, so I shouldn't need to set that?
<zmike> there's not currently any fallback path that will auto-select zink
<zmike> so yes, you do need to set it
<xperia64> MSVC mesa+mingw mesa-demos = wglinfo working, wglgears white screen
<xperia64> mingw mesa+mingw mesa-demos = linking/runtime error
<xperia64> mingw or MSVC mesa+Citra = boots games, black screen
<zmike> justsid might have some idea for getting wglgears working
sidney has joined #zink
eukara_ has joined #zink
sidney is now known as Guest447
quantum5_ has joined #zink
justsid has quit [synthon.oftc.net reflection.oftc.net]
eukara has quit [synthon.oftc.net reflection.oftc.net]
quantum5 has quit [synthon.oftc.net reflection.oftc.net]
ajax has quit [synthon.oftc.net reflection.oftc.net]
ajax has joined #zink
Guest447 has quit []
justsid has joined #zink
justsid has quit []
hch12907 has quit [Ping timeout: 480 seconds]
<xperia64> zmike: I'm on 22.1.0-rc5 and didn't have to set GALLIUM_DRIVER=zink for zink to be selected (although setting it makes no difference if things display)
<zmike> oh right wgl
<zmike> shows how often I use it (literally never)
<xperia64> RenderDoc shows Citra+zink as "OpenGL (Active)" and "Vulkan (Not Presenting)" on Windows, going to check what it says on Linux
<xperia64> ok, so "Vulkan (Not Presenting)" is definitely wrong
<zmike> yup, renderdoc and zink don't work great together
<xperia64> no I mean both show as Active in Linux
<zmike> sounds right
<xperia64> I read it more as it's not even trying to present under Windows?
<zmike> could be
<zmike> or could be renderdoc failing to detect it
<zmike> could stick a printf in zink_kopper.c where presents happen and find out
<xperia64> I'll give it a try. I think I finally have a sane build environment so I can actually mess with it now
<xperia64> doesn't even seem like a displaytarget is being created?
<xperia64> lots of code not being hit. need to see what isn't working at the top level
<xperia64> ...ok we never create a drawable
<xperia64> you gotta be kidding, GALLIUM_ZINK isn't being passed to stw_st.c
<xperia64> ok now kopper is probably actually being used on Windows
<xperia64> Not quite Citra but I'll take it: https://i.imgur.com/CWxP2XT.png
<xperia64> and there's Citra: https://i.imgur.com/1BqJJ6M.png
<zmike> \o/
<xperia64> runs at least twice as fast as native AMD OpenGL depending on the scene. OoT intro is ~170-200% max on native, 350-450% max on zink.
<xperia64> should I create an issue for the GALLIUM_ZINK define? A meson.build file needs a tiny change to actually enable kopper
<xperia64> not familiar with the mesa MR process so I'm not sure if it's one of those things that'd be easier for someone else to push :P
<zmike> you can give it a try and I'll help it along
<zmike> basically the same as github