Copy link to clipboard
Copied
PS 25.0.0 20230906.r.37 b14e317 x64
Windows 11 Pro 22H2, Build 22621.2428
I am using Photoshop with an XP-Pen Artist PRO 16TP display tablet.
I have this really annoying problem that often when I'm drawing in Photoshop the cursor turns into the generic Windows arrow cursor and no longer lets me edit the open file, for instance I can't use the brush tool anymore. So, if I press b to select the brush tool, nothing happens and the generic windows arrow cursor remains. If I click on for instance a different history state, the
However, if I open a new file (without even closing the current file or photoshop), I can use the brush tool there (and the pressure is working). So it is as though the display-tablet-pen is working perfectly fine except for in that one open file. When I close the file and open it again it now works.
Is there something that I am missing here?
Adobe Photoshop Version: 25.0.0 20230906.r.37 b14e317 x64
Number of Launches: 60
Operating System: Windows 11 64-bit
Version: 11 or greater 10.0.22621.2428
System architecture: Intel CPU Family:6, Model:7, Stepping:1 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, AVX, AVX2, AVX-VNNI, HybridCPU(8:16), HyperThreading
Physical processor count: 24
Logical processor count: 32
Processor speed: 2419 MHz
Built-in memory: 32368 MB
Free memory: 20452 MB
Memory available to Photoshop: 24871 MB
Memory used by Photoshop: 69 %
Crash Handler: Adobe
DCX Version: 7.1.5
SAM SDK Version: 4.1.4
ACP.local Status:
- SDK Version: 3.2.0.1
- Core Sync Status: Reachable and compatible
- Core Sync Running: 6.6.4.2
- Min Core Sync Required: 4.3.66.28
Live Edit Client SDK Version: 4.0.0
C2PA library version: adobe_c2pa/0.7.6 c2pa-rs/0.25.2
NGL Version: 1.35.0.19
D3D12Warp renderer: Disabled.
Manta Canvas: Enabled.
Alias Layers: Disabled.
Highbeam: Disabled.
Pentablet
Spec Version 1.1
Impl Version 1.0
Num Devices 1
Image tile size: 1024K
Image cache levels: 6
Font Preview: Medium
HarfBuzz Version: 4.3.0
TextEngine: Unified Text Engine
======= GPU
Native API stable: True
OpenGL API stable: True
OpenCL API stable: True
GPUDeny: 0
GPUForce: 0
useGPU: 1
useOpenCL: 1
isGPUCapable: 1
GPUName: NVIDIA RTX 4000 Ada Generation Laptop GPU
GPUVendor: NVIDIA
IsNativeGPUCapable: 1
IsOpenGLGPUCapable: 1
IsOpenCLGPUCapable: 1
HasSufficientRAM: 1
GPU accessible RAM: 12,011 MB
Required GPU accessible RAM: 1,500 MB
UseGraphicsProcessorChecked: 1
UseOpenCLChecked: 1
Windows remote desktop: 0
Windows available feature level: 12.2
Windows required feature level: 12.0
Windows has required feature level: 1
Display: 1
Display Bounds: top=0, left=0, bottom=2160, right=3840
Display Type: SDR
Copy link to clipboard
Copied
So, an update is that when I uncheck "Use graphics processor" in Performance settings, the problem seems to go away, but a different problem now pops up: after a while of everything working fine, when I press for instance the b key to use the brush tool, it will revert back to whatever I was using right before, for instance the zoom tool. This is the behaviour you would expect from holding the b button rather than simply tapping it. It interrupts my workflow tremendously.
I use a bluetooth keyboard (Logitech K380), so I'll try it with another keyboard and see if that helps.
But I'd like to know if anyone has any ideas of what would cause this behaviour? Is there a specific key that would cause this behaviour when pressed?
Copy link to clipboard
Copied
I have a 22E and it's giving me issues. The stoke that shows is way shorter than the physical stroke. It's like the pen can't keep up all of a sudden. It was with the last update from 2023 to 2024. I live by this monitor, so yah, this is a BIG issue.
Copy link to clipboard
Copied
I just re-installed 24.7.1 and no issues. Something in the update.
Copy link to clipboard
Copied
Ah I wish that solved it for me! I've tried PS 25, 24 and 22 and all different versions of Nvidia drivers and XP Pen drivers. Still not working for me 😩
Copy link to clipboard
Copied
Did you check to see if the "Supports Digital Ink" was checked?
Copy link to clipboard
Copied
Also, double check your drivers, these monitors are sensitive to having the exact right driver.