Sorry, what need to be in a specific folder? The Cache is located in INetCache, it got re-build after renaming.
But it seems that both the installed dt and the USB one use the same INetCache location.
I probably give up on the home PC and openCL. Just checked my office PC (I thought I bought it around the same time a bit later), home PC is i3 gen4 (came out 2014), office is i3 gen6 (2015). LUT works fine on the office PC.
The home PC has 4400 graphic, office has HD530.
Not sure if a cheap graphic card in the home PC will help, plus, I feel hesitant to throw good money after bad money. I will probably just use the notebook at home (works fine) and get a mouse (dt isn’t really designed for touch pad). Not a big issue.
I have a desktop computer with intel i7 8700 (8th gen, I think?) processor with an integrated intel HD 630.
Drivers in intel have had some issues with opencl, as you probably know.
In some upgrade of drivers intel even removed opencl completely due to that.
But the lasts versions seem to have opencl working correctly (I am using it in capture one).
Last driver reports opencl 2.1 NEO as its opencl motor.
Yours seems to be quite older (1.2) in a less capable integrated graphic board.
What surprises me is that you can even enable opencl? (but of course it is obvious that you can).
Due to problems with opencl, darktable has dropped opencl when you have an intel graphics card.
When you run darktable_cltest you get something like:
discarding device 0 Intel(R) UHD Graphics 630' because the driver OpenCL 2.1 NEO ’ is blacklisted.
Later darktable developers have reenabled opencl in intel boards under Linux, as the new NEO motor seems to work properly.
But they have kept it blacklisted under windows. It seems that nobody has tested it under windows and there are few darktable developers in windows.
So I cannot enable opencl.
But you seem to be running darktable in windows in an intel board and with opencl running.
Which version of darktable are you using? Which versions of intel drivers?
I’ve had a look at your log files. For each of them open cl starts properly (including lut3d).
So the open cl error happens later on… Don’t know how we can track this.
Could you launch dt on cmd console with the options -d all > log.txt, open the faulty image / lut3d (like on the screenshot you have shared), exit dt and share the file log.txt ?
Sharing an example of the faulty lut3d file could also help.
Tried, not working. It was somehow expected, remember, USB dt on the laptop works, in the home PC doesn’t work. And the darktablerc is on the USB drive. So it’s the same darktablerc that works on one PC but not on the other.
The problem is with the PC, not darktable I guess. The Sigma Photo software runs also in snail speed. I will look deeper into the PCs graphic drivers.
In the meantime I tried different Intel VGA drivers. I installed GPU_Caps_Viewer to check if openCL really works (it does).
I am still puzzled why I see the LUT applied in the darkroom preview, but not in the main edit screen.
Then, when I re-scale the main edit screen to i.e. ‘small’ I see the LUT applied in the main edit screen for a fraction of a Second. Strange.
I’ve seen that your intel GPU has less memory than the other one. That may be a part of the explanation.
But we should get somewhere an error message (I have not seen any in your log files)…