penguin42 @penguin42@mastodon.org.uk

Hmm; I might have a vulkan(o) swapchain::surface from my gtk-rs window - not sure but it's not crashed yet; still got to wire up a swapchain. I did get a "'function pointer `DestroySurfaceKHR` not loaded" when trying to destroy it (accidentally) - but hmm not sure where that's from.

At the point in using a comms library of figuring out which direction 'in' is

The problem with uhd monitors is they get uhd gunge stuck on them

#rust's 'use' syntax can make things confusing; I was following #gtk-rs's code and got confused by:
let ret = from_glib_none(ffi::gdk_window_get_device_position(....))

so I need the ffi crate? No! Because there's a use which renames:
extern crate gdk_sys as ffi;
🔨

All 3 of the #Manchester maplin shops are now shut, a shame, but it can never be said they had good prices or stock levels. I do wonder what happened to the 128MB dimm one of them still had as of a few weeks back

Bleh! Hayfever

My vulkan(o) mandbulb is getting better; sped it up, cleaned a lot of the nasty bits; nastiest bit left is the glue to gtk-rs; I'm just using a compute shader to generate an image as bytes; it should be possible to get vulkano to render directly - but it needs at least some glue to wire up display surfaces; but vulkano only seems to have that for the winit library. Hmm.

if ev is a vec3 then length(ev) and ev.length() are very different in GLSL; I think ev.length() is the length of the vector (ie number of elements, 3) and length(ev) is the geometric length of the vector. Only took a couple of hours, sigh.

TIL: glsl silently ignores 'lowp' size directives in array declarations in buffers (thanks to 'derhass' in ##OpenGL for letting me in on the secret). I see glslandvalidator does change a decoration on the parameter, but that seems to be as far as it goes. Anyway, I think I've now got my mandelbulb being calculated in Vulkan; now can I display it.

Heck, I think I may have managed to execute a vulkan compute shader with vulkano; not actually managed to extract the result yet to know, but it's taking vaguely the right amount of time.

This is somewhere between genius and madness: https://www.emojicode.org/ - the docs are great 'A true value is created using 👍 and a false value is created using 👎' or 'The 🍋 statement is only executed if the preceding 🍊 expression and any preceding 🍋 expressions evaluated to 👎, and the current 🍋 expression evaluated to 👍.'

It's really odd; maplin staff haven't been given closing dates for stores yet suggesting they've got at least one more week, but many are pretty much down to the dregs

Definitely dont understand the layouts in Vulkano; it's all commented aobut how you've got to be really really careful with it or it'll explode on calling into Vulkan; but then the only example seems to be a dummy.

I think I've just loaded a shader, a bit difficult to tell....

Tries to get his head around GLSL compute shader syntax; pointers to nice intros appreciated.

then there's the privacy policy updates from companies I've never heard of and never knew I was connected with.

Everyone of the 'privacy policy updates' uses tracking links. Sigh