Bug Reports

-PS cc2015.1 (dutch version) can't see new start screen, check box is on. -Color lookup few filters turn image black (bleach bypass and a few other) I work with new iMac and El Capitan, color lookup works normal with older mac and Yosemite.

The new Windows 10 update (I installed on the 20/11/2017) has broken the right click function on the wacom pen in Photoshop. When you right click on the pen to bring up the brushes the program uses the currently selected tool as well. All tools seem to have this bug and it can be seen in the history drop down effecting the canvas. This break the workflow completely as every time I change a brush an unwanted tool effect happens (unwanted brush stroke, unwanted move, unwanted marquee selection)I have updated to all the latest wacom drivers and the latest photoshop. I can reproduce this using a Wacom Cintiq 21UX and a Wacom Cintiq 22HD. I have also turned off all the known horrific windows 10 pen ink and flick issues.Is there any work around or fix for this?Damian

Hi,My Photoshop keeps constantly crashing whenever I try to create a Normal Map from Diffuse in the 3D mode. So far I have found out that the crashing occurs when working with any higher resolution images. I tried several different sizes of the same exact picture, and the crashing didn't occur with 1024x1024 px picture, but did happen when the size was 2048x2048 px.I have saved the crash report logs, if they can be used to fix this issue.

Updated to CC2019 from well running 2018.  First issue was with NEW dialoque .. disabled by setting to OLD dialog.  Bridge refused to reduce filesize with Image Processor (set to 1200x1200).. totally removed AND did Adobe-clean-util .. reinstalled both Bridge and Photoshop... Bridge works fine now, but photo-shop keeps showing "spinning wheel" (see screenshot : https://www.screencast.com/t/A4V1PALg0B6f " ...with 8% CPU load (on 8-core).  Screen does not fill with proper textbuttons...however i can open a file and work the system ???Adobe Photoshop Version: 20.0.0 20180920.r.24 2018/09/20: 1193433  x64Number of Launches: 6Operating System: Windows 10 64-bitVersion: 10 or greater 10.0.17134.1System architecture: Intel CPU Family:6, Model:14, Stepping:9 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, AVX, AVX2, HyperThreadingPhysical processor count: 4Logical processor count: 8Processor speed: 3 MHzBuilt-in memory: 16308 MBFree memory: 10443 MBMemory availab

Hi, I am running Adobe Photoshop cc 2018 in Windows 10. When I run Photoshop it says "Could not load default face expression presets because an unexpected end of file was encountered". Also another error like "Could not load default style because an unexpected end of file was encountered". But Photoshop open normally with no error. And I quit Photoshop and again run there is no such error message. It happens when I first run Photoshop. So is the problem still remaining with face expression, style, and brushes, or not. So, please reply.

Since updating to Photoshop CC 2015.5, I have encountered many challenges in having text appear properly for me. Characters in a text layer will disappear and reappear on a whim and there's nothing that I've been able to troubleshoot that has helped.Testing Notes: Bounding box is not an issue, as this happens as this will happen no only the LAST characters, but the FIRST characters of a text layer. Usually if the bounding box is not big enough, the whole word will disappear, not just one or two characters.The example below is created as Point Text, not a Paragraph Text, so there aren't any bounding boxes. This problem seems to affect capital letters especially, as changing it to lowercase works just fine (but see #4 below when it gets wacky again).   This problem doesn't appear to discriminate between fonts. The screenshots above is your plain ol' Helvetica. Fonts that never had an issue in a past version of PS now have this issue. Some don't.When I hit the down arrow on the curr

In PS 2019 with a right-click on a layer and choose "duplicate layer", "new document" you get a new document with a background layer not the original layer. Also if you duplicate a pattern-layer, you just get a new document with an empty white background layer. In former version you just got an identically layer in an new document. Can't imagine that should be a feature. I think it's a bug.

I just followed a video about this filter (photoshop CC 2018) + dynamic object. https://youtu.be/8Gfx8JPpJrA  and if the filter applied on a dynamic object, closes correctly, while in vcc2019, it does not close correctly !!!IfI use this filter in Photoshop CC 2018 (frenf version on macOS 10.14, when I close the filter interface, it automatically creates a 3D layer above the layer of the dynamic object used to launch the filter!Je viens de suivre une vidéo parlant de ce filtre (photoshop CC 2018) + objet dynamique. https://youtu.be/8Gfx8JPpJrA Si j'utilise ce filtre dans Photoshop CC 2018 (frenf version sur macOS 10.14 , lorsque je ferme l'interface du filtre, il se crée automatiquement un calque 3D au-dessus du calque de l'objet dynamique ayant servi pour lancer le filtre !I specify, I reset the pref. from PhotoshopSo there must be a problem in PhotoshopThere are also sometimes craxh when you want to close the filter by OK ????Je précise, j'ai réinitialisé les préf. de PhotoshopIl

When working on a layer with the mask disabled, using Undo will Enable the mask.Steps to reproduce: Open File Add Layer Mask Invert Layer Mask Disable Layer Mask "\" to turn on mask highlight (blue) Paint (3 strokes with white) Undo (Using Ctr Z)  The mask is Enabled when I "Undo", but it shouldn't. The mask should remained Disabled.This happens regardless of what tool you're currently using and also when selecting Undo in the Edit menu. It is occurring on both Windows and Mac computers. "Enable/Disable Layer Mask" does not have a keyboard shortcut assigned to it. This does not happen in previous versions of Photoshop (the mask remains disabled).

Adobe Photoshop Version: 20.0.1 20181029.r.41 2018/010/29: 1197484  x64I have PSD with frame animation and the at least one layers group, I can't use the "Paste frames" command with "Paste over selection" option. When I try to run such a command, I get the error "Could not complete the command because of a program error".After removing the layer group (with "Ungroup layers" command, thus the group's content is not deleted), the "Paste over selection" starts to work fine.Steps to reproduce: create new PSD  create frame animation create the new frame (there should be 2 frames now) create new group and create new layer inside this group in the Timeline panel under the "hamburger" button select "Copy frame" Again in the Timeline panel under the "hamburger" button select "Paste frame..." Select "Paste Over Selection" option and press Ok. The error will be showed.

After the Photoshop CC 2018 update, I am getting "Could not apply the workspace because of a program error" after clicking "select and mask" button. Before update, it worked perfectly. Have somebody same problem?

With every new version Photoshop get a new bug for liquify and smart objects.This time when you editing and save/update smart object witch have mask it mishandles the smart liquify effect. So you have to disable the mask before editing it.Same thing happens if you enter to edit liquify. You have to disable the mask, otherwise its distorted.

I often run dust and scratches as a smart filter and fill the mask with black and just bring it back where needed.  Since updating to 2019, if I save a file, then re-open it, or batch process flat files, the filter is applied to the whole image, rather than just what it is masked to.  I have to turn the mask off, then back on for it to apply.  I had to re-open 160 images and render the smart object layer to fix them.

Having trouble with the Spot Healing brush. When I click on the band-aid icon, there are no options that pop up to the side like I see in tutorials. Am in a a wrong mode? I am new to this. I can do the basics,and blemish remover is one, however I knew it on a version from a few years ago and can't see to find it now. I got the program last night. Thank you,Ash

Photoshop 2019 is freezing up when I put my computer in sleep mode. I have to kill that process and restart Ps. Rebooting seems to help for a day or so then the problem is back. I did not have this problem with 2018, nor do I have this problem with any of my other apps.I have a 4th-gen 4.00 MHz i7, 16 GB of RAM, a 512 GB SSD (only a couple of months old), and a decent graphics card with 2 GB of RAM (Nvidia GTX 750 Ti).

I've just updated to the latest version of Photoshop cc 2019 and since then when I have the brush tool selected the resizing/opacity HUD won't work as expected.In Photoshop CC 2018 the brush preview (i.e. the usually red overlay) look faded to the edges depending on the opacity level. like this:In Photoshop CC 2019 this works only if I use the HUD to change hardness instead of opacity, otherwise the brush won't show any fading, like this:Is there a way to show the fading edges in the preview even when changing opacity?

can someone give me a fool explanation on whats the difference between those two please.

Photoshop has become suddenly unusable. Almost every tool gives me an "Out of memory (RAM)" error and when I try to open the Performace pane I get the error in the title. I cannot get inside the settings, as this error keeps on popping up. I tried everything (reinstalling PS, deleting everything (including preferences), updating PS, updating Windows 10, switching to the latest Insider Preview). Nothing fixes this error.

Before I updated to CC2019 I created a workflow where I create versions of different templates in PS using artboards. Then I'd exports the artboards as separate .psd files for people in a different department to use. It worked wonderfully until I updated to the latest version of PS.Now I get the error in the attached image below when I try to do this.I've also attached screen grabs to get an idea of exactly what I'm trying to do.I've tried flattening library elements and smart objects. I've tried all the different options in the export options panel. Nothing changes.(was sent here by Adobe Customer Care on Twitter)

If you add a layer mask to a layer and start painting in it to hide/reveal pixels, if you undo the first brush stroke, the Art Layer becomes selected (unselecting the layer mask), therefore, when you start painting again, you're painting on the Art Layer, not the Layer's Mask. Happening in Photoshop 20.0.0 on Mac OS 10.13.6

This is a bug possibly connected to an unfixed 6-years old bug regarding the value for 50% gray in 16-bit mode in some Photoshop dialog boxes, see: https://feedback.photoshop.com/photoshop_family/topics/photoshop_uses_the_wrong_50_gray_as_the_neutr...The problem:Using Apply Image (Blending: Add, Opacity: 100%, Scale: 1, Offset: -128) on two 50% gray (RGB values of: 16384) layers in 16-bit mode produces non-50% gray layer.Steps to reproduce (with correct 50% gray value of 16384): Create an empty document in 16-bit mode (of any size) Create an empty layer, named "A". Delete the background layer. Fill the layer "A" with 50% gray (Edit>Fill: Contents 50% Gray) Use the Info panel, read RGB values in 16-bit mode of the Info panel: 16384, in 8-bit mode: 128 Duplicate the layer "A", name it "B". Make sure the layer "B" is an active layer. Image>Apply Image: Layer: A, Blending: Add, Scale: 1, Offset: -128 Read the resulting value: 16320 (in 16-bit mode of the Info panel),

This is an ongoing issue it seems so moderators may want to move this post to an existing thread if applicable. I continue to have graphics issues in V20.0.2. Since pictures are worth a thousand words, let me sum this up with photos:I am masking the edge of a cloud layer against the background. The cursor is near the bottom of the screen and is in the process of masking the edge of the cloud. I'm using a soft brush (it seems this always happens while using the brush tool but no specific brush), and this is what is happening:This (below) is what it should look like:Here is my system and PS info:If you have further questions, please let me know. I can get rid of the problem (I think) by switching off the Graphics Acceleration, BUT that's not an option for me. I use a lot of things that require that option. My drivers are completely up to date as is PS. My workaround right now is to turn off the layer then turn it back on, but this is both time consuming and disruptive. I really hope

I edit photos with a lot of adjustment layers (15 or more). Occasionally, one of the layers is a photo filter layer, to warm part of the image. After making all these adjustments, the last thing I do is combine everything (background image and all it's layers) into a smart object where I do my final sharpening. I've noticed that in Photoshop CC 2019, when I package everything into a smart object, a color shift appears in the new smart object anywhere that I used an adjustment photo filter. Those parts shift from the yellow it was to pink/fuscia in tone. So, I open the smart object, and now the same problem is there. So, I re-adjust the adjustment photo filter. First, I highlight that layer, open the properties menu, and click the color so that the Color Picker pops up. As soon as I touch the scroll for the color everything pops back to the way it should be. It's as if there was no problem at all. So I save the psb, which updates the smart object. Most of the time this has fixed the pro

Adding a custom scale and set a shortcut for it. After saving it restored to nothing

I've seen this post here: https://feedback.photoshop.com/photoshop_family/topics/larger_feather_radius which says how the selection feathering radius was turned up from 250 to 1000. I've confirmed that this is the case when using the GUI.However, when trying to do the same thing via scripting, either using the DOM or using the output of ScriptListener, values above 250 give the same visual result as putting 250 (and thus, different from when entering those values in the GUI).Specifically: app.activeDocument.selection.feather(new UnitValue(amt,"px")); and var desc1 = new ActionDescriptor();desc1.putUnitDouble( charIDToTypeID( "Rds " ), charIDToTypeID( "#Pxl" ), amt );desc1.putBoolean( stringIDToTypeID( "selectionModifyEffectAtCanvasBounds" ), true );executeAction( charIDToTypeID( "Fthr" ), desc1, DialogModes.NO );