Can't get set_text_voice_synced method to work

[uptothedog]

Hi, I'm trying to sync up my text reveal speed to my voice audio files as this seems to make a lot of sense in my use case. In the documentation I've found the following built-in method, which should exist for the Text subsystem:

func set_text_voice_synced ( enabled: bool = true ) ⇒ void

This method will sync the text speed to the voice audio clip length, if a voice is playing. For instance, if the voice is playing for four seconds, the text will finish revealing after this time. This feature ignores Auto-Pauses on letters. Pauses via BBCode will desync the reveal.

Now it's fair to say I'm a total beginner so I might just be messing this up, but I'm failing to find any trace of this built-in method even existing in the Text subsystem by trying to call it, nor do I find a mention of it within the subsystem_text.gd script.

Could someone give me some pointers on how to use it?

[CakeVR]

Hello, you would call this as Dialogic.Text.set_text_voice_synced(true). This is the same procedure for all the methods on that page.

[uptothedog]

Hmm, that's a shame; I did try to follow the instructions closely, and did use the migration tool. Thankfully I'm still in the beginnings of my game project, so it shouldn't take too long to do a clean install as you described.

I don't know if my experience will be helpful or not (I know those errors aren't very specific), but with the official release of Dialogic 2, there will be more users in the near future making the migration from 1 to 2.

To possibly help prepare for issues that may arise, let me know if there's any specific files you'd like to look at that have been created as a result of version 1 to 2 migration, and I can then try and provide those (I'll be keeping the malfunctioning project).

Thank you for your help.

[CakeVR]

I don't recommend changing from Dialogic 1 to 2. First, Godot 3 and 4 (requirement for Dialogic 2) are fundamentally different and so are Dialogic 1 and 2. I never used the existing Converter, we moved it out of the main repository, and there is currently no more development planned for it. It may still work to degrees. There are some success stories using the Converter.

You don't have to create a new project, but it's the cleanest way to go about this. The other way would require to cleanly check all the configuration files of Godot and clear the .godot folder cache.

[uptothedog]

Well, I've now migrated to a new project, but it seems this signal still isn't working. Is my way of connecting the signal incorrect? And if so, has the way Dialogic emits these signals perhaps changed somewhere along the line, as this connection did work before?

To provide further context, I have a script to handle the animations of my custom portrait. I've set this script to wait for signals from Dialogic, and my goal with these specific signals is to revert my portrait to an idle animation when the voice line is no longer playing.

Dialogic Core is set to autoload for the project.

Dialogic signal in the portrait handler script:
Dialogic.Voice.connect("voiceline_finished", Callable(self, "_on_voiceline_finished"))

Commenting anything out after when the script is supposed to be receiving the signal doesn't affect Godot in throwing me the error.

Error:

Stack trace: Cannot call method 'connect' on a null value.
Errors:

E 0:00:01:0990   DialogicGameHandler.gd:346 @ get_subsystem(): Node not found: "Voice" (relative to "/root/Dialogic").
  <C++ Error>    Method/function failed. Returning: nullptr
  <C++ Source>   scene/main/node.cpp:1638 @ get_node()
  <Stack Trace>  DialogicGameHandler.gd:346 @ get_subsystem()
                 DialogicGameHandler.gd:129 @ @Voice_getter()
                 PortraitHandler.gd:8 @ _ready()

If this path is supposed to be the project path, it looks incorrect in how Dialogic 2 is supposed to be installed (in the /addons/ folder).

[uptothedog]

Solved. I'd made a mistake with the loading order and the signals weren't there when the script was trying to connect to them, because they didn't get the chance to exist yet.

It seems this would have been very difficult to infer from the information I'd shared, so that'd be a lesson for me. My bad!