I would like a panel with a textbox that says "What would you like to do?" I would describe a task and the software would perform it, using some basic vision and the existing API built into Photoshop.   For example: "Select every shape layer and the layer directly below it, and for each, put them in a group." "Add 'preview_' to the start of every layer name" "Select the outline of every layer and add a layer mask to each" "Copy the layer style from first text layer and apply it to every text layer" "Repeat the last 3 operations performed on Layer1 to every layer" "Distribute the selected layers in an evenly spaced circle around the center"   Strictly speaking, I could open up a project right now, and every 20 seconds, think of another example. To me, this is a significantly more important feature than the ability to use AI to paint or draw for me. There's loads of things that can be done via Action (and I use them a lot), but Actions lack the ability to adjust on-the-fly, and take time to set up (and require me to do half the task in order to record one). Every menu, tool, and option in Photoshop is documented and tool-tipped; actions already have a scripting api.   ... View more

When I turn on paint symmetry, the plane is based on the center of the total geometry of my project.   Suppose that I have several materials in my project. It is frequently the case that I want to symmetrize around a specific subset of geometry containing a single material. To do this in today's version od Sunstancec Painter, I need to turn on symmetry, set the axis, and then drag the offset sliders to (very) roughly get the plane to the center of the intended piece of subset geometry.   I would like for a checkbox option in the symmetry settings to choose to center the plane on the active material's geometry, so that I can easily get in the middle without dragging sliders and eyeballing it. ... View more

In the beginning, there was the Photoshop~   Over time, the list of things a person might reasonably wish to do to pixels grew rather unweildy. Remember Photoshop CS3 Extended? I do. Remember the "3D hat" option? I remember a time when the hue and cry was for Adobe to stop adding features to the "bloated" Photoshop (and I remember waiting 5 minutes for CS2 to load).   Cutting a lengthy reminisce short, we got Lightroom. It's bundled with Photoshop and remains a popular tool for photography-processing-minded folks. It's basically a set of already-existing tools--mostly from Bridge and Photoshop--rearranged into custom-designed interface and workflow for a major area of digital media.   Here we are again; Adobe has a certain reputation among independent digital paint artists for being "evile" for being rental software loaded up with genAI and other such subscription features side-loaded onto an otherwise "good" digital painting tool. Adobe's brush format is the defacto pixel-art brush standard, borrowed in non-Adobe raster painting tools; Illustrator has most of the vector paint features popular in non-Adobe vector painting tools.   You have the tools, but they are spread across several programs and generally perceived to be "loaded up" with lots of features that aren't essential to the digital painting work task. Photoshop, Illustrator etc need to continue to evolve, explore, innovate and grow if the Adobe suite are to remain cutting edge industry-definers. But you also need people, living and working in the Adobe ecosystem with tools focused on their needs. Nobody should have to produce vector-drawn brush art in Illustrator or non-Adobe tools, and then "bring it into Photoshop for lighting/shading" for example, and yet this is seen as the workflow that artists are fated to follow.   I propose Photoshop Paint: a lightweight paint tool that joins the Photoshop family. This tool roams the space of painting-specific tools, creating vector and raster layers with vector and raster brushes, gradients, fills, shapes, and masks. Raster layers support lasso and "smart" selection, vector layers support re-coloring and there's a small set of basics (eyedropper, canvas move/rotate, Free Transform, layer fill/opacity).   Roll it into the Photoshop plan ($10/month) or... Do you want to be heros? You're losing a certain percentage to CSP, Affinity etc anyways, why not convert a few:  Sell it standalone for MacOS and Windows for $X ($45? $55?) one-time purchase, single-version only. If it's cheap enough (and remember, you're just selling UX development for features already buried under the mountains of the full suite), you don't need to fiddle with discounted upgrade deals and next-versio-selling whiz-bang features. Yes, sure, feel free to roll painting-like AI features into Photoshop... For example..."sketch to ink" conversion, using presets or an artist's local-built collection as a generative guide. And then, when you need to make a few more standalone sales, slide a toggle into the "next" version of Photoshop Paint to enable that tool. I know app and web versions require more continuous development so, sure, if you make a mobile version, make it exclusive to the Photoshop Family subscription plan.   Above all: This isn't a revisit of Photoshop Essentials. Like Lightroom, this is a curated selection of the existing tools most needed (and most borrowed by single-sale competitors) for digital painting, reworked into a UX/UI better suited for that industry. It gives Adobe room to continue to explore every direction in its pillar apps, while using an arrangement of the "best bits" for one major use-case to drive constumer engagement and to serve as an inspiration point for future main-line tech. Pivot on your strengths, pls! ... View more

After using the Paint Along a Path feature to draw a shape, I sometimes find that I need to slide the shape that I've drawn "up or down a little" and this is an excercise in frustration. While it is possible to select all of the control points in a shape, it is not possible to move them all as one. Simply being able to shift points along global XYZ with the arrow keys would be a huge improvement.   As a follow-up, adding the ability to "maintain snap to face" would be a bonus, but more difficult implementation. Imagine a circle of path points around the base of a cone. Selecting any number of points and moving them "up" would hopefully cause them all to simply translate upwards; projection depth would determine whether they still leave paint on the surface. But with "maintain snap" enabled, the initial "closeness" of the points to a surface would be checked, to determine if each point is snapped onto a face, and if so, the direction to that face. As the Up key is pressed, each point would raycast towards the initial detected direction, and if the face is detected, snap to it. On a cone, this would result in a ring of points scaling inwards as they are moved upwards. ... View more

If I wish to add painted embellishments that follow modeled geometry, it's suprisingly difficult to be precise, even with the newish Path tool. My goal is often to snap a painted line along an edge, or to snap a brush stroke to an edge or vertex, and I cannot find a way to do this precisely; I keep needing to zoom wayyy in to wiggle path control points around to get the paint to fold around corners and follor edges reliably. ... View more

While it is neat and useful to place paths in 2D, it would also be valuable to use the tool on the 2D view. Since our paintbrush materials are already in Painter, it's vastly more difficult to add 2D shape painting via a round-trip into Photoshop or Illustrator. ... View more

  Here, we have an asset page. Interesting asset. How do I use this asset? How do I download it? What is needed to make use of this asset? An utter impossibility.   Look at the page. Do I need a subscription? Credits? Ist there a cost? Is this available in some way? This is just a page on the internet showing me a ball. There is nothing suggesting how to engage.  Yes, I'm signed in. Yes, I'm on an Enterprise plan. No, I don't have and "credits" (I see the zero up there in grey).    So what? What happens now? Do I need credits? How many would I need for this asset? How would I get them? Do I need a subscription? What kind? Where do I get that? ... View more

I've seen other ideas for content aware paste, similar to the harmonization Neural filter, but I'd like to see the AI-powered version. Basically, when I paste content into a document, I want to be able to "make it fit."   I'm including an example of the kind of thing that would be a real break-through:   Here we've got an office backdrop, and I've dropped a picture of a pedestal on a base into a new layer. The new object does not match the perspective and lighting of the background image. Traditionally, I'm in for a long night after a bit of perspective warping with some clone stamping and custom painting to fake bits of perspective.   What about an AI powered set of tools? Can I "paste into" a selected region and have the image scaled and redrawn with an estimation of the correct perspective and lighting? Can I merge layers, adapting one to look at home in the other? --at present, I know I cannot. I asked Generative Fill to put in a Greek Vase on a stone pedestal and I got a lampshade on a metal pole. But generative is irrelevant. I need this image, manipulated to match perspective and lighting.   I imagine someday, a generated 3D object that I can position and then "Apply" as a guide. But I'd be happy in the short term to just see some kind of low-rank adaptation features for perspective matching etc. ... View more

With apologies if this already exists and I simply haven't found it, but... "File > Export Textures" has a default export location of "Documents/Adobe/Adobe Substance 3D Painter/export" on every project. Intuitively, I would never wish for every texture from every project to dump into this directory, and fairly logically, I would love to export to the project's working directory, into, perhaps, a sub-folder (maybe named "export").   I occasionally migrate a project from one computer to another and would not benefit from the project directory being locked down to the folder structure of the "other" computer, and so it would be useful for the default export directory to be a sort of "live variable" of the current project directory.   Could we please have this? It seems simple enough to fetch the "working directory" rather than the "Documents directory environment variable" which is the current behavior. I'd usually ask "can we have this be an optional setting to default to?" but in this case, I'm unable to see the benefit of--or impact from--keeping the current default behavior of saving everything from every project into one single folder.   Minor feature, benefit is that it's one less thing I need to remember to do on every single project export and it eliminates accidentally dumping a project worth of textures into an unintended location. ... View more

For game/app dev, the File > Generate > Image Assets utility, but leaves you with a bunch of images and no info on how they were arranged in PS. I've created a script (with help from searching the forums and the PS scripting guide) that searches through layers and layer sets for anything with a .png layer name, and exports metadata for these items. The script determines the true x, y coordinates for the upper left and lower right corner (the bounding box), and also the color label and linked layers. This information can be used to ingest images into code much more easily, and I wanted to provide the script since I saw a lot of partial things like it in my searching, but never anything quite like it. #target photoshop // This script should be run from within Photoshop String.prototype.endsWith = function( str ) { return this.substring( this.length - str.length, this.length ) === str; }; // PS runs EMCA3, does not know this function var orig_ruler_units = app.preferences.rulerUnits; app.preferences.rulerUnits = Units.PIXELS; var cTID = function(s) { return app.charIDToTypeID(s); }; // Shorten var doc = activeDocument;  var docPath = doc.path;  var output = '';  var txtDoc = new File(doc.path + '/' + doc.name.split('.')[0]+'.json');  doc.activeLayer = doc.layers[0];  var extension = ".png"; var docWidth = doc.width; var docHeight = doc.height; var hw = docWidth/2; var hh = docHeight/2; var centerX = (doc.width/2); var centerY = (doc.height/2); var cropBounds = [(centerX-hw),(centerY-hh),(centerX+hw),(centerY+hh)]; // When layers/groups are duplicated, PS breaks their // links and re-links to the new duplicate layer instead. // Since there is no accurate way to determine layer bounds // consistently for layers and sets, I need to duplicate and // flatten layers, which will break links. As a safety, I've // added Paul Riggott's functions for setting/reverting history. createNamedSnapshot("BeforeExport"); var fileLayers = listMatches (doc, extension); // Get a list of layers/sets with extension compoundList(fileLayers); // Assemble layer info into json string revertNamedSnapshot("BeforeExport"); // Restore doc to pre-script state writeFile (txtDoc, output); // Write json to file deleteNamedSnapshot("BeforeExport"); app.preferences.rulerUnits = orig_ruler_units; function listMatches(lSet, match){      var coords = [];     for(var i=0;i<lSet.layers.length;i++){          doc.activeLayer = lSet.layers; if(doc.activeLayer.typename == 'LayerSet'){ if(doc.activeLayer.layers.length>0){ if(doc.activeLayer.name.endsWith(match)){ coords.push(doc.activeLayer); } var b = listMatches(doc.activeLayer, match); for(var j=0; j<b.length; j++){ if(b .name.endsWith(match)){ coords.push(b ); } } }  }else{ if(doc.activeLayer.name.endsWith(match)){ coords.push(doc.activeLayer); } } };//end loop return coords; }; function compoundList(array){ var len = array.length; for(var i=0;i<len;i++){ var l = array; if(typeof l !== 'undefined'){ var linked = getLayerLinks(l); if(l.typename == 'LayerSet'){ var b = get_bounds(l); }else{ var b = l.bounds; } var x0 = String(b[0]).split(" ")[0]; var y0 = String(b[1]).split(" ")[0]; var x1 = String(b[2]).split(" ")[0]; var y1 = String(b[3]).split(" ")[0]; var col = getLayerColor(l.id); if(col == 'grain') col = 'green'; // Make a json string output += "{"; output += '"name" : "' + l.name + '",'; output += '"x0" : ' + x0 + ','; output += '"y0" : ' + y0 + ','; output += '"x1" : ' + x1 + ','; output += '"y1" : ' + y1 + ','; output += '"linked" : ' + linked + ','; output += '"color" : "' + col + '"'; output += "}"; if(i<len-1){ output += ","; } output += '\n'; } } } function get_bounds(layer){ var copy = layer.duplicate(); activeDocument.activeLayer = copy; copy.merge(); copy = activeDocument.activeLayer; doc.crop(cropBounds); var b = copy.bounds; copy.remove(); activeDocument.activeLayer = layer; return b; } function getLayerColor( layer ) {   var ref = new ActionReference();   ref.putProperty( charIDToTypeID("Prpr") ,stringIDToTypeID('color'));   ref.putIdentifier(charIDToTypeID( "Lyr " ), layer );  return typeIDToStringID(executeActionGet(ref).getEnumerationValue(stringIDToTypeID('color')));   }; function getLayerLinks( layer ) { var lis = layer.linkedLayers; var linked = "["; for(var i=0; i<lis.length; i++){ var layerName = lis.name; if(layerName.endsWith(extension)){ linked+= '"' + layerName + '"'; if(i<lis.length-1) linked+=","; } } linked += "]"; return linked; } // Thanks to Paul Riggott @ Adobe forums for these 2 scripts function createNamedSnapshot(name) {      var desc = new ActionDescriptor();          var ref = new ActionReference();          ref.putClass( charIDToTypeID('SnpS') );      desc.putReference( charIDToTypeID('null'), ref );          var ref1 = new ActionReference();          ref1.putProperty( charIDToTypeID('HstS'), charIDToTypeID('CrnH') );      desc.putReference( cTID('From'), ref1 );      desc.putString( charIDToTypeID('Nm  '), name );      desc.putEnumerated( charIDToTypeID('Usng'), charIDToTypeID('HstS'), charIDToTypeID('FllD') );      executeAction( charIDToTypeID('Mk  '), desc, DialogModes.NO );  };  function revertNamedSnapshot(name) {      var desc = new ActionDescriptor();          var ref = new ActionReference();          ref.putName( charIDToTypeID('SnpS'), name );      desc.putReference( charIDToTypeID('null'), ref );      executeAction( charIDToTypeID('slct'), desc, DialogModes.NO );  };   function deleteNamedSnapshot(name) {      var desc = new ActionDescriptor();          var ref = new ActionReference();          ref.putName( charIDToTypeID('SnpS'), name );      desc.putReference( charIDToTypeID('null'), ref );      executeAction( charIDToTypeID('Dlt '), desc, DialogModes.NO );  };   function writeFile(file, txt) {          file.encoding = "UTF8";          file.open("w", "TEXT", "????");          //unicode signature, this is UTF16 but will convert to UTF8 "EF BB BF"          file.write("\uFEFF");          file.lineFeed = "unix";  var preTxt = '{ "Default" : ['; var postTxt = "]}"; file.write(preTxt);         file.write(txt); file.write(postTxt);          file.close(); alert("JSON Export Created");     };   ... View more

In CC 2018, it was possible to animate a material on a 3D object. I am unable to do so on 20.0.4. The test setup is really straightforward: 1) Create a new, blank 1000 px square document 2) Create a new 3D mesh preset from layer, and make a sphere. 3) Create a new video timeline. 4) Double-click on the sphere's material in the Layers panel to open it. 5) Add a layer, and draw a line on the layer. 6) Create a video timeline, and keyframe the position of the "line" layer. 7) Move the play head to another position and move the "line " layer to create a short animation.  8) Save and close the material. On CC 2018, I could scrub the video timeline and watch the line move on the surface of the sphere. On CC 2019, when I scrub the timeline, the animation in the material does not play. Exporting the rendered video also does not include the material animation. This constitutes a major loss of functionality in the 3D area of Photoshop. ... View more

While I understand that using STL files from Thingiverse aren't guaranteed in any way to work in Photoshop... I have an STL file that used to work flawlessly in CC 2018 and is now utterly unworkable in CC 2019. I've got the latest version as of this posting date. Model looks like this: RackMultipart2019031633278jpa1-05125d8d-2521-43d7-b537-11b82c1d1945-119770193.png (There's a bunch of domes). In CC 2018, opening the file immediately results in a UV map that looks like this: RackMultipart20190316128248kja-55f26a43-ea25-4eda-83ed-914b1fdb7d89-1570501865.png The round parts are the domes, and it all paints quite nicely. In CC 2019, opening the file results in a prompt to generate UVs. The generated UV looks like this: RackMultipart20190316242161cax-bc63d5ee-8d7c-4296-b929-b327590dd4a6-342195605.png It is unusable. The result is the same with/without the preserve appearance checkbox. Additionally!!!! RackMultipart201903164665ncfuu-2dd54c82-49ee-47fb-b664-40accca47aa8-1023566653.png RackMultipart20190316966011tjc-98620e64-d05a-4eba-9d5b-0274d45ecce1-1766408482.png RackMultipart20190316934661y9f-88ed5a82-f957-4f4c-ad40-14a622eb07e3-61583162.png RackMultipart2019031629471sega-f7299b30-5179-483a-8c92-338c0c8cea03-1476156611.png The exact same tool-tip appears for all 3 of these options in the Generate UVs dialog.  ... View more

In Photoshop 19.0, add a Linked Vector Smart Object from the library into your image.Choose Image>Trim. An error will occur and the graphic will become unlinked. Here's the problem in action: https://www.screencast.com/t/jRdrbiqcI ... View more