Almar Klein

> So maybe working with references and views and command buffers is a good idea. That's definitely the idea! I imagine something like this: ```py from pygfx import Texture from...

> I now wonder if the offscreen canvas could be the intermediate that handles a swap chain etc. I'm not sure if I fully follow you. But in any case,...

> But you can create a resource with both and then deconflict with views. If that's the case, that'd be great! Indeed views can still conflict, but in cases where...

https://jinja.palletsprojects.com/en/stable/templates/#template-inheritance I'll have a look, and create an example that uses this trick. We probably need to add these blocks in our shader, but it seems simple enough!

I'm on holiday right now with very little time (and very bad wifi), will review/help when I'm back.

Did the null pointers in the capabilities also happen in previous versions, or is this new? It sounds like a bug in the driver or wgpu-core, you'd expect at least...

I pushed a change that I hope is a workaround for the issue with null-pointers in the capabilities struct. Basically we assume that adapter is capable of anything. Not ideal,...

I booted a Windows machine and I can reproduce the problem 🚀

Hi @rajveermalviya, thanks for chiming in! The situation seems related to us having been very lazy about passing `surface_if` into `WGPURequestAdapterOptions`, simply setting it to NULL. This e.g. allows creating...

Since the resulting struct has zero formats, not even bgra8unorm_srgb and fifo, it looks like we don't get the default, but something less than that.