# Issues with Keypoints Visibility and Class Changes in Roboflow

**URL:** <https://discuss.roboflow.com/t/issues-with-keypoints-visibility-and-class-changes-in-roboflow/7057>\
**Category:** 🤝  Community Help\
**Created:** [September 16, 2024, 10:11am UTC](https://discuss.roboflow.com/t/issues-with-keypoints-visibility-and-class-changes-in-roboflow/7057 "2024-09-16T10:11:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Martin\_Perosa](https://yyz1.discourse-cdn.com/flex029/user_avatar/discuss.roboflow.com/martin_perosa/32/5477_2.png) [@Martin\_Perosa](https://discuss.roboflow.com/u/Martin_Perosa)\
**Post date:** [September 16, 2024, 10:11am UTC](https://discuss.roboflow.com/t/issues-with-keypoints-visibility-and-class-changes-in-roboflow/7057/1 "2024-09-16T10:11:52Z")

</div>

I am experiencing an issue while working with keypoint annotations on my project. I have also created a video to demonstrate the problems, which I have attached for your reference.

1. **Class Change Issue** : I am working with three classes: “player,” “non-player,” and “referee,” all of which use the same skeleton structure. When I try to change the class of an object (e.g., from “player” to “referee”), Roboflow resets all the keypoints to the default skeleton values, causing me to lose the existing keypoint positions. Is there a way to change the class of an object without resetting its keypoints?

I have attached a video explaining and demonstrating the issue to provide better context.  
Thank you in advance for your support.

> **[Screen sharing - 2024-09-16 11\_44\_33 AM.mp4](https://drive.google.com/file/d/1lj1ejESoX3kx__CYVEfsW6AljX0j-ONw/view?usp=drive_link)**
>
> Google Drive file.

---

<div class="post-metadata">

**Author:** ![leo](https://yyz1.discourse-cdn.com/flex029/user_avatar/discuss.roboflow.com/leo/32/2228_2.png) [@leo](https://discuss.roboflow.com/u/leo)\
**Post date:** [September 16, 2024, 12:16pm UTC](https://discuss.roboflow.com/t/issues-with-keypoints-visibility-and-class-changes-in-roboflow/7057/3 "2024-09-16T12:16:20Z")

</div>

Hey @Martin_Perosa

Thanks for sending this in, we appreciate the feedback. It’s interesting that in your use case, there are three classes with the exact same skeletons. This is usually not the case for most keypoint detection projects and this is why the default behavior is to reset to the default skeleton.

Do all your skeletons have the same ID number as well?

---

<div class="post-metadata">

**Author:** ![Martin\_Perosa](https://yyz1.discourse-cdn.com/flex029/user_avatar/discuss.roboflow.com/martin_perosa/32/5477_2.png) [@Martin\_Perosa](https://discuss.roboflow.com/u/Martin_Perosa)\
**Post date:** [September 16, 2024, 12:33pm UTC](https://discuss.roboflow.com/t/issues-with-keypoints-visibility-and-class-changes-in-roboflow/7057/4 "2024-09-16T12:33:09Z")

</div>

> [@leo](#):
>
> Do all your skeletons have the same ID number as well?

Where can I see it? When I upload my annotated frames, I only have the ‘player’ class annotated, and I created the other classes in Roboflow. How can I create and share the same skeleton ID?

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex029/uploads/roboflow1/original/1X/bb6edbfa56d0cf2ee603f061e9e09103502cc8cc.png) [@system](https://discuss.roboflow.com/u/system)\
**Post date:** [October 7, 2024, 12:33pm UTC](https://discuss.roboflow.com/t/issues-with-keypoints-visibility-and-class-changes-in-roboflow/7057/5 "2024-10-07T12:33:17Z")

</div>

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.