Hi,
I experienced an issue. Under Speech Manager, under Game text at Translatable text types, I checked Speech and Dialogue Option. And I loaded my translated texts. When I'n in Play Mode and I set other language, I got many Information (white) messages like these for all text types, menus etc...and getting it continuously.
"Cannot find translation for 'Use' because the text has not been added to the Speech Manager.
-> AC debug logger
UnityEngine.Debug:Log(Object, Object)
AC.ACDebug:Log(Object, Object) (at Assets/AdventureCreator/Scripts/Static/ACDebug.cs:16)
AC.RuntimeLanguages:GetTranslation(String, Int32, Int32) (at Assets/AdventureCreator/Scripts/Speech/RuntimeLanguages.cs:260)
AC.MenuInteraction:RecalculateSize(MenuSource) (at Assets/AdventureCreator/Scripts/Menu/Menu classes/MenuInteraction.cs:478)
AC.Menu:AutoResize(MenuElement) (at Assets/AdventureCreator/Scripts/Menu/Menu classes/Menu.cs:1543)
AC.Menu:Recalculate() (at Assets/AdventureCreator/Scripts/Menu/Menu classes/Menu.cs:1492)
AC.PlayerMenus:RebuildMenus(MenuManager) (at Assets/AdventureCreator/Scripts/Controls/PlayerMenus.cs:135)
AC.PlayerMenus:OnStart() (at Assets/AdventureCreator/Scripts/Controls/PlayerMenus.cs:88)
AC.StateHandler:InitPersistentEngine() (at Assets/AdventureCreator/Scripts/Game engine/StateHandler.cs:962)
AC.StateHandler:OnAwake() (at Assets/AdventureCreator/Scripts/Game engine/StateHandler.cs:81)
AC.KickStarter:SetPersistentEngine() (at Assets/AdventureCreator/Scripts/Game engine/KickStarter.cs:155)
AC.KickStarter:OnAwake() (at Assets/AdventureCreator/Scripts/Game engine/KickStarter.cs:1069)
AC.MultiSceneChecker:Awake() (at Assets/AdventureCreator/Scripts/Game engine/MultiSceneChecker.cs:50)
"
I just don't understand that, if I set the Speech and Dialogue Options text types at Translatable text types, why is there running checks for other types and get messages continuously? Thank you, Chris in advance!:)
My Unity version: 2019.2.9f1
My AC version: v1.70.1
It looks like you're new here. If you want to get involved, click one of these buttons!
Comments
This should have been resoled in v1.70.4 - please import the latest release and try again.
Thank you, Chris, it solved this issue!