Keypoints reset to default pose when switching between two classes (Undo restores original positions)

[h-furukoori]

Summary

When switching between two registered classes in the Keypoint Editor, existing keypoints are replaced by the class default pose (initial coordinates).

However, performing Undo restores the correct original keypoints.

This suggests the annotation data itself is preserved, but the display state is being overwritten.

---

Important Condition

This issue occurs only when:

• Two classes are registered in the project

• The annotated object’s class is switched between those two classes

It does not occur in single-class setups.

---

Steps to Reproduce

1. Prepare a project with two classes (both having keypoint skeletons)

2. Annotate an object using one class

3. Confirm keypoints are correctly positioned

4. Change the object’s class to the other class

5. Observe keypoints are replaced by default pose

6. Press Undo

7. Original keypoints reappear

---

Expected Behavior

When switching between classes:

• Existing keypoints should remain, or

• Be mapped to the new class skeleton if compatible

They should not be replaced by default coordinates unless explicitly reset.

---

Actual Behavior

• On class switch, keypoints immediately change to default pose

• Undo restores original keypoints

---

Key Observation

Since Undo restores the correct positions:

• Annotation data appears intact

• The issue likely occurs in rendering / class-switch handling

• Default skeleton pose seems to be re-applied during class change

---

Impact

If saved after class switching (without Undo),
the default pose may overwrite correct annotations,
risking silent data corruption.

---

When it Started

Observed since around Feb 24, 2026.

---

Question

Were there any recent changes to:

• Skeleton initialization

• Class-switch handling

• Assist / auto pose logic

that could cause default pose application when switching between two classes?

Happy to provide screen recording if needed.

[Nathan_Badanjek]

Hello,

Thank you for posting here, I understand your frustration behind the Key Point reset upon changing classes. Unfortunately there is no way at this moment to map Key Points from one class to another. I would suggest ensuring the correct class is chosen before editing the Key Points on one Object while a separate solution is reached. I’ve passed this request onto product for further review.

Thank you!

[h-furukoori]

Hello, thank you for your reply.

However, I believe there may be a misunderstanding. I am not trying to map Key Points from one class to another. The issue is that when I switch classes in the “Annotation Editor” dialog on the annotation screen, the coordinates of the Key Points reset to their initial positions.

This occurs not only in past projects but also in newly created projects. I have cleared the cache in Edge and was able to reproduce the issue, and it also occurs in Chrome. Therefore, it does not seem to be a problem with my local environment.

This issue started occurring around February 24, 2026.

Thank you for your assistance.