P: Generative Remove Feedback (Lr Classic & Lr Eco)

@August_The_Dragonfly: "Remove tool has occasionally started filling space with solid black instead of the generated image"

There's been another report about that recently:

https://community.adobe.com/t5/lightroom-classic-discussions/p-generative-remove-feedback-lr-classic-amp-lr-eco/m-p/15568689#M416660

If the problem were widespread, we would have seen many reports about it by now. So it may be restricted to a small subset of photos or something specific to particular installations.

Try updating your graphics driver by going directly to the manufacturer's web site, rather than relying on Windows Update or a manufacturer's update utility:
https://helpx.adobe.com/lightroom-classic/kb/troubleshoot-gpu.html#solution-4

If that doesn't help, please copy/paste here the entire contents of the LR menu command Help > System Info -- that will let us see exactly which versions of hardware and software LR thinks you're running.

@Emily35418231mkqg: "since updating Lightroom, the generative removal AI tool has really decreased in intuition for certain removals/replacements"

See my post above:

https://community.adobe.com/t5/lightroom-classic-discussions/p-generative-remove-feedback-lr-classic-amp-lr-eco/m-p/15573142#M417054

@Magnus5C29: "Since the recent update to Generative Remove, it seems to affect areas outside of the brushed selection. It used to stay perfectly within the brushed area, but now it changes surrounding parts of the image too"

This started in LR 14.5 (August) and has continued through LR 15.0. Many have complained about the problem, and Adobe has acknowledged it as a bug:

https://community.adobe.com/t5/lightroom-classic-bugs/p-gen-remove-now-changes-elements-outside-the-painted-mask/idi-p/15457946/

where Adobe employee Sameer K wrote, "The team has identified the issue, but the fix wasn't included in the Lightroom Classic v15 release. It'll arrive soon, as this issue goes beyond Lightroom Classic and also requires broader fixes in Camera Raw."

@thedogwithnobrain: "Rather than generating a fill the selected area just goes black."

Using your screenshot, that problem doesn't occur in m LR 15.0 / Mac OS 15.7.1 / Macbook Pro M2 Max.

1. Which of the options Use Generative AI and Detect Objects have you selected?

2. If the forum won't let you attach the file here, upload it to Wetransfer, Dropbox, Google Drive or similar free service and post the sharing link here. We can see if the issue is specific to your computer or occurs on other installations. Adobe is much more likely to pay attention if they can easily reproduce the problem.

No, it doesn't.

I updated Lightroom, now it use the new base so I can't roll back to the working version, and the generative removal tools still broken. It still disrespect selection boundary, especially for small selected area, running the objected I'm working with. This is a disaster! 

@Ilham_Zovanka8747: "Generative Remove Failed. Unfortunately, this feature is not available in your region at this time."

According to this Help article:

https://helpx.adobe.com/firefly/web/get-started/learn-the-basics/adobe-firefly-faq.html#react-spectrum-4

"Adobe Firefly isn't available in Russia, Belarus, and China. In addition, Adobe services and products cannot be used in Cuba, Iran, North Korea, Syria, Crimea, and the so-called Donetsk and Luhansk People's Republics."

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]

@OraChaya: "Instead of removing the person next to this girl, it put a new person there".

That usually happens when you've left a small bit of the object unselected or haven't selected all of its shadow. Make sure you've selected all parts of the person's pants at the bottom and increase the selection around his shoulder.

Do Help > System Info -- which version number of LR are you running? The behavior of Generative Remove changed recently.

With your screenshot, I was able to remove the person.  If you're still stuck, attach here a full-resolution JPEG exported from the unedited original, and we can probably get it working.