cbtsam Loc: Monkton, MD

I wonder if anyone else has had this problem with the Generative Expand function in PS Beta 25.1 and found a solution. It seemed to work pretty darn well in 25.0, but in 25.1, there is a visible margin between the expanded area and the original, as if the new stuff is offset several pixels. I've tried many different generations of the same area, with no difference. I've tried feathering the selection before using the function, with no difference.

If it matters, I'm running an iMac 5K 27", 2017, with a 4.2 GHx Quad Core intel Coe i7, a Radeon Pro 580 8 GB, and 32 GB 2400 MHz DDR4, and Ventura 13.5.1.

terryMc Loc: Arizona's White Mountains

I have noticed some weirdness in the Generative Expand, if not specifically that one. It seems a bit temperamental, and you have to do things in a certain precise order.

Yesterday I expanded a canvas and something went awry, so I started over, leaving the transparency from the first attempt. It would not generate until I made a new crop, and then generated outside the leftover transparency leaving a transparent gap between the new detail and the image. I guess you're supposed to undo and start all over, but I will usually resort to just using Generative Fill and selecting with the marquee after expanding the canvas. That always works.

Rongnongno Loc: FL

I would hope that you are reporting this to Adobe BEFORE posting here... This is why the beta is out: Report bugs.

Klickitatdave Loc: Seattle Washington

I have run into the same issue with Beta 25.1 and unfortunately like you have not found a workaround other than to run the remove tool over the affected area. This works reasonably well but obviously is not an ideal solution. I did report the issue to Adobe so hopefully, it will be resolved in the next release.

cbtsam Loc: Monkton, MD

Sure thing, Ron. Each generative gesture comes with three little dots, and clicking them allows one to rate the outcome, and/or report something about the outcome. I've reported several failures, and this one several times.

However - I know this will surprise everyone - Adobe has not been in the habit of getting back to me with suggestions regarding how the old coot in the mirror might have been the bug, creating the unsatisfying outcome by stupid commissions and/or omissions. Thus, da Hog.

cbtsam Loc: Monkton, MD

Thanks to terryMc and to Klickitatdave for your attempts to help me out.