Page 1 of 1

Unit Localization problem [Solved]

Posted: Sat Jan 23, 2010 7:49 pm
by General_Nate
Hey guys! I've been trying to localize my sides from being "X1h975Z865z9756" to "Terminator"
But I've had no success, yet. I followed THIS tut, but I think it's a bit out dated.

Anyway, here is what I have:
Hidden/Spoiler:
[+]entity
|
[+]ter
|_ter_inf_trooper
And even with that, "X8645X977x960" still butts his ugly head on the side selection screen...

I have checked and re-checked spelling, and everything matches up.

Could someone post a link to a more updated tut, or maybe show me how here? Thanks! :thumbs:

Re: Localization problem

Posted: Sat Jan 23, 2010 8:27 pm
by AQT
After editing your localization, did you remember to check the Localize box in VisualMunge before munging? If not, that could be the problem.

Re: Localization problem

Posted: Sat Jan 23, 2010 8:31 pm
by General_Nate
AQT wrote:After editing your localization, did you remember to check the Localize box in VisualMunge before munging? If not, that could be the problem.
I sure did...

Re: Localization problem

Posted: Sat Jan 23, 2010 8:41 pm
by AQT
The tutorial was pretty clear. It just failed to mention how to launch the tool, saving, and what to check when munging. Please post a screenshot of the MultiLanguage tool, expanded showing where you set up the localization for your unit.

Re: Localization problem

Posted: Sat Jan 23, 2010 8:46 pm
by AceMastermind
General_Nate wrote:[+]entity
|
[+]ter
|_ter_inf_trooper
Side name is irrelevant, the odf name is what matters, in your illustration you're saying the unit's odf is ter_ter_inf_trooper.
If your unit odf is ter_inf_trooper the tree should look like this:

entity
  • ter (scope)
    • inf_trooper (key)

Re: Localization problem

Posted: Sat Jan 23, 2010 9:08 pm
by General_Nate
AceMastermind wrote:
General_Nate wrote:[+]entity
|
[+]ter
|_ter_inf_trooper
Side name is irrelevant, the odf name is what matters, in your illustration you're saying the unit's odf is ter_ter_inf_trooper.
If your unit odf is ter_inf_trooper the tree should look like this:

entity
  • ter (scope)
    • inf_trooper (key)
Eureka!!! That fixed it.

Thanks a ton guys, can be solved!