Pixel Crushers Forum

I ran into a weird bug with this - if I click the same quest twice in a row, it's blank the second time. (In between I hit a back button that turns off the description panel and reopens the list panel.) It's works fine so long as I click a different quest in between. https://blekkenhorst.ca/2021/wp-...

On my goodness, I'm so embarrassed. I was missing a bracket after the conditional checking the tag, so it was triggering the Debug.Log properly, but the alert was being triggered by everything, including the road the player was standing on. :oops: Don't know why it was only triggered when hitting th...

It's fine if it only happens when they move, as the play runs into it. The issue is the alert doesn't disappear when the player stops moving, or once the player moves away from the wall. The debug log stops, but the alert doesn't dissappear. I tried oncollisionenter earlier, it's not working because...

If I disable the proximity selector, I can't interact with the NPCs at all. The problem seems to have fixed itself when I removed the trigger from the player. I'm usuaing a character controller to control the player, and it seems like having a trigger collider on the player, even if it was small, wa...

I've been trying to figure this out for a few days and I've hit a wall. The proximity selector to trigger NPC dialogue only sometimes works. It seems slightly more likely to trigger if I hit the input key twice. I have this in the Update loop of the ProximitySelector script: if (Input.GetKeyDown(Key...

That was so easy, thank you!

We're trying to switch our quest menu so the quests are listed by title, and then clicking on the quest title will then open a new panel with the quest details. We'd use a back button to return to the list. The current template we're adapting is 'Basic Standard UI Quest Log Window', it's displaying ...

I've encountered another issue though, somewhat related - I am triyng to use that OnConversationEnd event, but it is calling it on the first frame of the last line of the conversation, rather than when the dialogue actually finishes - this means our dialogue camera system and character controller lo...

You were right! There was an empty event there. Removing it fixed everything.

The NPCs were set to OnUse, and the Player was set to Selector with the mouse, which doesn't make sense for our center-locked third person character. Ideally the player would get the interact message when entering a trigger on the character, and the conversation would start when the player hit the i...