Photoshop Developers

Subject: Camera Raw 18.5+ and Lightroom Classic 15.5+ disable GPU acceleration on Windows 11 Pro (RTX 4060 Ti).Description of Issue: Since Camera Raw version 18.5 (up to 18.7) and Lightroom Classic version 15.5 (up to 15.6), the GPU acceleration for the NVIDIA GeForce RTX 4060 Ti is disabled. The software displays "Graphics processor acceleration is not supported by your system." inside Lightroom and Camera Raw preferences.Steps to Reproduce:    1. Open a RAW photo in Photoshop (Camera Raw 18.5/18.7) or launch Lightroom Classic 15.6.    2. Check Preferences > Performance. Expected Result:GPU should be fully supported, just like in Photoshop's Help > GPU Compatibility check (which correctly shows DirectX 12.2 available and sufficient VRAM).Actual Result:GPU info inside Lightroom/Camera Raw remains completely blank or unsupported.Verified Workaround:Downgrading Photoshop to Camera Raw 18.4 and Lightroom Classic to version 15.4.1 completely resolves the issue, and full GPU accelerat

During the manipulation dock widgets loose his ability to restore preferred width.Please see this video:  Do not hesitate contact me, if you will have a questions.

Adobe Photoshop 27.9.1 — Repeated Native Text Engine Crash During Automated Text Fitting Environment - Application: Adobe Photoshop 27.9.1- Operating system: Windows 10 Pro (Build 19045)- Integration: Photoshop scripting / UXP automation- Crash date: October 26, 2026, at 23:40:09 (UTC+03:00) Problem I am developing an automated text-fitting integration for Adobe Photoshop. During controlled operations involving paragraph text measurement, resizing, and rich text formatting, Photoshop has experienced native crashes. The Adobe Crash Reporter recorded: - Exception: EXCEPTION_ACCESS_VIOLATION- Exception code: 0xc0000005- Crashing function: OptycaImpl::NormalizeInput- Related stack frames:  - InputOutputHBImpl::getInputClusters  - WRFontContextComponent::Info  - OptycaImpl::SetClientEncoding Some controlled text resizing operations succeed, including preserving text styles and undoing changes. However, failures occur in other text-fitting scenarios. A separate rich-text growth preflight als

I am a professional photographer and this issue is seriously affecting my daily work in Photoshop.The problem occurred in Photoshop 27.10 and is still present in Photoshop 27.11.Problem:During active image adjustments, Photoshop displays a dramatically incorrect brightness/tonal appearance. Only after I release the mouse button does the image return to the correct rendering.A very clear example is a Levels adjustment layer:Create or select a Levels adjustment layer. Move one of the sliders. While the slider is being moved, the entire image becomes significantly brighter or darker than the actual adjustment. As soon as the mouse button is released, Photoshop displays the correct result.The problem is not limited to Levels. I also experience similar brightness shifts while retouching, for example when using the Clone Stamp tool.This is reproducible and makes accurate visual image editing extremely difficult, because Photoshop does not show the actual result while an adjustment is being m

I have tried Adobe’s suggestions and some other ways the internet and Ai has suggested to me, even downgrading to previous versions, but it’s been a bug since the Macos 27 update. Could not complete the Export As command because of a program error (854aee.3204).Please fix this asap.  With regards,Joeri Woldberg

EnvironmentVS Code: 1.138.0 (Universal build) OS: macOS 26.6.2, Apple Silicon Extension: ExtendScript Debugger 2.1.0 (Adobe) Target apps tested: Photoshop 2026 (200.064), Illustrator (30.064)IssueRunning or attaching a debug session via VS Code's Run and Debug panel never completes. Selecting "Launch Script in ExtendScript Engine" and pressing F5 (or using the "Eval in Adobe..." status bar action) produces no visible effect:No alert() dialog appears in the target application No error appears in the Debug Console or Extension Host logs No macOS Automation permission prompt is ever shown, and VS Code never appears under System Settings > Privacy & Security > Automation The Run and Debug panel shows a persistent loading/spinner state with no resolutionWhat I've already ruled outTo narrow this down, I loaded the extension's native module directly via Node, bypassing VS Code entirely:jsconst m = require('.../lib/esdebugger-core/mac/esdcorelibinterface.node');m.esdInitialize('vsces

Photoshop unexpectedly sets the active layer's opacity to exactly 50% whenever the Option key is pressed while the cursor is hovering over a button in a custom UXP plugin.The issue occurs consistently, regardless of the active layer's initial opacity. Disabling the button's hover listener eliminates the problem.The plugin does not contain any code that changes layer opacity. Its button "mouseenter" listener is intended to detect the Option key and update the button's displayed text.This appears to be an unintended interaction between the UXP button's hover event handling, modifier-key detection, and Photoshop's native layer-opacity behavior.EnvironmentApplication: Adobe Photoshop 27.11.0 Operating system: macOS Tahoe 26.7.1 Platform: Mac Plugin framework: Adobe UXPSteps to reproduceLaunch Photoshop and open a document containing at least one layer. Select a layer and set its opacity to any value. Open a custom UXP plugin with a "mouseenter" listener added to a button that detects the O

I’ve experienced this issue quite a few times over the last few weeks where I am using Photoshop and the whole menu system becomes inactive, every single option in the menu is greyed out. This is a huge pain as it stops me from saving my progress.I believe the trigger for this is when I go to place an embedded image, the pop-up window opens to show me Finder, I then leave Photoshop for a little while with the window open to use other apps, then when I come back the bug has occurred. I can close the pop-up window but then every menu option is disabled.As I’ve just gone to check which version of Photoshop I am using, by accessing ‘About Photoshop’ within the Photoshop app, the menus have now become active again.I am using Photoshop 27.10.0 on an Apple MacBook using Tahoe 26.6.2. 

PROBLÈMEDepuis plusieurs semaines, Adobe Photoshop 2026 (Windows) affiche l'erreur : "Impossible d'exécuter la commande [X] en raison d'une erreur du programme (b46572.249)."Cette erreur touche plusieurs commandes différentes : Teinte/Saturation, Noir et blanc, et certains outils de sélection. Elle survient sur tous les fichiers, même un document neuf créé dans Photoshop, en 8 bits comme en 16 bits.Autres symptômes associés :Le panneau "Réglages" reste vide en permanence. Le panneau "Outils" ne se charge pas ou charge partiellement. L'export/enregistrement en JPG échoue par moments (message : "Impossible d'écrire le fichier de paramètres prédéfinis du nouveau document"). Édition > Préférences > Performances est parfois inaccessible.CONTEXTELe problème est apparu peu après plusieurs semaines passées à essayer de résoudre un problème de gestion des couleurs à l'impression (imprimante Epson XP-15000), pendant lesquelles logiciels, pilotes et profils colorimétriques ont été manipulés

Photoshop version: 27.10.0Platform: Windows 11ISSUEA .psjs script executes successfully when run from inside Photoshop using:File > Scripts > BrowseHowever, the same type of .psjs script does not execute when launched externally through the Windows registered .psjs file association.The external launch is accepted, but the PSJS payload does not run and its expected diagnostic receipt is not created.EXPECTED RESULTLaunching a .psjs file through its registered Windows association should pass the script to Photoshop and execute it.ACTUAL RESULTWindows/ShellExecute accepts the .psjs launch, but Photoshop does not execute the script.TESTS PERFORMED1. External Windows .psjs launchRegistered file type:Photoshop.PSJSFileType.200Registered command:"Photoshop.exe" "%1"Photoshop was running and responsive.The external launch was accepted, but the diagnostic script did not execute and no receipt was created.2. Internal Photoshop executionI then ran the diagnostic .psjs from:File > Scripts

La edición asistida por IA dejó de funcionar por completo e indica que algo salió mal que lo intentes más tardes. Cada que hacen una actualización empeoran muchas cosas que ya estaban bien.

Ps yi kaldırdım yeniden yükledim ama firefly banana modelinde görsel üretmiyor. 

Tres personas sentadas detrás de una mesa redonda y otras cuatro en la misma situación, no son detectadas pour la opción detectar personas, con el fin de suprimirlas de la foto.Las personas se ven perfectamente  en la imagen, y Son lo suficientemente representativas para ser detectadas.

I've tried changing the language in Photoshop and reinstalling it, but the error persists.I'm trying to use the PhotoMerge feature, but I keep getting an error message. 

I finally had to reinstall the former Photoshop V 27.9 on both my Windows 11 workstation and Windows 11 laptop for the on-device remove tool for using my installed Nvidia RTX 5080/4090 with16GB VRAM. I’m running the current Nvidia Studio Driver 610.88 and the tool runs great and fast!. However, after updating to regular PS V27.9.1, also includes the current PS Beta V27.9.11, the On-Device remove tool to severely stalls and must cancel to avoid long waits. Using the Cloud selection works, only if on WiFi, but I am still waiting for an update fix for the off-line On-Device to function properly. Whatever changes happened in the PS updates, the On Device Tool was affected. This issue has been ongoing for over three months!! BTW - No logs are necessary to collect send as the identical issue can be recreated on any PC using Windows 11 and the RTX having 16GBVram card at Adobe PS lab, then read the log.

 Posted in the wrong community. Please remove or move this thread.Hello,I would like to report a reproducible Photoshop WinTab compatibility issue involving the Wacom Art Pen 2.Environment:- Windows 11 64-bit- Adobe Photoshop 2026: 27.9.1.1- Wacom Intuos Pro M (2025), model PTK670- Wacom Art Pen 2, model ACP70000DZ- Wacom Windows driver: 6.4.13-4- Tablet firmware updated through Wacom Update Utility- Photoshop brush setting:  Brush Settings > Shape Dynamics > Angle Control = RotationSteps to reproduce:1. Enable Windows Ink for Photoshop and remove/disable PSUserConfig.txt.2. Restart Photoshop.3. Rotate the Art Pen 2 while using a brush configured for barrel rotation.4. Barrel rotation works correctly.5. Close Photoshop.6. Create PSUserConfig.txt containing:   # Use WinTab   UseSystemStylus 07. Disable Windows Ink for Photoshop in Wacom Tablet Properties.8. Restart Photoshop and test the same brush.Actual result:Pressure and tilt continue to work in WinTab mode, but Art Pen 2 barr

# UXP defect report — cursor handling, and four missing DOM features Prepared 2026-08-20 from measurements taken inside a UXP hybrid plugin panel.Everything below was **measured in the panel itself**, not inferred: the testharness, its controls, and the raw verdicts are described at the end. --- ## Environment | | ||---|---|| Photoshop | 27.9 (Windows) || OS | Windows 11 Pro, 10.0.26200 || Plugin type | UXP **hybrid** (JS panel + native `.uxpaddon`) || Manifest | `manifestVersion: 6`, `host.data.apiVersion: 2`, `minVersion 24.2.0` || Loaded via | UXP Developer Tool (side-loaded) || Panels | two (`type: panel`), one main, one log | --- ## Summary Five defects, in rough order of impact. The first is the one that makes a classof ordinary UI impossible. 1. **`cursor` is not re-evaluated once a pointer button is held and moved** —   it reverts to the default arrow regardless of what any element specifies.2. **`cursor: url(...)` is discarded at parse time**, taking its fallback   keyword wit