Pixel Crushers Forum

This may be a Unity bug. (There were several similar Unity bugs in Unity 2020.) Can you back up your project and update to Unity 2021.1.28 or 2021.2.1?

So, let's check it out. Just a bug unlikely, because I create a new project in this very version and everything works fine. It is in the project is some kind of bug. Another thing I noticed: if you check the "translate to I2" translation is not added, but in the new project adds (I created a new conversation, added nodes, set translations and clicked on "To I2")

The new version doesn't work either.

It could still be a bug in the way Unity's Asset Database has stored metadata about the dialogue database asset. If your project is not too big, you could try Assets > Reimport All.

To double-check a few things:

- There are no errors or warnings in the Console, correct?

- Is this the only dialogue database asset in the project? You can enter "t:dialoguedatabase" in the Project view's search bar to show all databases in the project. If there is more than one database, make sure the correct one is assigned to the DS To I2 window.

- Have you tried setting the DS To I2 window's Verbose dropdown to Warnings? If so, does From I2 log any warnings?

- If that doesn't provide any info, please try setting the Verbose dropdown to Detailed. Then click From I2, and send a copy of the Editor.log file to tony (at) pixelcrushers.com.

Good morning,

Checked with Verbose, found errors, as many as the total fields (if I record a conversation with 3 blocks, there are three errors, if 20, there are 20 errors):

Dialogue System: I2Languages doesn't contain data for Dialogue System/Conversation/1/Entry/1/Dialogue Text
UnityEngine.Debug:LogWarning (object)
PixelCrushers.DialogueSystem.I2Support.DSToI2Window:RetrieveFields (string,System.Collections.Generic.List`1<PixelCrushers.DialogueSystem.Field>,PixelCrushers.DialogueSystem.I2Support.FieldSelectionDictionary) (at Assets/Pixel Crushers/Dialogue System/Third Party Support/I2 Localization Support/Scripts/Editor/DSToI2Window.cs:704)
PixelCrushers.DialogueSystem.I2Support.DSToI2Window:RetrieveDatabaseFromI2 (PixelCrushers.DialogueSystem.DialogueDatabase) (at Assets/Pixel Crushers/Dialogue System/Third Party Support/I2 Localization Support/Scripts/Editor/DSToI2Window.cs:678)
PixelCrushers.DialogueSystem.I2Support.DSToI2Window:RetrieveFromI2 () (at Assets/Pixel Crushers/Dialogue System/Third Party Support/I2 Localization Support/Scripts/Editor/DSToI2Window.cs:597)
PixelCrushers.DialogueSystem.I2Support.DSToI2Window:OnGUI () (at Assets/Pixel Crushers/Dialogue System/Third Party Support/I2 Localization Support/Scripts/Editor/DSToI2Window.cs:199)
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)

As I suspected, something with the "relationship" between I2 and DS.

Hi,

Do you have more than one I2 LanguageSource asset?

In any case, would you please try this: tick the DS To I2 window's Specify I2 Asset checkbox and assign the I2 asset that contains the DS translations. Then try the From I2 button again.

Hi,
I have two sources, one general and one for dialogs and exactly the one I specified for dialogs. I did everything that is specified in the guide. Even when there is one source, I still specify it.

It seems to be working. Should be one source I2, I add a second and can not get data from it, as soon as I leave one all works, though I had to delete the database of dialogs, all over again will have to do, but that's okay, the main thing that worked.

Thank you very much!

Hi,

Glad to help! When 'Specify I2 Asset' is NOT ticked, the DS To I2 window asks i2 Localization to query the default language source. In this case, it sounds like i2 wasn't using the correct language source.

Видимо, но флажок стоял. Какой-то глюк.