Pixel Crushers Forum

So... Instead of foreach(db in databases){foreach(q in quests){...}} I should be able to select quests/actors using LINQ Distinct and ID as a unique key, right?

If I understand you correctly, working on guids would require me to track 'original guid' and somehow to know which quest is the 'original one' and which one is its copy in the synced DB... I noticed that in Dialogue window you display synced items (actors/quests) as not interactable(they are greyed...

Thanks a lot. Another question: We keep our quests in a separate database from dialogues and we synchronize them using SyncFrom/Syncnow. The thing is that we get a separate entry for each quest that is synced between databases. The same goes for actors and probably every shared/synced item. Can we d...

Hi again Tony, sorry for the late response... regarding your previous answer: - I updated DS to 2.2.46.1 - I used Localization Package Integration(must have omitted this before, because this time I can see String Table to DS button...sry for that) - I added component Localization Bridge Component So...

Hi Tony, I am in the process of updating our DS to the version you mentioned, but I still struggle with localizing the quests. In the docs https://www.pixelcrushers.com/dialogue_system/manual2x/html/localization.html you mention "DS To Loc window's "String Table To Dialogue System"&qu...

Damn you are right. I completely forgot we switched to the default one after having issues with restoring UI input in some cases... Thank you very much!

Thank you for the quick reply.
The thing is that we already have selected UI/Submit in our InputSystemUIInputModule. Still, as my colleague said we receive "dialogue skips" on the not-related buttons/keys...