hm weird. i have a laptop with uhd 620 and it works. seems to be a driver difference between linux and windows, where the windows version does not shot yuv support in vulkan.
okay now this is more the monster here 
glad to hear it works.
i guess you want the howtos and the module docs, not that it’s very detailed either.
Hello @hanatos
hm weird. i have a laptop with uhd 620 and it works. seems to be a driver difference between linux and windows, where the windows version does not shot yuv support in vulkan.
Quite likely 
Thanks for the documentation link. I am going to read it for sure!
Now, IMHO, the more pressing missing feature is the lack of support for the Windows file system.
As already reported, it is not possible to search for files other than in C (other partitions are not available in the search)
I have noticed you are already working on this feature on github.
While testing, I have also remarked you can not drag and drop a single RAW file into the GUIs (from C:) but I suppose vkdt does not work as GIMP or other softwares in this respect.
RawTherapee does not support this option either (you are always first supposed to import the single image)
right. i think i may even have deleted some code with respect to that because i didn’t understand. sorry, hard to think in non-single-rooted file systems once you’re socialised the other way… should not be hard to fix but i don’t routinely work on a windows machine so it might take me some time.
ah good. i opened an issue for this so i won’t forget. i don’t really use graphical file managers so i’d never get this idea myself. fwiw you can pass single raw file names on the cmdline. i suppose it would work to drag/drop the file onto vkdt.exe in the file manager.
My DAM is the OS file manager, either Linux or Windows, and I drag/drop files from there to a desktop icon of rawproc, and vkdt for that matter, and both open the file with aplomb. If you’re set to open a file provided by the command line, you’re good to go in one use case.
Now, if you want to drag a file to an open instance of a program that’s a different thing.
Also, in Windows I’ve had no problem recognizing other drives or even network fileshares in the programs i write, not sure what’s the complication…
i think it’s just me. i implemented folder navigation to go up and down but no text input to actually edit the path. maybe that would be the simplest fix actually.
Hello @hanatos
Just tried on a different pc:
Operating System: Windows 10 Home 64-bit (10.0, Build 19045) (19041.vb_release.191206-1406)
Processor: Intel(R) Core™ i7-10710U CPU @ 1.10GHz (12 CPUs), ~1.6GHz
Memory: 16384M
Card name: NVIDIA GeForce GTX 1650 with Max-Q Design
Vkdt runs well.
However, In the long run, it tends to freeze, in that the GUIs become unresponsive and I am forced to kill it through the CMD.
Aside from this, I am reading the documentation.
Therefore, I am a bit ashamed to ask because, quite likely, I am missing something…
Is there a picker, in the GUIs, to quickly set the white balance (as in other softwares: RawTherapee etc)?
Currently, I am moving the slides to correct the colour cast…
great
hmm hard to diagnose from this. let me know if you find out more. maybe adding -d all -D perf outputs something intelligible?
yes, there’s the pick module but to save you the hassle of connecting it yourself, there’s also the pick-neutral.pst preset, which you can select by pressing ctrl-p in darkroom mode to apply presets (or find the preset button in the ui, or maybe you have bound it to another shortcut). this basic colour stuff is discussed here, see the white balancing section. you can also pick skin tones instead of neutral. to select the spot you would navigate to tweak all → pick 01 and push the button for the spot you want to edit. with the preset there’s just one, 00.
Hello @hanatos
Yep. I know 
Now, It is working flawless.
There is no way to reproduce this previous glitch…
I am also following your documentation with new stuff to test and everything looks fine (even though I am a rookie…)
Indeed, yours, is a veeery powerful software…
Thanks a lot for your help!
Hello @hanatos
Just out of sheer curiosity since Windows 8.1 was still missing from my tests…
It has been discontinued from Microsoft itself (January 2023) therefore it is not worthy any bugfixing from your side…
I have run this Asus laptop on a daily basis for the last 10 years without ever a single glitch.
Sooner or later, perhaps, it will rest in peace (hardware failing, who knows…)
Operating System: Windows 8.1 64-bit (6.3, Build 9600) (9600.winblue_ltsb_escrow.221111-1730)
Processor: Intel(R) Core™ i7-3537U CPU @ 2.00GHz (4 CPUs), ~2.5GHz
Memory: 8192MB RAM
Card: NVIDIA GeForce GT 740M
Vkdt does not start (vkBindlmageMemory2 not found)
hmm vulkan sdk/driver too old? i have no idea how versioning/backporting of stuff works on windows. quite possible that libvulkan delegates to a driver that doesn’t speak vulkan 1.2 or some such.
thanks a lot
just tried, i have to find my way to test some photo dev
windows 11 Version 10.0.22631 Build 22631
11th Gen Intel(R) Core™ i7-1165G7 @ 2.80GHz, 2803 MHz, 4 cœur(s), 8 processeur(s) logique(s)
32 Gb
GPU Intel(R) Iris(R) Xe Graphics
Did you build it or use the nightly … Using the nightly and unzipping it and trying to run it I get a terminal window that I see a few lines appear in, maybe 4 or 5 and its in a flash so I can’t read it… Then I get a white screen like it is going to load and then it just closes after that flashes…
Terminal I think has this.
is that the link from this thread or the new/experimental package from the github nightly release? the latter i never tested… i only hope it works
and could you start from a terminal and pass vkdt.exe -d all -D perf as arguments? it would display search paths and maybe some more information to double check it all works as expected. maybe i should make extra verbose mode the default on windows…
Thanks for the reply… at work now but I will give it a shot tonight when I am home…
Thanks again…
Best
Todd
Hello everyone,
Just tried the nightly build and it does not work:
Operating System: Windows 10 Home 64-bit (10.0, Build 19045) (19041.vb_release.191206-1406)
Processor: Intel(R) Core™ i7-10710U CPU @ 1.10GHz (12 CPUs), ~1.6GHz
Memory: 16384M
Card name: NVIDIA GeForce GTX 1650 with Max-Q Design
The GUIs starts but it is unable to load the thumbnails.
Tried also through the CMD with vkdt.exe -d all -D perf but the final “interesting” log is quite short: “Unable to load the thumbnails > unable to load the images”.
On the contrary, the original ZIP version works fine: same RAWs images tested.
Therefore I am going to stick with this version. On this same computer it works great
thanks again for this win version
from link of this thread with vkdt.exe -d all -D perf,
vkdt crashs opening new images in a new collection (directory) but not always
[mem] staging: peak rss 38.9562 MB vmsize 38.9562 MB
then after restart:
[i-bc1] C:\Users\olivier/vkdt/cache/6360beea631b0564.bc1: can't open file!
[i-bc1] C:\Users\olivier/vkdt/cache/6360beea631b0564.bc1: wrong magic number or version!
other : metadata : path cannot be found → i guess path of exiftool or another tools is missing
windows 11 Version 10.0.22631 Build 22631
11th Gen Intel(R) Core™ i7-1165G7 @ 2.80GHz, 4 cores, 8 logic processors
32 Gb 15 Gb shared with GPU Intel(R) Iris(R) Xe Graphics
Downloaded the nightly, didn’t expect it to work on my Microsoft Surface 7 tablet, but here’s what I got for the record:
$ ./vkdt.exe -d all -D perf
[pipe] base directory C:\Users\glenn\Desktop\vkdt-0.7.99-165-g6411f83a
[pipe] home directory C:\Users\glenn/vkdt/config
[pipe] loaded 76 modules
[gui] glfwGetVersionString() : 3.3.8 Win32 WGL EGL OSMesa MinGW
[gui] monitor [0] Surface Panel at 0 0
[gui] vk extension required by GLFW:
[gui] VK_KHR_surface
[gui] VK_KHR_win32_surface
[qvk] dev 0: vendorid 0x8086
[qvk] dev 0: Intel(R) Iris(R) Plus Graphics
[qvk] max number of allocations 1028374
[qvk] max image allocation size 16384 x 16384
[qvk] max uniform buffer range 4294967295
[qvk] num queue families: 1
[qvk] picked device 0 without ray tracing and without float atomics and without coopmat support
[qvk] validation layer: Loading layer library C:\ProgramData\obs-studio-hook\.\graphics-hook64.dll
[ERR] yuv (G8_B8R8_2PLANE_420) not supported!
[ERR] init vulkan failed
[ERR] failed to init gui/swapchain
for the record also, the booting is ok but after it’s at random
PS C:\Users\olivier\Downloads\vkdt-nightly-w64\vkdt-0.7.99-165-g6411f83a> ./vkdt.exe -d all -D perf
[pipe] base directory C:\Users\olivier\Downloads\vkdt-nightly-w64\vkdt-0.7.99-165-g6411f83a
[pipe] home directory C:\Users\olivier/vkdt/config
[pipe] loaded 76 modules
[gui] glfwGetVersionString() : 3.3.8 Win32 WGL EGL OSMesa MinGW
[gui] monitor [0] Generic PnP Monitor at 0 0
[gui] monitor [1] Generic PnP Monitor at 1920 17
[gui] monitor [2] Generic PnP Monitor at 0 -1050
[gui] vk extension required by GLFW:
[gui] VK_KHR_surface
[gui] VK_KHR_win32_surface
[qvk] dev 0: vendorid 0x8086
[qvk] dev 0: Intel(R) Iris(R) Xe Graphics
[qvk] max number of allocations 4188197
[qvk] max image allocation size 16384 x 16384
[qvk] max uniform buffer range 134217724
[qvk] num queue families: 2
[qvk] picked device 0 without ray tracing and without float atomics and without coopmat support
[qvk] available surface formats:
[qvk] B8G8R8A8_UNORM
[qvk] B8G8R8A8_SRGB
[qvk] R8G8B8A8_UNORM
[qvk] R8G8B8A8_SRGB
[qvk] colour space: 0
[gui] no joysticks found
[gui] you have more than 2 monitors attached! only the first two will be colour managed!
[gui] no display profile file display.Generic PnP Monitor, using sRGB!
[gui] no display profile file display.Generic PnP Monitor, using sRGB!
[qvk] available surface formats:
[qvk] B8G8R8A8_UNORM
[qvk] B8G8R8A8_SRGB
[qvk] R8G8B8A8_UNORM
[qvk] R8G8B8A8_SRGB
[qvk] colour space: 0
[db] allocating 1024.0 MB for thumbnails
[mem] images : peak rss 0.00390625 MB vmsize 0.00390625 MB
[mem] buffers: peak rss 0 MB vmsize 0 MB
[mem] staging: peak rss 0.000244141 MB vmsize 0.000244141 MB
[perf] time to load images 0.011s
etc...
okay thanks for the detailed log though. “no float atomics” is one thing i might want to double check is working reliably (has separate code paths that i don’t tend to test much). random crashes never sound overy encouraging. on the bright side there’s really not much threading on the cpu side going on. i’m struggling with async vkQueueSubmit calls with nvidia drivers occasionally, hope that’s not an issue.
the bc1 thumbnails might be partial files for random crashes, so not being able to load them next time is kinda expected on windows (on linux i write them to a temp file and place a hard link once done, but windows currently copies instead of hard linking… though i saw newer windows does support both symlinks and hard links). maybe cleaning the quoted cache/ directory is not a bad idea 