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

Re-clarified Armature Scale Warnings. #95

Merged
merged 3 commits into from
Nov 16, 2023
Merged

Conversation

BluWizard10
Copy link
Contributor

This change has been done because as we both know, CATS is not updated anymore to support Blender 3.0 series.

*That is, unless you are informed to use the Dev Branch that Felien is maintaining.

HOWEVER, I feel it might be best to not need to mention CATS anymore because it may become irrelevant (or not) if another Tool of similar functionality exists in the future. So instead, I propose we mention to use "FBX Units" instead as a general term for the Armature Scale Warning.

As you look through these changes to the strings, you will find that I think these are somewhat better explanations for the reasoning behind the Warnings and is future-proof. A line break was also added to the main Armature Scale Warning which will describe more information if viewed from the Console, suggesting to the user (assuming they are using Blender to edit their Avatar) to export their FBX using the instructions I written in. Hopefully this is simple enough for most people to understand.

…gestion.

The Log Message is extended with more information only visible in the Console, assuming the end-user is using Blender.
This included removing the "CATS" suggestion for various reasons. The Log Message is also extended with more information only visible in the Console, assuming the end-user is using Blender.
Updated to match PumkinsStrings.cs
@rurre rurre merged commit d601463 into rurre:master Nov 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants