I’m extremely lost trying to figure this out. I can’t get it to stop warning me about attributes. The only attribute there I can’t delete. The UVs were deleted. I have no idea what to do. Any suggestions?
Using 4.3
1 Like
I came here to post exactly the same issue - it’s really messing with my workflow.
My only guess is that it’s the position attribute that cannot be deleted?
(on my screenshot “sharp_face” is Shade Flat, deleting it does not fix the issue, and I can’t see the polygons)
4.3.0 also. This is my first version 4 experience so no idea if it was present in .1 or .2
I don’t know the exact reason, but it’s a warning that’s output when I choose Dyntopo.
It’s just a warning.
You can ignore it and select OK. 
Normally, in 4.3, there is no warning, if attributes have been suppressed.
It is normal that position of vertices is an attribute, that can not be suppressed.
Otherwise, all vertices would be at origin of mesh.
And sharp_face attribute should not trigger warning.
Normally, only deleting UVs should be necessary, on a mesh that has not been painted or has no custom attribute intentionally created for shading, geometry nodes or mesh editing, or automatically created by addons.
So, maybe, there is an issue with addons or blend file.
Do you have same issue with a new blend file created in 4.3, after a Load Factory Settings ?
If it is a file created in previous releases, does the issue persists with a copy saved in 4.3 ?
If an answer is yes to those questions, you probably should fill a bugreport.
Cheers!
It seems to be per object - there is a ghost attribute I can’t see. Not sure it it’s a leftover from 3.6 that doesn’t show up (I only recently updated).
If I append my rough head sculpt into a Factory Settings file it has the same problem.
A fresh cube (Default UVs deleted) does not have the problem.
badhead-goodcube.blend (630.9 KB)
Sculpt the Head,
Dyntopo on [WARNING], click ok
Sculpt
Dyntop Off
Dyntopo on [WARNING], click ok
Sculpt
As a work-to-do-today workaround, Voxel Remesh with “Preserve: Attributes” un-checked clears the ghost attribute and fixes it. I only use Dyntopo for roughing out, so this works for me.
If you remove the UV, which is set by default, the warning will no longer occur. 
※ Caution, UV is restored when UV is removed with Dyntopo selected.
This appears to be a specific bug/anomaly that I am 100% repeating just with certain specific objects.
There is no UV map, there is no option to delete any UV map, the Warning always happens every time Dyntopo is turned on, there are no visible attributes to delete (except position and shade mode - which do not (typically) trigger, the warning).
This is not expected behaviour and does not occur with freshly created objects.
I uploaded a blend file - if it’s something simple I’ve missed, it may be of use to tealtxgr if someone can figure it out!
Sometimes there are object anomalies that are not resolved by all options.
A personal solution to object anomalies is simple. 
If there is a problem with the object itself, create a new object and combine it with the new object.
This will give you the characteristics of the new object.
It doesn’t always work out well. Back up existing objects for your safety
Good suggestion, but way ahead of you! There is an invisible vertex group or something, combining does not fix it.
1 Like
I’d like to check the object, but if possible, please share it.
Unless it’s impossible to expose or it’s difficult to share due to capacity issues 
Already shared - the post yesterday with the grey head screenshot.
1 Like
Oh nice one!
So it’s a face set issue - oh… face sets are now preserved in Dyntopo mode - I wonder if that’s a factor, like a legacy face-set thing from 3.6 that’s not getting reset.
Well, that’s brilliant whatever it actually is.
Thanks!
EDIT: Confirmed. It’s Face Sets. Just doing “Face set from Visible” fixes it for me.
2 Likes
Well I’m super glad this isn’t me just being dumb at least 
I ended up just remeshing in the long run just so I could get stuff done. Should I go ahead and submit this as an issue since it’s a bug?
It’s a problem that can’t be solved by remesh. 
I think bug reporting will be possible depending on what process the object was created.