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

Allow setting values greater than the maximum in TorusMesh inspector #80441

Conversation

Calinou
Copy link
Member

@Calinou Calinou commented Aug 9, 2023

This is consistent with other PrimitiveMeshes' behavior.

This is consistent with other PrimitiveMeshes' behavior.
@akien-mga akien-mga modified the milestones: 4.x, 4.2 Aug 9, 2023
Copy link
Member

@clayjohn clayjohn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

Notably TubeTrailMesh, and RibbonMesh still don't have the or_greater on all ranges. However, in those cases, rings and splits can also change how they are calculated in the particles shader and can lead to serious issues. So I think it is okay not to increase the ranges on those unless users really need it

@akien-mga akien-mga merged commit 7257d16 into godotengine:master Aug 9, 2023
15 checks passed
@akien-mga
Copy link
Member

Thanks!

@Calinou Calinou deleted the editor-torusmesh-inspector-hint-or-greater branch August 10, 2023 05:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Make property limits of PrimitiveMesh soft limits
4 participants