Sit doesn't seem to be bevy's asset system? i can create a new image handle every frame, even insert a new bevy gpu texture backed by the same wgpu texture without flicker, i think its the import? idk how flicker happened on the old shm impl tho
Smaybe importing the dmatex clears the underlying image?
Smaybe because i have to import it with an
ImageLayout::Undefined and moving from that to any other layout like ImageLayout::General clears the image to black iircSthat would explain why the import is fully stable after i moved the actual import into the zbus handler, i await the function on the export side and only write to the texture after that, before it was basically a race condition ig
Stho that would assume that wgpu somehow changes the
ImageLayout while creating a wgpu texture from the raw textureSsomeone else is doing dmabuf in vulkan!!!! https://community.khronos.org/t/barriers-for-external-image-in-dma-buffer/111513
Saaaand no replies after 6 months, that's not surprising...
Safter talking to chatgpt for a bit i think i need to add a memory barrier for an image layout transition
Salso wow using ash directly is so annoying for this when compared to vulkano
Sno, its not as simple as a memory barrier
Snot knowing vulkan and gpu(cpu is similar i believe) memory visibility and flushing caches is biting me rn
Si will continue work on this tomorrow
Svulkan basically requires you to flush memory and manage cache updating manually, kinda like what the atomic
Ordering does, except more manual
Nbtw blender 4.5 with vulkan backing uses dmatex in stardust
Nwhich is amazing
Nit chose it!!!! finally!!!!
Nnothing else really did but it's a solid real world dmatex test case, one that's not the weston-simple-dmabuf-egl
Nand it flickers sooo
Nhope that helps
Ndeep research can help a ton here, you can get it to look up all of this autonomously and make a report
Nwait... blender gl backend fails but vk backend doesn't??
Nhmm strange
Nvk clients work on the vk compositor but gl clients don't... hmmm
NNEVER MIND BLENDER WORKS IN BOTH CASES AS OF 4.5
NNi mean the gl one doesn't register as sRGB correctly (maybe a format bevy dmabuf doesn't convert?)
Nalso the fps isn't the best (this is a 144Hz monitor with frametime limited to 60)
Nstill feels a bit janky though... like it misses some inputs or the dmabuf doesn't update really quite right?
Ni think that's frame timings though
Nwait woahhh whatt
Nuhhh
Nuhhhhhhhhhhhh!!!!!!!!!!1
Nidk what the hell happened but DMABUFS WORK PRETTY DARN WELL NOW
Nneverball works
Nlike, it just works
Nmaybe my system was like, hella broken???!?!??
Nbut it works flawlessly now
Nidk i pushed my changes
Nso like ?!?!?!??!
Nit workies
Nnot shm though, that's still flickery as hell
N!?!?!?!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!1
Nwait wait wait wait wait idk what happened but there's no more global flicker afaik
Nit's uh, now it's like there's a race condition in uploading shm data to gpu
Nok nvm neverball still flickers but interestingly on the 144Hz monitor it's a lot harder to percieve
N!!!!!!!!!!!!!!!
Nwait wait wait wait huge clue
Nmassive clue
Nall the materials that are like... shadeless disappear at the same time
Nwait no because the lines are still there
