Photoshop (Beta)

Buenas tardes, cuando intento abrir Photoshop beta versión 27,11 empieza la pantalla de inicio a abrirse pero se cierra y no se abre; en cambio el Photoshop versión 27.10 no beta se abre perfectamente.A que puede ser debido?Un saludo : Sergio

Con l'ultimo aggiornamento la rotondità del pennello va sempre a 0%.Ho provato rimettendola a 100% dal pannello “Impostazioni pennello”, ho provato a reinstallare photoshop beta, a cancellare la cartella dei settaggi, a pulire il registro di sistema, a disinstallare la tavoletta grafica. Quando clicco sull’icona del pennello per cambiarlo o cambiare la grandezza, la rotondità torna subito a 0%.Con una versione differente di photoshop il problema non si presenta.**This post has been moved by the administrator.

In the last few days the remove tool is painfully slow. 

When opening the Brush tool at the Options bar, roundness appears at 0% with any brush. It works when fixed, but as soon I open again, it returns to 0%. It's not the case when opened with the brush panel at the left, there it works fine.

Issue: Clone Stamp brush becomes a flat horizontal line after the latest Photoshop Beta update, and the Clone Stamp tool is also no longer functioning correctly.Photoshop version: [paste from Help → System Info]OS: macOS [version]Steps to reproduce:Open an image. Select the Clone Stamp tool. Choose a normal Soft Round brush. The brush preview/cursor appears as a thin horizontal line instead of a round brush. Option-click to sample an area. Paint with the Clone Stamp tool.Expected result:A normal round Clone Stamp brush that reproduces the sampled pixels correctly.Actual result:The brush appears as a horizontal line, and the Clone Stamp itself is not working correctly. It produces strange, distorted or otherwise incorrect cloning results instead of reproducing the sampled area normally. The issue is not just the cursor/brush preview. The actual cloning behavior is broken.Additional notes:This started immediately after updating Photoshop Beta today. Resetting Clone Source, checking curso

selecciono imagenes con el bridge , edito en camara raw y despues intento abrir en photoshop pero se bloquea el progrma. antes lo hacia asi cn muchas imagenes . ahora solo se puede hacer uno a uno y solo si desde bridge eligo abrir directamente en photoshop y no camara rawnunca antes paso esto pero hace unos dias si

This still appears to not be fixed. If I open files with Graphic Processor off they load correctly If I turn it back on they open super saturated in the mail view. Switching Image modes doesn't help me.

I honestly feel that Photoshop is no longer Photoshop. It is becoming a fundamentally different product, increasingly designed around AI-assisted creation at the expense of the traditional manual tools and workflows that made Photoshop what it is.I want to make something very clear: I am not against AI, innovation, or change. Quite the opposite. I have been working with Photoshop practically since its earliest years, and I have often preferred using Beta versions precisely because I enjoy experimenting with new tools and new possibilities. I have welcomed AI features when they complement manual work and make it faster or expand what we can do — features such as 3D object rotation are a perfect example.The problem is that the balance now seems to have been lost.Basic, historical Photoshop operations are becoming unnecessarily difficult, unpredictable, or actively obstructed by new behaviours.For example, guides, rulers and snapping behaviour make even something as elementary as drawing

Mehr gibt es nicht zu erläutern, die Neural Filters funktionieren nicht mwehr seit dem Update auf 27.11.0

Hi, since a few days when opening Photoshop, the keys don't work properly. I can't use CTRL+N or +O for a new file or to open a File. When I open an image by mouse, I can click on the tools and rename the layers for example. But I can't use the keys to select the tools or to increase/decrease my brush. The Function keys still work so I can show/hide my layers/colors etc. Anyone an idea? Already went to Preferences/Tools and turned on/off Spring-loaded Tool Shortcuts, that didn't do the trick. Also tried booting in Save mode and clearing all preferences to defaults..  Nothing works. If I open Illustrator, the keys work.   Anyone an idea? This drives me crazy 😞

Camera Raw 18.4+ – Subject Masking Regression: identisches WinML-Modell funktioniert in 18.3.2, wird ab 18.4 nicht mehr korrekt geladenIch konnte das Problem inzwischen anhand der Camera-Raw-Logs und des ModelZoo genauer eingrenzen.SystemWindows 11 Photoshop 27.10.0 Camera Raw 18.3.2 / 18.6 Intel Arc Graphics, Meteor Lake, 128 EU Intel Grafiktreiber: 32.0.101.8860 identische Hardware und identische Photoshop-Version für den VersionsvergleichDas Problem tritt auf zwei unterschiedlichen Windows-11-Systemen auf.FehlerbildSeit Camera Raw 18.4 funktioniert in Maskieren → Motiv auswählen die automatische Motiverkennung nicht mehr.Camera Raw zeigt:„Das KI-Auswahlmodell kann nicht heruntergeladen werden.“Andere KI-Maskierungsfunktionen, insbesondere Himmel, funktionieren weiterhin.Außerdem funktioniert in Photoshop selbst:Auswahl → Motivproblemlos auf derselben Hardware.Ein Downgrade auf Camera Raw 18.3.2 behebt das Problem sofort.Adobe führt für Camera Raw 18.4 selbst eine Änderung an genau d

Bug report template:Issue: Photoshop version: 27.10 & 27.11 Beta OS: Windows 11Steps to reproduce:Use a black/white brush or gradient on a mask Expected result: A smooth gradient or brush markActual result: Grey banding occurring, looking like a low colour bit-depth is being used (when the image mode is 16-bit). I tested the same image on multiple versions. I get smooth gradients and brush marks on Release version 27.5 and Beta 27.9, but I see banding when I update to 27.10 and 27.11.I have checked all my gradient and brush settings and made sure they’re identical between all versions of the apps. I have tried playing with brush spacing, smooth and gradient dithering and classic vs smooth method, but that doesn’t make much of a difference.I have also tried toggling Use OpenCL on/off in the graphics preferences but it doesn’t help.I have Use Graphics Processor ticked on, Use OpenCL off, Anti-Alias Guides and Paths on, 30-bit display off and GPU compositing on. My GPU is an RTX 4080.

PS Beta 27.11The brush tip cursor flickers every second all the time.I attached a video of the issue

Adobe Photoshop Version: 27.11.0 20260830.m.3655 ceb0621  arm64 (beta, PublicBeta)If you try to open Black and White window (cmd+opt+shit+b) it fails to build:Drover error in ok_cancel_dialog:Drover error in black_and_white_view:<unknown>:1:0: error: cell named 'show_auto_button'already exists.File: layout descriptionLine 00010: sub_layout(name: "content");char 00000: ^^^ 

There is an awful AI Assisted button on the top bar that doesnt seem to be removeable. This must be removeable. Advise how to remove this awful thing

The "Export As" window is glitching, which sometimes makes it go behind Photoshop. Additionally, its size does not stay adjusted as usual and it is always smaller. I have to resize it every time I open the program and use the "Export As" function.Another problem is that the file preview is pixelated, which does not happen in the regular version. This started in this last beta update; it didn't have this problem before. Furthermore, the image only looks good if I set the zoom to 100%. However, I cannot see the full image with good quality like before because it goes past the borders. I have to keep moving it to see the corners that do not show up. Image from Photoshop (Beta) version 27.9Previous version 27.8 is perfectly normal and trouble-free.Image from Photoshop version 27.8 

"When using the crop tool with AI generative fill, the result isn't perfect."

When using Cmd shortcut to auto-select, when group is selected it selects layers, when layers is selected it selects groups

 Basically action from the selection menu is reversed somehow. When I use V for move tool and select Layer from the drop down menu then I can only select the whole Group, and when I select Group from the drop down menu I now can only select a single Layer.

User posted bug in wrong group:  

I try to convert an image into black & white from the menu Image>Adjustments>Black & White and get this. Started happing only after the last update today.Drover error in ok_cancel_dialog: Drover error in black_and_white_view: <unknown>:1:0: error: cell named 'show_auto_button'already exists.  File: layout description Line 00010: sub_layout(name: "content"); char 00000: ^^^

​When using GPU with HDR enabled monitor, all image content is dark.This is new with the Aug 2 version of V27.10 (today). Nothing changed but installing the update.Windows 11 - 25H2 26200.8875Adobe Photoshop Version: 27.10.0 20260802.m.3625 8f8ccb9  x64 (beta, PublicBeta)GPUName: NVIDIA GeForce RTX 3070 TiMonitor: XG27UCG  (ASUS ROG XG27UCG)(See included .txt for more)This is how a page normally looks (and still looks in PS 27.8) This is how it looks in today’s 27.10 - I had to cheat to get this, because the image looks fine in an SDR screenshot, but this level layer reproduces what I see:This is a greyscale image, but I get the same issue in RGB photos.Note that the UI rendering is fine, and if I copy the image to another app, or move PS to another monitor, it looks fine.  I can fix this by either Edit → Preferences → Performance → Use Graphics Processor - Off  or by Windows Settings → System → Display → HDR → HDR - OffFor now I am working around this by disabling HDR because obviousl

EN LA VERSION BETA DE PHOTOSHOP LA FUNCION DE SUSTITUCION DE CIELO NO PERMITE UNA PREVISUAIZACION DE LA COLOCACION DEL CIELO, NO SE PUEDEN MOVER LOS CONTROLES YA QUE NO SE VE ABSOLIUTAMENTE NADA O SOLO SE VE UNA SOMBRA

Parametric filters do not show up on any version of the Photoshop beta that are currently out. They are missing from the filters tab, and are greyed out when looked up in the search tab. I'm on a Microsoft Surface Pro, with a Snapdragon processor. I’ve reinstalled the beta, reset my preferences, confirmed I’m in an RGB 8bit channel, and tried a few other potential solutions (that haven’t worked...)Any fixes?