P: Heal tool overlay not showing - departure from 13.2

"You have to constantly toggle through like 4 options, but it seems as if the points are never full removed."

While the UI has changed over the years (as you've observed) to incorporate the addition of newer Remove modes (Content Aware, Generative AI), the behavior of each mode has in general remained unchanged. So if you're experiencing a problem with a particular mode (e.g. Heal) no longer behaving as it used to, that could indicate a bug rather than a deliberate change. Please start a new thread with details, and attach a full-resolution JPEG exported from the unmodified original photo (not a screenshot) along with screenshots showing the brush strokes you've made and the results.

It feels like whenever there's a subtle change, half the replies argue whether or not there's been a change.

In this case, there is, without a doubt, a frustrating change in hiding any of the previous spot remove/heal/clone/remove (even the name keeps changing?) points. You have to constantly toggle through like 4 options, but it seems as if the points are never full removed.

It'd be one thing if you could set 2 options for the H button. But there isn't.

You really can't argue that there's been a change with folks who have used the tool thousands of time a week for over a decade. I really don't care about the reasoning, justification, etc. It's different, and it's incredibly frustrating.

Same goes for the removal of the opacity slider on the remove/heal/clone/remove tool prior to using it.

STOP CHANGING TOOLS THAT HAVE BEEN THE SAME SINCE THE START. These programs aren't some fun game, they're tools for our professional businesses we use daily.

Imagine changing how the trigger of a drill works for almost all professinal carpenters on the planet. It would never happen, because the idea of that is absurd.

I confirm this has been fixed in my LR 13.5.

Greetings all, 

Updates for the Adobe Photography Products are released.  The August 2024 updates contain an update for this issue. 

If you do not see the update in your Creative Cloud Application, you can refresh it by hitting [Ctrl/Cmd]+[Alt/Opt]+[ R ].

Note: It may take up to 24 hours for your update to be available in your Creative Cloud app.

Thank you for being so patient.

"i would say this bug has been informally recognized by adobe."

The presence of this thread in the Bugs section indicates it's been formally recognized. Adobe moderators, part of the product team, carefully curate this section's contents. There have been many bug reports that never get a comment from Adobe employees until the fix is released, e.g.

https://community.adobe.com/t5/lightroom-classic-bugs/p-sdk-photo-applydeveloppreset-preset-can-lockup-lrc-with-ai-settings/idc-p/14630771

https://community.adobe.com/t5/lightroom-classic-bugs/p-sdk-photo-applydeveloppreset-preset-can-lockup-lrc-with-ai-settings/idc-p/14630771

https://community.adobe.com/t5/lightroom-classic-bugs/p-14-3-sonoma-wb-picker-loupe-tool-is-stuck-after-first-click/idc-p/14630702

https://community.adobe.com/t5/lightroom-classic-bugs/p-quot-debug-capture-time-quot-appears-in-dialog/idc-p/14436236

https://community.adobe.com/t5/lightroom-classic-bugs/p-sdk-keyword-setattributes-fails-to-change-the-case-of-the-keyword-s-name/idc-p/14436227

https://community.adobe.com/t5/lightroom-classic-bugs/p-profile-for-canon-rf-24-105mm-f2-8-l-is-usm-z-has-edge-artifacts/idc-p/14436214/

https://community.adobe.com/t5/lightroom-classic-bugs/p-french-german-spanish-masks-panel-scaling-issue/idc-p/14146189

https://community.adobe.com/t5/lightroom-classic-bugs/p-inconsistent-counts-in-the-metadata-browser-for-directly-assigned-keywords-containing-children/idc-p/14146192

https://community.adobe.com/t5/lightroom-classic-bugs/p-can-not-connect-to-remoter-server/idc-p/14013884

https://community.adobe.com/t5/lightroom-classic-bugs/p-edit-in-photoshop-sends-it-to-the-photoshop-beta-not-2023-no-option-to-choose/idc-p/13819340

i would say this bug has been informally recognized by adobe. In other threads, an adobe employee has responded in the thread. for example, from a different thread:

"We've identified this bug as already filed in our system. A fix should be released shortly. 

Rikk Flohr - Customer Advocacy: Adobe Photography Products
STATUS: Acknowledged"

this thread has no such acknowledgement 

"has this bug been identified and filed in adobe's system. will a fix should be released shortly?"

This bug has been formally acknowledged by Adobe, which is why the thread was moved into the Bugs section of the forum. At this point, we likely won't hear back from them until the the bug is fixed, at which point they'll update this thread. Adobe rarely indicates when a bug might be fixed.

has this bug been identified and filed in adobe's system. will a fix should be released shortly?

curious, as adobe has replied to other bug posts stating that the bug stated had been identied.

could adobe also please reply here as well?

@mark233495990o4g: "each photo could have 50 or so spot removes. so without the ability to know in real time without a doubt where you are sampling from, it's like fumbling in a dark room without a flashlight. and it takes twice as long if you have to keep going back to check your work. "

Did you see the workaround:

https://community.adobe.com/t5/lightroom-classic-bugs/p-heal-tool-overlay-not-showing-departure-from-13-2/idc-p/14724316#M55315

It's a couple more clicks per spot, which I know adds up with many removals, but it will give you the control you need while waiting for this to be fixed.

I use the spot removal tool extensively. each photo could have 50 or so spot removes. so without the ability to know in real time without a doubt where you are sampling from, it's like fumbling in a dark room without a flashlight. and it takes twice as long if you have to keep going back to check your work.  

Also, when you drag to adjust the sample area, it is no longer precise. you move the mouse but the sample area doesn't change until you move it further than you'd like. has anyone else noticed this?