Journal not showing anything

[Tony Li]

What version of Unity are you using?

Did you enable support for 2D? (Tools > Pixel Crushers > Common > Misc > Enable Physics2D Support)

[neliuz]

Yes, i did enable it!
My version of unity is: 2018.3.6f1

[Tony Li]

I'm checking the project that you sent me.

Can you accept quests in the web demo?

What do you mean by you are "unable to accept any quests"? Do UI buttons not respond? Or, if you can click on UI buttons, do they not add a quest to your journal?

[Tony Li]

I'm able to pick up a quest and view it in your project, too. I'll send you an email.

[neliuz]

Ok , yeah do that! Thanks!

I dont see any buttons in the Demo project to accept the quests,
From the package i sent you i am able to accept quests,
The problem is that i dont see anything in the Journal , ( see quest progress etc.. )
And the image hero_portrait is not there, plus i can see it there but when pressing start it disappears.

Best Regards

Cornelius

[Tony Li]

I provided detailed answers in my email to you. To summarize:

1. Your scene should have only one EventSystem.

2. Call QuestJournal.ShowJournalUI or ToggleJournalUI on the player GameObject, not the prefab.

3. Assign the player's portrait image to the player's Quest Journal > ID > Image field.

I don't understand why you don't see any buttons in the Demo. But the steps in my email should help you get your scene working.

[neliuz]

Thanks Tony!
Appreciate your help with this!
Will reply on the email as well

Best regards

Cornelius

[Zero4ffect]

I've been futzing around with this same problem for a couple of days now and just now discovered that the 'Quest Dialog UI' and 'Quest Journal UI' GameObjects had been enabled in the base prefab. After re-disabling those GameObjects in the base prefab hierarchy the Quest Journal started working again as expected. I didn't investigate further so I'm not sure why this was the case.

Hope this helps someone.

Best,
- Z

[Tony Li]

Thanks for pointing that out. It's awkward to require them to be disabled. I'll address that in the next update.