Pixel Crushers Forum

Hi all,

I'm currently trying to go through the quest machine tutorial, where the dialogue system is integrated.

I've followed the guide and paid attention to ensure the same questgiver id is used with the corresponding to the actor, similarly the player id is the same as that in the attached player quest journal as it is in the actor list. (The player id is Player, like that in the example)

I seem to be getting an error for DialogueSystemQuestDialogueUI.GetPlayerActorTransform() or DialogueSystemQuestDialogueUI.FindMainPlayerActor() functions, please see attached image for console log.

Am i missing some key setup feature linking the actors in the database with quest machine ids?

If you need any moreinformamtion on my current setup please let me know.

Regards,

Liam

Hi,

It looks like you might be using an old version of the integration. Are you using the latest versions of Quest Machine and the Dialogue System?

You can also download an updated integration package from the Quest Machine Extras page. By itself, it won't fix the issue you see, but it may prevent a different issue in the future.

Does your scene have a Dialogue Manager GameObject?

Have you assigned a dialogue database to the Dialogue Manager GameObject?

You may also be interested in this walk-though of the integration steps: QM-DS Integration Walk-Through

I have version 1.2.3 for Quest Machine and version 2.2.3 for Dialogue System, so i'm only a minor revision back, would that make too much of a difference? Unless i've copied old prefabs from examples which don't work with the new software versions?

I have a Dialogue manager in the scene including my dialogue database with the relevant conversation between my player and NPC,

The quest used inside the dialogue manager is labeled the same as the quest id in quest machine.

Inside my quest machine quest, i've selected the conversation option in the offer text box for the quest with relevant dialogue database and conversation selected, the same can be said for the active and completed states dialogue text fields.

I suspect that if you update to the latest QM and DS, including the updated integration package on the Quest Machine Extras page, it will fix the issue.

I downloaded the new integration package and works a charm, thank you so much.

Glad to help!