Specified target is being changed by the system

Start
Prev
1
Next
End

1

grit
Topic Author
Offline
New Member

More

7 years 11 months ago #1437 by grit

Specified target is being changed by the system was created by grit

Dear Frank,

I am using objects, which have a Tk 2D Sprite component as well as an Audio Source component.
I want to localize the AudioClip in the Audio Source (not the tk2d sprite). Thus I choose "AudioSource" as a target.
The term type is an AudioClip.

This worked fine before with an older version of I2 Localization (2.4.5 f3)

I just updated my whole project (Unity 5.3.4 f1) and along with this also the I2 plugin (to 2.6.5 f5).
Now every time I run the game or only switch between scenes, the target is being switched to 2DToolKit Sprite, and the localization doesn't work any more because of that. The error tells me, that the sprite is not being found in the collection, because of course it is actually an audio clip. The log:

SetSprite - Sprite not found in collection: GameCounting/01_game_counting_1_fr
UnityEngine.Debug:LogError(Object)
tk2dBaseSprite:SetSprite(String) (at Assets/Plugins/tk2d/Code/Sprites/tk2dBaseSprite.cs:260)
I2.Loc.Localize:DoLocalize_tk2dBaseSprite(String, String) (at Assets/Plugins/I2/Scripts/Targets/Localize2DToolKit.cs:78)
I2.Loc.Localize:OnLocalize(Boolean) (at Assets/Plugins/I2/Scripts/Localize.cs:169)
I2.Loc.LocalizeInspector:OnDisable() (at Assets/I2/Localization/Scripts/Editor/Inspectors/LocalizeInspector.cs:87)

I am not sure, if I might have messed something up, because in this project I am using UnityScript instead of C#, and because of that, I had to reorganize the folder structure of your plugin a little, see attached screenshot.

Do you have an idea why this is and how to solve this?

Thanks a lot,
Grit.

Please Log in or Create an account to join the conversation.

Frank
Offline
Administrator

More

7 years 11 months ago - 7 years 11 months ago #1441 by Frank

Replied by Frank on topic Specified target is being changed by the system

Hi,
Thanks for reporting this issue!
I just uploaded a new version of the plugin (2.6.6a2) to the beta folder that includes a fix for that.

Hope that helps,
Frank

Are you