hi all, i just packaged up a new feature release for vkdt, 0.9.0. this is mainly about replacing the c++ dear imgui library by the c nuklear library, and comes with a lot of ui changes.
a more detailed changelog can be found in the github release notes.
here’s a screenshot of my Pictures i.e. playraw folder:
enjoy!
Time to start packaging!
Thanks! I just had a play with it on Windows. Seems to be working well and it’s super fast. Now I just need to learn how to use it properly!
Wayland and GPU drivers: buggy af 
yeah had much fun with wayland lately… will have to bundle up 0.9.1 soon, with a few fixes and workarounds. the amdvlk vulkan implementation has some issues, use radv.
Did you build it or use the zip file… For me it crashes trying to run the exe file. I’ll try the command line tonight when I get home…
Hello @priort
Tested on Windows 11:
Processor: 12th Gen Intel(R) Core™ i7-12700H (20 CPUs), ~2.7GHz
Memory: 32768MB RAM
Card name: NVIDIA GeForce RTX 3070 Ti Laptop GPU
It works without problem (e.g. by clicking on the .exe).
Super fast and no crash whatsoever
Compared to previous versions it is also possible to open files in different partitions of my computer
It is a pity there is not some video tutorial to better understand its workflow. The documentation on github is fine but some video tutorial would be magnificent (e.g. for using the node editor) 
Thanks for the feedback…I have fairly similar configuration but a desktop… I have the 12gen i5 with a 3060Ti latest driver from Oct 15th and 64 GB memory…running on Win11…
I will see if a command line will run and if not if I can get some debugging info from that…
I just unzipped it in my downloads folder and ran it from there… I wonder if there is some sort of path issue I have created by doing that??
I just used the exe from the zip file. Ran fine for me.
I just unzipped it in my downloads folder and ran it from there
I did the same
Just tested the CLI (cmd.exe) and it works as expected.
Thanks …I just tried it on my laptop at work mind you where maybe the security stuff is kicking in but it starts to open a window named vkdt and then the mouse pointer spins busy for about 5 seconds…nothing makes it to the screen and the window closes. I think I saw the same at home but I will try again and see if I can generate a log or notice a status while it tries to open…
Work PC is Win11 Pro… 13th gen CPU 32GB DDR5 and Nvidia A500 graphics card.
Its working for you and @europlatus so I am sure its something on my end…
I’m running Win 10 with a 5700X3D CPU and 6700XT graphics card just as an FYI.
hi all, i just released 0.9.1, a small point release update with some wayland fixes. this is mainly interesting for packagers i suppose, as an end user i’d use the nightly packages (these have the wayland fixes and additional features).
You’re the best, thanks!
Very stoked to try vkdt for the first time in ages during the holidays! Saw that 0.9.1 is up. Do you plan on making AppImages available for this version too?
Also, do you know if someone has made a friendly introduction video to vkdt? Can’t find a single clip on YouTube.
i would recommend to just use the nightly appimages. the release is just older, not any more stable.
sorry, i guess i’m not very friendly or into yt, i wouldn’t know if there are friendly videos… 
i have recorded some demo videos in the past, but more as answers to specfic questions. as a starting point maybe the howto section here is useful: vkdt website and documentation
Gotcha, thanks!
Perhaps someone else will chime in and say they recorded an intro video
Ok, maybe I’m telling you nonsense, but I exported an image to jpg and exr, and then opened the exports in Gimp:
exr:
jpg:
shouldn’t they look the same? The jpg looks like expected, but if I want to goon with gimp, I’d like to use an uncompressed image, like exr (I think), but what I get is something different.
Footnote:
When I noticed the behaviour the first time I tried to reproduced this. I just did some slight edits to see if they were exported to jpg and exr. The images here shown are exports from Gimp to show the difference.
how did you export the exr? in particular what’s the colour setup/trc/primaries?
and what did gimp interpret it as? in particular exr is always assumed to be linear trc by the spec and by gimp. vkdt will still let you export it to sRGB trc if you so choose. that’s exactly how your image looks like. gimp loads it and assumes linear sRGB, and you exported to trc sRGB primaries sRGB.
btw if you export to rec2020 primaries, you need to assign the BT2020 profile in gimp, it does not read the exr primaries tag.
Err, one should generally not export to EXR w/ a TRC, it’s meant for linear data. Gimp probably just applied yet another sRGB one on top.
