Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sprite3D Frame Coords bug #93810

Closed
Rogemcy opened this issue Jul 1, 2024 · 3 comments · Fixed by #93982
Closed

Sprite3D Frame Coords bug #93810

Rogemcy opened this issue Jul 1, 2024 · 3 comments · Fixed by #93982

Comments

@Rogemcy
Copy link

Rogemcy commented Jul 1, 2024

Tested versions

4.2.2 Stable Official
4.3 beta custom build , godot-master 2024_06_30 , scons use_llvm=yes platform=windows target=editor

System information

Win10 64bit

Issue description

QQ截图20240701203443

I also found it in 4.2.2 Stable .

4 2 2 Stable

Steps to reproduce

1, add a Node3D as root node;
2, add a child Sprite3D , load a texture ;
3, check the Sprite3D Animation property -> FrameCoords (should have up/down arrows like other properties for keying).
4, add a AnimationPlayer node , add a new animation ;
5, keying for the Sprite3D's Frame Coords , check the UpdateMode property(should be Discrete by default)

# Minimal reproduction project (MRP)

sprite3d_frame_coords_issue.zip

@AThousandShips
Copy link
Member

Please add some details to your report, this is not enough

@Rogemcy
Copy link
Author

Rogemcy commented Jul 2, 2024

Please add some details to your report, this is not enough

Thanks ! I've uploaded a MRP , And I also found it in 4.2.2 Stable .

@TokageItLab
Copy link
Member

TokageItLab commented Jul 5, 2024

The reason is that the property type of frame_coords in Sprite3D is incorrectly registered as Vector2. Unfortunately, this may need to be fixed in 4.4 as it could causes a compatibility breakdown.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants