New User Having Trouble With Quick Start Tutorial

[singhjason75]

Hello Everyone, I am new here, and I am having some trouble with the Quick Start Tutorial.

Attached is what my game view looks like when I try to run the game.

I enabled support for 2D physics, the New Input System, and for TextMeshPro.

I am also receiving console errors that say "Can't find subtitle panel for [gabriel]" etc.

I attached a screenshot of the errors as well.

Any help I could get on this would be much appreciated. I am relatively new to Unity as well, and I most certainly may have overlooked something obvious.

[Tony Li]

Hi,

What version of the Dialogue System are you using? (Tools > Pixel Crushers > Dialogue System > Welcome Window)

I think the new Input System may be getting in the way. It probably isn't fully configured for the Dialogue System in your project. This may get things running:

1. Inspect the Dialogue Manager prefab's Input Device Manager component.

2. Clear the Back Buttons list by setting Back Buttons > Size to 0.

3. Clear the Submit Button field; set it to an empty string instead of "Submit".

[singhjason75]

Hi! Thank you for the quick response!

So, I am currently using version 2.2.7. I set the back buttons size to 0, and cleared the Submit Button string. However, It seems that the problem is still persisting. The errors are still there as well.

[Tony Li]

If you just want to see it working, untick the New Input System checkbox in the Welcome window, and make sure your project settings allow the legacy input system. (I'm betting that the new input system hasn't been fully set up for use with the Dialogue System yet. The detailed instructions for that are in Plugins/Pixel Crushers/Common/Documentation/Input_Device_Manager.pdf. If the new input system isn't fully set up, it can throw errors that could stop the Dialogue System from fully initializing.)

If you want to get the new input system working with the Dialogue System, and if you're using a Selector or Proximity Selector component, check if the 'Use Button' field is assigned. If so, set it to an empty string for now.

In the Console window, the yellow warnings are less of an issue right now than the red error messages. If you still see any red errors after making the changes above, please click on one of them, press Ctrl+C to copy its details to the clipboard, then paste the clipboard into a reply here.

[singhjason75]

So, I am still working on seeing if the New Input Manager is working with the dialogue system. However, here is a red error I keep consistently getting.

[singhjason75]

Here is a bigger screenshot if that helps

[Tony Li]

Hi,

That message isn't related to the new Input System. As a first pass to see conversations working, inspect the Dialogue Manager and disable the Instantiate Prefabs component.

If you're able to play conversations without any errors, then re-enable the Instantiate Prefabs component, and let's look at what button is having the issue. At that point, please let me know if you've started customizing the quest log window prefab that's assigned to the Instantiate Prefabs component. If so, drill down into it until you find the 'Abandon Button Panel' GameObject. Inspect it, and assign the 'Abandon Button' child GameObject to the Standard UI Button Template component. Then save the prefab and give it a play.

[singhjason75]

Now that you mention it, I most certainly may have messed about with customizing some of the UI templates before I even checked if conversations were working. As a test, I repeated all the steps of the tutorial on an entirely new project, and that seems to work perfectly even with the New Input System Support. I am just going to use that project going forward.

Thank you for all your help, but it seems like it was my own fault the UI wasn't displaying properly.

[Tony Li]

I'm happy to hear that it's working now.