Bug Reports

Hello, first of all the latest update is pretty awesome. There are some much wanted improvements. However I just noticed that with the reworked export as function the image settings are always reset to PNG. Previously it remembered what it was set to.And, perhaps worse, previously the default destination was always the folder the PSD was inside. Which is pretty much always where I want the files to go. Now it remembers the last destination, which is almost never where the file is supposed to go. This costs me a lot of time... an option would be fine, because I'm sure some users love the new way of handling things.

Adobe Photoshop CC 14.2.1 OSX1.- Run an action that makes a custom selection on a channel made by calculations and adds the selection as a mask to a layer. — The mask gets made as expected.2.- Use color range to select skin tones. Deselect.3.- Rerun the action that makes a custom selection on a channel made by calculations and adds the selection as a mask to a layer. — "The command make is not currently available".I have attached an image with the action steps. Record this action (on color range be on "Sampled colors" and click anywhere on the image), run on a background layer. Revert, delete the layer or open a new image an make a selection on skin tones using Color Range. Try running the action again. An error occurs, as if the Color Range dialog doesn't get updated to select the custom selection made on the action. Only way to make the action work again is manually going to Color Range again and selecting other option rather than skin tones (highlights, midtones, etc) — this is manu

In Photoshop, the "Select and Mask" feature is basically unusable. After making one or two selections, it tends to either hang or crash (although sometimes it works for several minutes/selections so this problem is not perfectly reproducible). I have made a video of the "hanging" issue at http://me.jameswilliams.s3.amazonaws.com/photoshop_select_and_mask_freeze.m4vI was also able to save a crash dump from an instance that it crashed. I can make this available upon request but it is quite large so I do not want to upload it to S3 until asked. The exception for the crash dump was Unhandled exception at 0x00007FFE649587BB (ntdll.dll) in Photoshop.exe: 0xC0000374: A heap has been corrupted (parameters: 0x00007FFE649BC6E0). occurred Troubleshooting Steps:I have tried the following. In all cases, the problem continued:  Fully update Photoshop and Windows 10 Uninstall and reinstall Photoshop Reboot  Upgrade to Intel's drivers for the Intel HD 640 GPU (these drivers are se

Deselected single path points are supposed to be displayed as crosses. In my case the cross is drawn in the top-left of a document, the actual points stay invisible until I select them. If I disable GPU, path points are displayed properly, but I use GPU features a lot.CC2018 and previous versions don't have this issue. Using different GPU options, compositing engine doesn't seem to give any result.Some PS and system Info:Adobe Photoshop Version: 20.0.1 20181029.r.41 2018/010/29: 1197484  x64Operating System: Windows 10 64-bitglgpu[0].GLVersion="4.1"glgpu[0].IsIntegratedGLGPU=0glgpu[0].GLMemoryMB=6144glgpu[0].GLName="NVIDIA GeForce GTX 1060 6GB"glgpu[0].GLVendor="NVIDIA Corporation"glgpu[0].GLVendorID=4318glgpu[0].GLDriverVersion="25.21.14.1722"glgpu[0].GLRectTextureSize=32768glgpu[0].GLRenderer="GeForce GTX 1060 6GB/PCIe/SSE2"glgpu[0].GLRendererID=7171full system info: https://pastebin.com/Y7imjL70

The drop shadow changes distance from the object depending on the zoom level. Also, sometimes I get green or red boxes over the image that look like display problems, but then save out when I save a flattened version.

I seem to be having an issue with the Vanishing Point Filter in Photoshop CC 2019 on an iMac/Mojave system. When I resize an image to fit within the vanishing point mesh, everything is fine until I drag the image inside the mesh area. Then it's as though the image itself stays resized, but the canvas its on is still the original size. This is apparent because the grab handles for sizing the image are space way too far apart and extend beyond the actual image, making resizing within the vanishing point mesh almost impossible. Please see the following to reproduce the fault. Note, I did not have this issue in PS CC 2018, although at that time I was on High Sierra so I'm not sure which you need to look at to troubleshoot this one. It is also possible I'm doing something wrong or am missing a step. I'm following the directions in a PS tutorial for CC 2019 by Julieanne Kost on Lynda.com and it's virtually identical to the same course for CC 2018.Steps to Test Vanishing Point Filter 1. Open

I've always found it helpful to be able to drag new guides from the rulers while the Transform function is active on a layer/object. This was particularly helpful for object such as logos that have built-in white space. If I try to create guides before transforming, the guides only snap to and center based on the drawn pixels. If I do Edit > Transform, then the object's full artboard size is shown and allows for better centering and edges for snapping ruler guides to. This was always available until the recent Photoshop CC 2019 release.

I have faced a major issue after changing from PC to IOS. On a pc this problem was easy to solve, just change the keyboard language from Finnish to English alt + shift. Cant do that on IOSWith IOS nordic keyboard it is not possible to use the stamp tool rotation shortcut because we don't have bracket keys separately on our keyboard < / >. Photoshop won't allow to change this shortcut and it is affecting everyone's workflow in the nordic countries. Would it be possible to allow users from other countries who are not using the english keyboard on a mac to be able to change this shortcut. This is a major issue and is costing me time and money when I cant have a fast workflow anymore. It would be amazing if we could use , and . for changin the rotation.

Wow, I am so disappointed. I just upgraded from Photoshop CS6 Extended to Photoshop CC 2019 20.0.6 yesterday. This morning I worked with it for a few hours to update some of my graphics. All of these graphics were made in CS6. To my surprise and disappointment, it must have crashed close to twenty times during those two hours or so.And what is surprising is that I was not doing anything intensive. I was only using Photoshop's built-in functions to change text size, to change text color, to move layers around with the Move Tool, to use the Fill tool with Content Aware, and to resize documents. That is basically it. To my recollection, all of the crashes occurred while doing the first three. That is, change text size, change text color and move layers around with the Move Tool. Just simple stuff.Please note that I was NOT using any third-party plugins to add special effects to my graphics. As I said, I was only using Photoshop's built-in functions.The crashes were so frequent, that I bec

Whenever I create an adjustment layer it makes the Layers panel disappear (as well as the properties panel witch should open automatically). They only come back if I restart or, weirdly, if I resize the Photoshop window. When I try to switch between multiple open images, they do not display (just the ghost of the original image). This can again be fixed by resizing the window. These aren't fatal flaws but they SERIOUSLY slow down my workflow, so I'd like some answers if possible. Everything is updated to the newest version.

This wasn't happening in the previous version of Photoshop. I have Photoshop always open (for days at a time) while working on multiple projects. After a longer periods of time when I don't switch back to Photoshop and it just sits opened in the back, it stops responding when I try to switch back to it. I noticed it's missing an icon in the taskbar and I can't alt+tab to it. When I minimize all other windows and find Photoshop on the bottom it is not posible to click on anything (no tool, no menu item, not even close it). I have to end the Photoshop process in the Task Manager and reopen it. This behavior only started after upgrading to the newest version of PS v20.0.0. Only good thing is I was always able to recover what I was working on thanks to automated backup and recovery in PS.

Is this ever going to get fixed? After hours of googling all I find is more people having the same problem.This is in no way actually related to not enough memory, I have 40% of my 16 GB RAM free, 8 GB scratch space on one disk, 200 GB more on another, and it happens even when I'm trying to content-aware fill a single pixel in <1 MB single layer file...Persists after reinstalls or resetting preferences, same in 19.0, 20.0.1 and 20.0.2Other people have reproduced the bug, given the steps.Here's a sample file: https://ufile.io/a4fml- zoom in to 300% (optional)- select spot healing brush (default = size 19 px, mode normal, content-aware)- click with it at the top here: https://imgur.com/a/oyfKPdhAlternatively:- click anywhere else, it does the memory message anywhere unless it's an empty area.- select any non-transparent area, even if it's just 1 pixel, with the rectangular marquee, click it with the right mouse button and select fill (content-aware)And yes, I know the intended effect

The saving location issue is fixed in the latest updated.However, the minor issues I also reported are still present. No keyboard focus on the window to allow pressing Enter to save. Zoom is blurry and pixelated. There is still a browser right-click context menu over the dialog, and you can still drop in arbitrary files into the window and have them open.Note: This conversation was created from a reply on: Photoshop CC 2019: "Export as" is exporting to the last folder you exported to.

I'm not sure why this is becoming a problem now, but on Photoshop version 20.0.3 and 20.0.2, gradient overlays that use transparency, whether by a gradient fill layer or as a layer style, behave inconsistently when Legacy Compositing is off.Certain actions, like editing text, will cause the opacity of gradients in the document to change. If the gradient is a layer style on a layer, trying to edit that blending mode will cause the gradient opacity to change again.This is bug is a real hassle to work with when my gradients are seemingly changing for no reason when doing other things in a document.Here is an example file that demonstrates this issue. Try editing the type. Then try double-clicking on the Gradient Overlay effect.

In CC2019 v 20.0.3 there appears to be an issue with layer styles stroke.To replicate:Make an empty layer Add a solid brush stroke say 200 px wide Go to layer styles and add a stroke with size of 50px position inside and normal blend mode.Reduce the opacity. As the opscity is reduced, the stroke cuts into the pixels on the pixel layer - revealling transparency - all the way down to 1%.However when the stroke is reduced to 0% opacity the pixels reappear.CC2018 works correctlyI am using Windows 10 v 1809 and NVidia graphics GTX1080 driver 417.71Use legacy compositing makes no difference to this issueDave

There is an issue which crashes Photoshop if a material value is moved.To replicate :1. Make a text layer and a 3D extrusion from that layer2. In the 3D panel click the Filter By material button.3. Choose a material e.g. Front Inflation material4. In the properties panel adjust the Shine value sliderResult crashWorkaround :Miss step 2 above i.e do not use Filter by material in the 3D panel just step straight to Step 3 and select the material.  This time - no crashMy system Photoshop 20.0.4 on Windows 10 (r1809) and Nvidia GTX1080 driver 417.71Dave

When I use "Color" blending, I got incorrect color under the some circumstances.Environment: OS: Win10x64-1809 (OS build 17763.437) or Win7x64Photoshop: 20.0.4 20190227.r.76 2019/02/27: 1205725 x64Steps to reproduce:  Create PSD with 1080*1080 canvas size. Create layers group Create red rectangle inside the group (use Rectange tool) Set Stroke to None in the rectangle settings Set Opacity=95% for the rectangle Use Free transform to stretch the Rectangle on the whole canvas Set Color blending for layers group Remove white bacground layer Expected result - semitransparent red color over the whole canvas. Something like thisActual result - semitransparent black layerAlso, when I exporting the group with "Quick export as PNG", I expecting semitransparent red color, but get the whole black color without transparency.The problem gone if I turn on "Use old compoistion core" in settings. The problem can't be reproduced on non-square canvas sizes and unstable reproduces on different

Photoshop CC 2019 bug: Pressing the up or down arrows in a numerical text entry field in the "Export As" dialog, whilst holding down the SHIFT key, adjusts the numbers in 5s, rather than 10s.

It seems that, with PS CC 2019, some problems were introduced in the File Info dialog box (at least on Windows systems).The main problem is that the up/down cursor keys don't seem to work anymore in text fields in File Info. For instance, in the Keywords section of the Basic tab of File Info, if you have many keywords (enough of them so that they span more lines than the field will fit by default), you can scroll up and down through them using the GUI's clickable arrows, but pressing the up/down cursor keys (in the physical keyboard) to move through the lines won't do anything.The same applies to other multi-line fields in File info when using PS CC 2019.On top of that, there is at least another problem that could be related - in the Photoshop tab (File Info>Photoshop), the history log for the file is shown (provided it was activated in the preferences). In this case, if the list is long, the clickable arrows don't seem to work at all. This problem is already reported in a separate

Everything will be okay in 8 bit mode.However, when using 16 bit mode, importing psd into the AI and ID, if there is a group of layers inside a transparent background PSD (no solid colour there), group with layer mask will not work properly, especially the opacity function of those layers inside the group. Without layer mask or not, the opacity of the layers inside the group is totally different. It seems, the calculation of the opacity getting error when there is layer mask even it is white with nothing!I got more detail now: if a group of layers only contains some adjustment layers like solid colour, etc, the problem happens.

When exporting an Image Sequence under Export -> Render Video, choosing Matte in the JPEG settings does not work. The background colour of the JPEGs is always black, no matter which option is chosen.

Photoshop 20.0.0 , Français, erreur dans le dialogue d'exportation.Largeur = LargeurRelief à corriger par HauteurMerci de faire cette correction.Photoshop 20.0.0, English, error in the export dialog.Width = LargeurRelief to be translate by HauteurThank you for making this correction.

I am having an issue with animating using the timeline. Everything works fine except when I try and move a mask. If I want a mask to move to slowly reveal the layer, say from right to left, if I try and drag the mask over and release it lined up with the edge of the document Photoshop crashes/disappears. If I move it from the right edge to the center, it is fine, but if I move it to one of the edges it crashes. It does it on all the documents I have tried it on, not just one specific document. It has happened only since the latest update, which I did at the same time I updated my Mac to the latest OS. I have be using the timeline to animate things for years, never had this issue, I have no idea how to fix it. I am working on a 17" iMac

As You can see I have a lot of infinite lights. I don't know when they was created. When I try to render 3d layer, delete or disable visibility of lights program crashes without displaying errors. Addictionaly during opening project pops up an error about limit of lights. What can I do? Anyone can helps me solve this problem? s

In a Document with multiple Artboards, when i copy an Layer and/or Groups via the "New Layer" Button in the Layers Panel, The copied Layers move to the first Artboard in the Document and on a different position. Costs me lot of work to move the Layers where they should belong.....