Small bug still with updating slots/textures without DNA about uma

[ecurtz]

I honestly have very little recollection about what the accessedFrame field is trying to solve. I vaguely recall complaining about it in the past and receiving some sort of explanation, it might be obsolete at this point, or perhaps PowerTools is using it in some way?

I didn't think that EnsureBoneHierarchy() would be an issue because it isn't changing the bone data like the other one was it's just resetting, but I think that should be to the existing current state.

[DirtyHippy00]

I agree - this certainly seems like sketchy behaviour, but since that logic is used in many places I suspect it is actually there for a reason. I am guessing by not executing this logic we will see some side effects at some point - but I have not noticed any myself with a decent bit of testing now (with both full updates and just slot/overlays).

[Jaimi]

Is this still an issue, or can this item be closed?

[DirtyHippy00]

This is still an issue. The only way it behaves as expected is if "res.accessedFrame = -1;" is commented out in EnsureBone. I upgraded to the newest UMA not super long ago, and I had to make this change manually (I had an internal reminder comment for it), in order for this to work correctly.

[Jaimi]

Removed and tested with ragdoll, additional boned slots, changing race, etc.