Pixel Crushers Forum

Hi there,

I'm a brand new user looking to implement all three tools (Love/Hate - Dialogue System - and Quest Machine).

I'm following along with the integration videos but it seems like every time I get to the end of the first video and try to interact with my NPC I am getting an "Object reference not set to an instance of an object" issue. I noticed that on play the quest machine moves to the "Don'tDestroyOnload" object but the dialogue manager gets destroyed.

When I debug in visual studio it says that the dialogue manager instance does not exist, obviously because the game object is being destroyed on play.

I'm not sure why this would be happening or what I have done to cause this issue. I ran through the dialogue manager wizard/player wizard/ and NPC wizard to make sure I wasn't missing any components and it seems to come back correctly.

Is there a unity package with a demo scene where all three tools are integrated (similar to what the tutorial is doing in the video)? That's honestly the best way for me to learn versus trying to edit and manipulate the demo scenes that are already there, etc.

Thanks so much! looking forward to using these awesome tools if I can get them off the ground.

Hi,

Thanks for using the assets!

A download link for the final tutorial files are in the Description section of the integration tutorial videos.

The Dialogue Manager GameObject has a component named InputDeviceManager. This component only allows one instance of itself to exist. If another GameObject also has an InputDeviceManager, that GameObject's InputDeviceManager may be destroying the Dialogue Manager GameObject. Make sure the only InputDeviceManager component is on the Dialogue Manager GameObject.

If you're adding in the save system, the SaveSystem component behaves the same way. Either put the SaveSystem component on the Dialogue Manager GameObject, or remove it from the Dialogue Manager and put it on a separate GameObject.

Tony thank you so much! I totally missed the final tutorial files! Apologies for not seeing that earlier.

Thank you so much for pointing to the inputdevicemanager I can almost guarantee you that is what it is.

I'll give it a go.

Thanks again for the quick response and amazing feedback.

Glad to help! I'm finishing work for the night, but if any other questions come up, let me know and I'll check in the morning.