Copy link to clipboard
Can anyone confirm or refute that the Dell XPS 2-in-1 (4k i7 build, with Iris Plus graphics) should be able to run GPU image processing?It seems that only basic acceleration is allowed to be enabled.
Lightroom version: 3.0 [ 20191017-0835-b386176 ] (Oct 17 2019)
NGL Version: 126.96.36.199
Operating system: Windows 10
OS Version: 10.0 
Application architecture: x64
System architecture: x64
Computer model: Dell Inc. XPS 13 7390 2-in-1 / Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz
Logical processor count: 8
Processor speed: 1.4 GHz
Built-in memory: 32537.6 MB
Real memory available to Lightroom: 32537.6 MB
Real memory used by Lightroom: 5184.2 MB (15.9%)
Virtual memory used by Lightroom: 5334.7 MB
Memory cache size: 6579.3 MB
Internal Camera Raw version: 12.0 [ 321 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 1940MB / 16268MB (11%)
Camera Raw real memory: 1942MB / 32537MB (5%)
System DPI setting: 216 DPI (high DPI mode)
Desktop composition enabled: Yes
Displays: 1) 3840x2400
Input types: Multitouch: Yes, Integrated touch: Yes, Integrated pen: Yes, External touch: No, External pen: No, Keyboard: Yes
Graphics Processor Info: DirectX: Intel(R) Iris(R) Plus Graphics (188.8.131.5272)
Graphics Processor Detail: loaded: Yes, supported: Yes, compute: No, init: I2_GPU2, hard: fail_cached_sanity_test, soft: not_checked, wl: No, bl: No
OS Media Capability: true
Application folder: C:\Program Files\Adobe\Adobe Lightroom CC
Settings Folder: C:\Users\jason\AppData\Roaming\Adobe\Lightroom CC
I also have this issue on a HP Spectre x360 2-in-1 with the Core i7-1065G7 (Ice Lake). So it seems to be an issue with that processor and not the Dell system specifically.
i have the same issue - dell xps 2-in-1 (4k i7 build, with Iris Plus graphics as well).
Any luck with driver updates?
The driver update didn't do it alone, the latest Lightroom CC update seems to have enabled everything.
I'm on the nvidia OEM drivers now rather than the Dell repacked ones, not sure if it mattered or if it was just a bug. But it seems resolved now.