P: Subject Mask from previous versions are requesting an update

@dewaynec  I would recommend contacting Support. They have tools to repair catalogs and can assist you here. 

Well this has been a right cluster, Adobe. After having 14.0 trash my masks, I updated to 14.0.1, unzipped the old catalog files from "Old Lightroom Catalogs", copied them over the top of the botched 14.0 files, launched 14.0.1, it tells me my catalog is corrupt and needs repaired, it "repairs" it, upgrades it, opens it, and IT'S FREAKING EMPTY!!!

A bit of context for the users is need.

Ai needs to be updated in 4 cases:

1. A new ModelVersion has shipped.

LrC never informs users of this, it just demands you update your Ai without explanation...there is no way to determine current ModelVersion for any existing AI beside using the SDK/API photo:getDevelopSettings

2. Remove has been done and might affect the existing Ai Selection (Sky, Background, Subject, etc...)
Reality is LrC never really verifies the location of the Remove so you must check yourself.

e.g.

Create a Ai Sky Mask.
Use remove NOT on the Sky...on the land.

LrC knows there is a Sky Mask and demands an update..BUT alas is not needed because the Sky is not affected.

3. Image was flipped vertically or horizontally.

This affects Ai selections such as Sky.

4. Empty Ai maks or Remove are present on the image and thus need to be updated.

LrC leaves Empty Ai on the photo because if you sync or copy them to another image it might actually detect them.

Empty Remove are the result of interrupting "Update Ai Settings" when Syncing or Pasting the Ai powered Remove (Ren Remove , Content Aware)
.

Last but not least: Users should check always if the Update of AI settings gave better or worse results...visual check only.

@dewaynec 

  "Honestly, this whole "updating masks" thing doesn't make a lot of sense to me anyway. If Lightroom knows a mask needs      updated, why doesn't it just update it then?"


Because it is computationally expensive to update them AND also lrC let's users decide when its best to do it to minimise creating useless history steps.

e.g

Suppose you do a new Remove (Clone/Heal/Gen Remove...or Objects Aware)
LrC doens't know if you need to do another Remove right after this one, LrC lets you decide when it's best to Update Ai Settings

Otherise in history you would end up with this sequence:

Update Ai Settings
New remove Spot

Update Ai Settings
New remove Spot

If LrC was updating Ai Settings automatically then you would find yourself staring at the Update Ai setting modal progress basically every time LrC finds one in need of Update..and if you cancel the update you end up with Empt Maks that will need to be updated...and the auto update would start again ad infinitum till you let it finish.

Not good.

What are you saying ? There is a LrC version 14.

Even a 14.01 from today

Quick update: I'm seeing the update mask prompt now. It appears that Lightroom wants to update all the generative masks (subject, object, and so on) in an image. As far as I can tell, the mask adjustments seem to be intact. 

Honestly, this whole "updating masks" thing doesn't make a lot of sense to me anyway. If Lightroom knows a mask needs updated, why doesn't it just update it then?

I just updated Lightroom for the first time today to version 14, so I received the 14.0.1 release. Nonetheless, I'm still seeing a masking red dot on images that have masks. However, going through the individual masks doesn't show any masks that need an update. So maybe this issue isn't completely fixed yet? Or possibly I'm missing something?

One of our editors upgraded from 13 to 14 and is struggling with the mask/removal bug. All AI Gen removal edits need regenerated...

My question is, will upgrading to 14.0.1 fix it using the upgraded v14 catalog, or do I need to first restore the v13 catalog and then upgrade to 14.0.1?

Sorry if this is discussed, but the post from Rikk is a bit confusing.