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

AnimationTree has unintentional translations #86033

Closed
KoBeWi opened this issue Dec 11, 2023 · 2 comments · Fixed by #87887
Closed

AnimationTree has unintentional translations #86033

KoBeWi opened this issue Dec 11, 2023 · 2 comments · Fixed by #87887

Comments

@KoBeWi
Copy link
Member

KoBeWi commented Dec 11, 2023

Tested versions

4.2

System information

Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 (NVIDIA; 30.0.15.1403) - Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 Threads)

Issue description

I noticed that AnimationTree will translate animation names.

AnimationPlayer:
image

AnimationTree:
image
Both the display and list are translated.

Then on another look, seems like are more unintentional translations here, like node Titles and path.
image
Here Output is fetched from the bottom tab name (which in Polish is translated as console, because literal translation would be less clear). Seems like the node has a name, which gets capitalized and then auto-translated (as evident by error messages that call it "output").

image
Here Root is translated, which I think is another case of capitalized name.

Steps to reproduce

  1. Make sure editor is not using English
  2. Create AnimationPlayer
  3. Add animation with a name that exists in translations
  4. Add AnimationTree and set AnimationNodeBlendTree as root
  5. Add Animation node

Minimal reproduction project (MRP)

N/A

@AThousandShips
Copy link
Member

Does these controls have translation off by default? Like some other cases like this

See also:

@KoBeWi
Copy link
Member Author

KoBeWi commented Dec 11, 2023

AFAIK every Control has autotranslation enabled by default. So it needs to be fixed in case-by-case basis.

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.

3 participants